From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ian Lartey <ian@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-leds@vger.kernel.org,
linux-watchdog@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, swarren@wwwdotorg.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, mturquette@linaro.org, linus.walleij@linaro.org,
cooloney@gmail.com, rpurdie@rpsys.net, akpm@linux-foundation.org,
sameo@linux.intel.com, wim@iguana.be, lgirdwood@gmail.com,
gg@slimlogic.co.uk, j-keerthy@ti.com, ldewangan@nvidia.com,
t-kristo@ti.com
Subject: Re: [PATCH v10 0/12] Palmas updates
Date: Sun, 24 Mar 2013 21:13:37 +0000 [thread overview]
Message-ID: <20130324211336.GA18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130323060455.78a4c90c3f1e028434818fd1@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On Sat, Mar 23, 2013 at 06:04:55AM +1100, Stephen Rothwell wrote:
> On Fri, 22 Mar 2013 14:55:10 +0000 Ian Lartey <ian@slimlogic.co.uk> wrote:
> > Patches based on linux-next-20130319
> I can't really comment on the patch set except to say that you should not
> base on linux-next, you should base on the tree to which you expect the
> patch set to be applied.
It's fairly common to suggest to people working over lots of subsystems
like this that they use -next since for most subsystems it contains the
trees that should be submitted against and it's much more efficient.
This works OK most of the time when people are posting patches as
opposed to pull requests, though obviously cross tree issues do happen
from time to time.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-24 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1363964122-19201-1-git-send-email-ian@slimlogic.co.uk>
2013-03-22 19:04 ` [PATCH v10 0/12] Palmas updates Stephen Rothwell
2013-03-24 21:13 ` Mark Brown [this message]
[not found] ` <1363964122-19201-5-git-send-email-ian@slimlogic.co.uk>
2013-03-24 3:19 ` [PATCH v10 04/12] watchdog: add Palmas Watchdog support Guenter Roeck
2013-08-20 20:31 ` Wim Van Sebroeck
[not found] ` <1363964122-19201-6-git-send-email-ian@slimlogic.co.uk>
2013-03-24 4:09 ` [PATCH v10 05/12] watchdog: Kconfig for Palmas watchdog Guenter Roeck
[not found] ` <1363964122-19201-13-git-send-email-ian@slimlogic.co.uk>
2013-03-25 1:07 ` [PATCH v10 12/12] regulator: palmas remove palmas-charger option from DT bindings Mark Brown
[not found] ` <1363964122-19201-2-git-send-email-ian@slimlogic.co.uk>
2013-03-25 17:59 ` [PATCH v10 01/12] mfd: DT bindings for the palmas family MFD Stephen Warren
2013-03-25 19:47 ` Mark Brown
2013-05-30 11:33 ` keerthy
2013-05-30 23:03 ` Stephen Warren
[not found] ` <DC88CAD03C0052499C1907B327FC63229E662E@DBDE04.ent.ti.com>
2013-06-04 6:24 ` gg
2013-04-05 16:30 ` [PATCH v10 0/12] Palmas updates Samuel Ortiz
2013-04-08 15:55 ` Graeme Gregory
2013-04-08 16:11 ` Samuel Ortiz
[not found] ` <1363964122-19201-4-git-send-email-ian@slimlogic.co.uk>
2013-04-05 16:32 ` [PATCH v10 03/12] mfd: palmas add variant and OTP detection Samuel Ortiz
[not found] ` <1363964122-19201-3-git-send-email-ian@slimlogic.co.uk>
2013-04-08 15:51 ` [PATCH v10 02/12] mfd: palmas: is_palmas_charger needed by multiple drivers Samuel Ortiz
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=20130324211336.GA18316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=cooloney@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=ian@slimlogic.co.uk \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=swarren@wwwdotorg.org \
--cc=t-kristo@ti.com \
--cc=wim@iguana.be \
/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).