From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Opensource [Anthony Olech]"
<anthony.olech.opensource@diasemi.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH V1 2/3] MFD: da9052: Add new DA9053 BC chip variant
Date: Wed, 26 Feb 2014 20:41:35 +0900 [thread overview]
Message-ID: <20140226114135.GC31120@sirena.org.uk> (raw)
In-Reply-To: <20140226093203.GK9195@lee--X1>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Wed, Feb 26, 2014 at 09:32:03AM +0000, Lee Jones wrote:
> > It can be worth doing anyway with a subsystem that's actively developed
> > since sometimees the dependencies are the other way - the APIs in Linus'
> > tree may have gone away.
> Then what happens if the tree that your patch finally gets sucked into
> is pulled before the one you've written your code against? I'd say
> basing your code on -next is generally a bad idea.
Submitters should defintely at the very least be checking against the
subsystem tree (since that's what they're really submitting against) -
it's always annoying when someone submits code that either doesn't
apply or fails to build with the current tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-26 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 16:32 [PATCH V1 2/3] MFD: da9052: Add new DA9053 BC chip variant Opensource [Anthony Olech]
2014-02-25 8:57 ` Lee Jones
2014-02-25 10:13 ` Opensource [Anthony Olech]
2014-02-25 11:50 ` Lee Jones
2014-02-25 12:15 ` Mark Brown
2014-02-25 12:40 ` Lee Jones
2014-02-25 23:07 ` Mark Brown
2014-02-26 9:32 ` Lee Jones
2014-02-26 11:41 ` Mark Brown [this message]
2014-02-26 11:59 ` Lee Jones
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=20140226114135.GC31120@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anthony.olech.opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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