From: Sam Ravnborg <sam@ravnborg.org>
To: Andrey Smirnov <andrew.smirnov@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 0/4] Enable DT support for AT91SAM9263EK
Date: Thu, 4 Jan 2018 18:52:49 +0100 [thread overview]
Message-ID: <20180104175249.GA24826@ravnborg.org> (raw)
In-Reply-To: <CAHQ1cqGm7dhq+fJ=kXP9SzVO59btoPgoJMCpROMELWTnRDMSNQ@mail.gmail.com>
Hi Andrey.
> Didn't see anything unreasonable in this series, so:
>
> Reviewed-by: Andrey Smirnov <andrew.smirnov@gmail.com>
Thanks for the review!
> One note though, Sam, I can see re-roll count in the subject of the
> cover letter, but not in the subject of the patches that follow. Would
> you mind using "git format-patche" with --reroll-count (-v) going
> forward? It's way easier to figure out the version of a given patch in
> a series if you can see that in the header.
I have somehow missed this option - will use it in the future.
@Sascha - let me know if you want me to re-submit this
and the other patch-set with Andrey's ack.
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-01-04 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:02 Sam Ravnborg
2018-01-01 13:15 ` [PATCH 1/4] arm: at91: move irq_fixup to header file Sam Ravnborg
2018-01-01 13:15 ` [PATCH 2/4] arm: at91: simplify soc setup Sam Ravnborg
2018-01-01 13:15 ` [PATCH 3/4] at91sam9263ek: enable multi-image build Sam Ravnborg
2018-01-01 13:15 ` [PATCH 4/4] at91sam9263ek: enable DT support Sam Ravnborg
2018-01-07 22:11 ` Sam Ravnborg
2018-01-04 16:45 ` [PATCH v2 0/4] Enable DT support for AT91SAM9263EK Andrey Smirnov
2018-01-04 17:52 ` Sam Ravnborg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180104175249.GA24826@ravnborg.org \
--to=sam@ravnborg.org \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox