From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: r7s72100: add ethernet clock to device tree
Date: Tue, 6 Sep 2016 12:49:38 +0200 [thread overview]
Message-ID: <20160906104937.GF16304@verge.net.au> (raw)
In-Reply-To: <SG2PR06MB116533792940F6E3193E7EDB8AE50@SG2PR06MB1165.apcprd06.prod.outlook.com>
On Fri, Sep 02, 2016 at 12:50:39PM +0000, Chris Brandt wrote:
> On 9/2/2016, Simon Horman wrote:
> > For future submissions please consider:
> > 1. Supplying a cover letter (git format-patch has a --cover-letter option)
> > for patch-sets comprising more than one patch. This allows you to describe
> > an overview of what the series as a whole achieves. And is also
> > convenient for maintainers to reply to when accepting your patches.
>
> OK. I can do that.
>
>
> > 2. Starting a new thread for each new version of a patch/patch-set.
>
> Does that mean to NOT use --in-reply-to= when submitting a v2,v3,etc... ????
I think so.
> One more question:
> Can I submit a patches series now that just adds all the MSTP clock nodes that I'll be working on for the next couple weeks? (USB, SDHI, MMC)
> Or, do I have to wait till I have the drivers working?
> Or, better yet, can I add all the MSTP clocks that will probably get used at some point (basically, everything that we're using today in our 3.14 BSP).
I think that would be ok. I would slightly prefer that MSTP patches are
added in such a way that they can be tested. But in this case I'm not
sure anyone would test them :^)
prev parent reply other threads:[~2016-09-06 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 15:54 [PATCH 1/3] ARM: dts: r7s72100: add ethernet clock to device tree Chris Brandt
2016-09-01 15:54 ` [PATCH 2/3] ARM: dts: r7s72100: add ethernet " Chris Brandt
2016-09-01 20:50 ` Geert Uytterhoeven
2016-09-01 15:54 ` [PATCH 3/3] ARM: dts: rskrza1: add ethernet DT support Chris Brandt
2016-09-01 20:50 ` Geert Uytterhoeven
2016-09-01 16:30 ` [PATCH 1/3] ARM: dts: r7s72100: add ethernet clock to device tree Sergei Shtylyov
2016-09-01 16:38 ` Chris Brandt
2016-09-01 16:54 ` Sergei Shtylyov
2016-09-01 19:35 ` Geert Uytterhoeven
2016-09-02 1:40 ` [PATCH v2 " Chris Brandt
2016-09-02 1:40 ` [PATCH v2 2/3] ARM: dts: r7s72100: add ethernet " Chris Brandt
2016-09-02 1:40 ` [PATCH v2 3/3] ARM: dts: rskrza1: add ethernet DT support Chris Brandt
2016-09-02 8:26 ` [PATCH v2 1/3] ARM: dts: r7s72100: add ethernet clock to device tree Simon Horman
2016-09-02 12:50 ` Chris Brandt
2016-09-06 10:49 ` Simon Horman [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=20160906104937.GF16304@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).