From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Keerthy <j-keerthy@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Immutable branch between MFD, GPIO and Regulator due for the v4.9 merge window
Date: Fri, 9 Sep 2016 13:11:40 +0100 [thread overview]
Message-ID: <20160909121140.GQ27946@sirena.org.uk> (raw)
In-Reply-To: <20160908072646.GH4921@dell>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Thu, Sep 08, 2016 at 08:26:46AM +0100, Lee Jones wrote:
> On Wed, 07 Sep 2016, Linus Walleij wrote:
> > Hm it is based on a later release candidate than my tree so I'll wait
> > and see if I
> > have to pull it (like if there are clashes in linux-next...)
> You use -rc1 as your base? Crazy man. :)
I do that too for the topic branches. It's really helpful for cross
tree work as it avoids issues like the above - wherever it's being
merges it shouldn't pull in any extra dependencies so things are clearer
when reviewing diffs/logs and git has an easier time coping.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-09 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:58 [PATCH v9 0/3] mfd: lp873x: Add lp873x PMIC support Keerthy
2016-08-31 8:58 ` [PATCH v9 1/3] " Keerthy
2016-08-31 12:18 ` Lee Jones
2016-08-31 8:58 ` [PATCH v9 2/3] gpio: lp873x: Add support for General Purpose Outputs Keerthy
2016-08-31 8:58 ` [PATCH v9 3/3] regulator: lp873x: Change the MFD config option as per latest naming Keerthy
2016-08-31 12:24 ` [GIT PULL] Immutable branch between MFD, GPIO and Regulator due for the v4.9 merge window Lee Jones
2016-08-31 12:50 ` Keerthy
2016-08-31 15:21 ` Lee Jones
2016-09-07 20:03 ` Linus Walleij
2016-09-08 7:26 ` Lee Jones
2016-09-09 12:11 ` Mark Brown [this message]
2016-09-12 9:18 ` Lee Jones
2016-09-13 8:32 ` Linus Walleij
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=20160909121140.GQ27946@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.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).