From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: linux-next: manual merge of the driver-core tree with the sound-asoc tree
Date: Mon, 10 Nov 2014 10:02:24 +0000 [thread overview]
Message-ID: <20141110100224.GG3815@sirena.org.uk> (raw)
In-Reply-To: <20141110050719.GA16980@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Mon, Nov 10, 2014 at 02:07:19PM +0900, Greg KH wrote:
> On Mon, Nov 10, 2014 at 03:51:42PM +1100, Stephen Rothwell wrote:
> > I assume that there was a good reason not to farm these patches out to
> > their respective maintainers?
> Yes, It was easier to hit everything in one tree, at one time, so that
> is what Wolfram did. Sorry for the merge conflicts, I didn't think
> anyone would be adding .driver attributes to files after they had been
> added to the tree.
People are rather more likely to do that if they know that not adding
driver attributes is a thing, and that's more likely to happen if you
tell people that this change is happening, for example by sending the
patches to them. This merge conflict was the first I'd heard of this
being something we wanted to do.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-10 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 4:31 linux-next: manual merge of the driver-core tree with the sound-asoc tree Stephen Rothwell
2014-11-10 4:38 ` Greg KH
2014-11-10 4:51 ` Stephen Rothwell
2014-11-10 5:07 ` Greg KH
2014-11-10 10:02 ` Mark Brown [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=20141110100224.GG3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).