From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Olof Johansson <olof@lixom.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linus.walleij@stericsson.com,
arnd@arndb.de, linux-sh@vger.kernel.org, horms@verge.net.au,
grant.likely@secretlab.ca, lethal@linux-sh.org
Subject: Re: [PATCH] gpio: Emma Mobile GPIO driver V2
Date: Sat, 19 May 2012 14:06:14 +0200 [thread overview]
Message-ID: <201205191406.15061.rjw@sisk.pl> (raw)
In-Reply-To: <CAOesGMi8LPO=AFSshC8UyCmBB3hG38YKHWnHmcNCnLvgR2xcTw@mail.gmail.com>
On Thursday, May 17, 2012, Olof Johansson wrote:
> On Wed, May 16, 2012 at 3:37 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Thursday, May 17, 2012, Olof Johansson wrote:
> >> On Wed, May 16, 2012 at 1:05 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> > On Wednesday, May 16, 2012, Linus Walleij wrote:
> >> >> On Wed, May 16, 2012 at 12:15 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> >>
> >> >> > Do you guys have any preferences how to merge this?
> >> >> >
> >> >> > Can I include it together with the EMEV2 SoC bits perhaps? That may be
> >> >> > easy so we can keep track of the platform data header file dependency.
> >> >>
> >> >> For ux500 I made a special "gpio and pins" branch and sent through ARM SoC.
> >> >
> >> > The problem is we have a patch depending on the $subject one in the EMEV2
> >> > series and it would be better to keep them both together if that's not
> >> > a big deal.
> >>
> >> Dependencies are fine, as long as they are not circular. You can
> >> either pull in the gpio/pins branch into the EMEV2 branch, or base it
> >> on it.
> >
> > I guess I'll try to merge the gpio/pins into the EMEV2 branch.
>
> By the way, I should have mentioned that if the dependencies are only
> for building and not for context when applying patches, then it's
> sufficient to let us know in the pull request so we merge the branches
> in the right order when sending to Linus (so we maintain
> bisectability).
Well, eventually I have taken the GPIO patch from Magnus into the emev2 branch,
because that has been much more convenient to me (pull request sent already).
Thanks,
Rafael
next prev parent reply other threads:[~2012-05-19 12:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 15:43 Magnus Damm
2012-05-15 16:32 ` Joe Perches
2012-05-17 6:20 ` Magnus Damm
2012-05-16 7:11 ` Linus Walleij
2012-05-16 10:15 ` Magnus Damm
2012-05-16 11:25 ` Linus Walleij
2012-05-16 20:05 ` Rafael J. Wysocki
2012-05-16 22:22 ` Olof Johansson
2012-05-16 22:37 ` Rafael J. Wysocki
2012-05-16 22:54 ` Olof Johansson
2012-05-18 22:56 ` Grant Likely
2012-05-19 1:18 ` Olof Johansson
2012-05-19 1:44 ` Grant Likely
2012-05-19 2:27 ` Olof Johansson
2012-05-19 12:06 ` Rafael J. Wysocki [this message]
2012-05-16 7:29 ` Paul Mundt
2012-05-16 10:09 ` Magnus Damm
2012-05-16 12:09 ` Arnd Bergmann
2012-05-16 15:47 ` Magnus Damm
2012-05-17 0:41 ` Paul Mundt
2012-05-18 23:25 ` Grant Likely
2012-05-19 6:46 ` Paul Mundt
2012-05-19 20:05 ` Grant Likely
2012-05-18 22:57 ` Grant Likely
2012-05-19 2:13 ` Paul Mundt
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=201205191406.15061.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=lethal@linux-sh.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
/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
Powered by JetHome