From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "Kukjin Kim" <kgene.kim@samsung.com>,
"'Alexandre Courbot'" <gnurou@gmail.com>,
"Olof Johansson" <olof@lixom.net>,
"'Romain Naour'" <romain.naour@openwide.fr>,
'linux-next' <linux-next@vger.kernel.org>,
"'Grant Likely'" <grant.likely@secretlab.ca>,
"'Linus Walleij'" <linus.walleij@linaro.org>,
"'Tomasz Figa'" <tomasz.figa@gmail.com>,
"'Heiko Stübner'" <heiko@sntech.de>,
linux-samsung-soc@vger.kernel.org,
"ARM kernel mailing list" <linux-arm-kernel@lists.infradead.org>
Subject: Re: GENERIC_GPIO considered deprecated
Date: Mon, 8 Apr 2013 21:36:44 +0200 [thread overview]
Message-ID: <201304082136.44905.arnd@arndb.de> (raw)
In-Reply-To: <5162EC32.2030602@wwwdotorg.org>
On Monday 08 April 2013, Stephen Warren wrote:
> >>
> >> Should do the trick, if we can make sure that your tree is merged
> >> prior to my patches.
> >
> > I'm not sure but I think, arm-soc tree should be merged into mainline before others...
> >
> >> Can you put it into your tree for 3.10?
> >>
> > I did, so it should be fine.
> >
>
> You may want to discuss how to handle this dependency with the arm-soc
> maintainers (CC'd).
I'm fine with putting the same branch into arm-soc as well as the gpio tree
and anything else that might need it, that tends to be the least invasive
way.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: GENERIC_GPIO considered deprecated
Date: Mon, 8 Apr 2013 21:36:44 +0200 [thread overview]
Message-ID: <201304082136.44905.arnd@arndb.de> (raw)
In-Reply-To: <5162EC32.2030602@wwwdotorg.org>
On Monday 08 April 2013, Stephen Warren wrote:
> >>
> >> Should do the trick, if we can make sure that your tree is merged
> >> prior to my patches.
> >
> > I'm not sure but I think, arm-soc tree should be merged into mainline before others...
> >
> >> Can you put it into your tree for 3.10?
> >>
> > I did, so it should be fine.
> >
>
> You may want to discuss how to handle this dependency with the arm-soc
> maintainers (CC'd).
I'm fine with putting the same branch into arm-soc as well as the gpio tree
and anything else that might need it, that tends to be the least invasive
way.
Arnd
next prev parent reply other threads:[~2013-04-08 19:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 2:15 GENERIC_GPIO considered deprecated Alexandre Courbot
2013-03-30 22:07 ` Romain Naour
2013-03-31 22:18 ` Alexandre Courbot
2013-04-04 0:35 ` Kukjin Kim
2013-04-04 18:12 ` Alexandre Courbot
2013-04-08 7:31 ` Kukjin Kim
2013-04-08 16:11 ` Stephen Warren
2013-04-08 16:11 ` Stephen Warren
2013-04-08 19:36 ` Arnd Bergmann [this message]
2013-04-08 19:36 ` Arnd Bergmann
2013-04-08 23:38 ` Stephen Rothwell
2013-04-08 23:38 ` Stephen Rothwell
2013-04-09 0:07 ` Alexandre Courbot
2013-04-09 0:07 ` Alexandre Courbot
2013-04-09 0:10 ` Stephen Rothwell
2013-04-09 0:10 ` Stephen Rothwell
2013-04-09 1:45 ` Kukjin Kim
2013-04-09 1:45 ` Kukjin Kim
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=201304082136.44905.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gnurou@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=romain.naour@openwide.fr \
--cc=swarren@wwwdotorg.org \
--cc=tomasz.figa@gmail.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.