From: Peter Korsgaard <jacmet@sunsite.dk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wm831x-spi: use id_table rather hand rolled variant handling
Date: Mon, 12 Sep 2011 18:47:32 +0200 [thread overview]
Message-ID: <87pqj57lnf.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110912163812.GE5887@opensource.wolfsonmicro.com> (Mark Brown's message of "Mon, 12 Sep 2011 17:38:12 +0100")
>>>>> "Mark" == Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
Hi,
Mark> Non-bugfix patches like this should always be submitted against the
Mark> latest code in -next unless the subsystem is being unusual. I can tell
Mark> you're not working against the latest -next becuase it has a version of
Mark> this in it already. :)
Argh, sorry - I just noticed it while looking at something else in mfd/.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-09-12 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 15:45 [PATCH] wm831x-spi: use id_table rather hand rolled variant handling Peter Korsgaard
2011-09-12 16:38 ` Mark Brown
2011-09-12 16:47 ` Peter Korsgaard [this message]
2011-09-12 16:54 ` Mark Brown
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=87pqj57lnf.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=broonie@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.