linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org,
	Alexandre Courbot <gnurou@gmail.com>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	linux-omap@vger.kernel.org, Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio
Date: Sat, 23 Jul 2016 10:10:52 -0400	[thread overview]
Message-ID: <20160723141051.GB12632@windriver.com> (raw)
In-Reply-To: <8737n022tr.fsf@belgarion.home>

[Re: [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio] On 23/07/2016 (Sat 10:09) Robert Jarzmik wrote:

> Paul Gortmaker <paul.gortmaker@windriver.com> writes:
> 

[...]

> >
> > But with ARM and GPIO being different subsystems, we'll need to get
> > this in ARM 1st, and then wait a release before changing the GPIO
> > header, otherwise we'll risk triggering these three build failures.
> >
> > So, if folks consider these three trivial changes OK for late in the
> > for-4.8 cycle, then great.  Otherwise I'll resubmit the ARM parts for
> > for-4.9 and the GPIO bits for the one after that.

[...]

> Hi Paul,
> 
> I'll take the mach-pxa changes to pxa/for-next tree with Linus's ack.
> Tony, I think you will carry the remaining omap2 one, right ?
> 
> As for the cycle, I'd prefer have it for-4.9 as we're at rc7 and it's a bit late
> for me. If you want your GPIO bits to get in 4.9 I think I can commit to request
> pull very early (-rc1 time) or give my ack so that Linus can carry these changes
> through the gpio tree with the other changes.

Yep, agreed it is now (Sat) a bit late, so as per what I said above, do
whatever you are comfortable with and I'll react accordingly to make
sure the gpio fix lands on a baseline with all the other three patches
present and doesn't introduce build regressions.

Thanks,
Paul.

> 
> Cheers.
> 
> -- 
> Robert

      reply	other threads:[~2016-07-23 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20  4:13 [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio Paul Gortmaker
2016-07-20  4:13 ` [PATCH 1/3] ARM: mach-omap2: remove bogus "or_module" from rx51-peripherals Paul Gortmaker
2016-07-22  6:41   ` Tony Lindgren
2016-07-22 14:02     ` Paul Gortmaker
2016-07-23  5:55       ` Tony Lindgren
2016-07-23 14:14         ` Paul Gortmaker
2016-07-20  4:13 ` [PATCH 2/3] ARM: pxa: add module.h for corgi symbol_get/symbol_put usage Paul Gortmaker
2016-07-20  4:13 ` [PATCH 3/3] ARM: pxa: add module.h for spitz " Paul Gortmaker
2016-07-22 15:29 ` [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio Linus Walleij
2016-07-23  8:09 ` Robert Jarzmik
2016-07-23 14:10   ` Paul Gortmaker [this message]

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=20160723141051.GB12632@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=daniel@zonque.org \
    --cc=gnurou@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=robert.jarzmik@free.fr \
    --cc=tony@atomide.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).