From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shaveta Leekha <shaveta@freescale.com>,
Christian Ruppert <christian.ruppert@abilis.com>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: Removal of GENERIC_GPIO breaks -next
Date: Wed, 17 Apr 2013 18:46:44 +0530 [thread overview]
Message-ID: <516EA0BC.2040109@synopsys.com> (raw)
In-Reply-To: <CAAVeFuL6qAz1OvnxtMj4jCjR3YR8C218+8oAgGRkCaWQJ_-KEg@mail.gmail.com>
On 04/17/2013 06:34 PM, Alexandre Courbot wrote:
>
> Yes, I am not too worried about arc since it doesn't break anything.
> But as you mention it would be better if the whole job could be done
> by the same patch. The problem here is the merge order, for me to
> address this I need to work after your patches.
OK I understand. Since your code touches a lot more stuff, I don't know if the
ordering should be governed by this small harmless patch alone :-)
> So maybe in the end my
> series should be merged at the end of the merge window, and after all
> architecture code is merged, to make sure I can address all instances.
You are touching a lot of arches anyways so you will have to be after them
anyways. Is that right ?
Anyhow lets park this patch for now - we can push it in the 3.10-rc cycle.
-Vineet
next prev parent reply other threads:[~2013-04-17 13:16 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
2013-04-17 12:07 ` Vineet Gupta
2013-04-17 13:04 ` Alexandre Courbot
2013-04-17 13:16 ` Vineet Gupta [this message]
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=516EA0BC.2040109@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=christian.ruppert@abilis.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 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.