From: Christian Ruppert <christian.ruppert@abilis.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shaveta Leekha <shaveta@freescale.com>,
linux-next <linux-next@vger.kernel.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>
Subject: Re: Removal of GENERIC_GPIO breaks -next
Date: Wed, 17 Apr 2013 13:21:19 +0200 [thread overview]
Message-ID: <20130417112117.GA993@ab42.lan> (raw)
In-Reply-To: <CAAVeFu+fM=fJ2zp-gX4T07COMB31yvs74dXUqrw1LH09M7MXLg@mail.gmail.com>
Hi Alexandre and Stephen,
Concerning the arch/arc/plat-tb10x/Kconfig issue, I already have a patch
pending which will select PINCTRL_TB10X and GPIO_TB10X for the TB10x
platform as soon as both drivers are accepted into the kernel. Both
drivers were submitted to lkml last week, see
http://www.spinics.net/lists/kernel/msg1515239.html and
http://www.spinics.net/lists/kernel/msg1515240.html.
I suggest to add the removal of GENERIC_GPIO to that patch and arrange
with Vineet to push it through the normal arc upstream when the TB10x
pinctrl/gpio drivers show up in linux-next. Alternatively, an
independent patch could be produced and applied either through the same
channel or sent to this list. Tell me what you prefer.
Greetings,
Christian
On Wed, Apr 17, 2013 at 07:37:33PM +0900, Alexandre Courbot wrote:
> Hi Stephen,
>
> It seems like the last few patches I pushed to my branch are going to
> break powerpc/85xx due to a merge issue. I have tried to warn you by
> email today but maybe you haven't read it yet.
>
> arch/powerpc/platforms/85xx/Kconfig has a "select GENERIC_GPIO" which
> will cause compilation breakage because I removed the GENERIC_GPIO
> config option for all platforms. This line should be removed by my
> "Convert selectors of GENERIC_GPIO to GPIOLIB" patch, but this line
> slipped in between and is thus still here.
>
> Also arch/arc/plat-tb10x/Kconfig now defines GENERIC_GPIO, this will
> not cause breakage but should not be here anymore (ideally removed by
> the "Remove GENERIC_GPIO config option" patch)
>
> Apart from these two issues, things seem to have gone fine, but I'm
> not sure how they should be addressed and by who?
>
> Thanks,
> Alex.
--
Christian Ruppert , <christian.ruppert@abilis.com>
/|
Tel: +41/(0)22 816 19-42 //| 3, Chemin du Pré-Fleuri
_// | bilis Systems CH-1228 Plan-les-Ouates
next prev parent reply other threads:[~2013-04-17 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:37 Removal of GENERIC_GPIO breaks -next Alexandre Courbot
2013-04-17 11:21 ` Christian Ruppert [this message]
2013-04-17 12:07 ` Vineet Gupta
2013-04-17 13:04 ` Alexandre Courbot
2013-04-17 13:16 ` Vineet Gupta
2013-04-18 7:18 ` Stephen Rothwell
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=20130417112117.GA993@ab42.lan \
--to=christian.ruppert@abilis.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=gnurou@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shaveta@freescale.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 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).