From: Alex Courbot <acourbot@nvidia.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Romain Naour <romain.naour@openwide.fr>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] gpio: remove GENERIC_GPIO completely
Date: Fri, 29 Mar 2013 08:24:59 -0700 [thread overview]
Message-ID: <5155B24B.2030601@nvidia.com> (raw)
In-Reply-To: <1364562678-8945-1-git-send-email-acourbot@nvidia.com>
On 03/29/2013 06:11 AM, Alexandre Courbot wrote:
> If I can get a few acks on these (or at least the first two ones) I'd like to
> include them into my next branch as soon as possible so points of breakage can
> be fixed. There are indeed a few new users of GENERIC_GPIO (CC Romain, I sent a
> warning but saw no action so far) in the next tree and compilation will break
> for them.
Alternatively, Grant may want to pull all the patches I did so far -
they are in next for more than 10 days now and no complain has been
raised. Also it's probably better to keep all GPIO-related changes into
the same tree.
Alex.
WARNING: multiple messages have this Message-ID (diff)
From: acourbot@nvidia.com (Alex Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] gpio: remove GENERIC_GPIO completely
Date: Fri, 29 Mar 2013 08:24:59 -0700 [thread overview]
Message-ID: <5155B24B.2030601@nvidia.com> (raw)
In-Reply-To: <1364562678-8945-1-git-send-email-acourbot@nvidia.com>
On 03/29/2013 06:11 AM, Alexandre Courbot wrote:
> If I can get a few acks on these (or at least the first two ones) I'd like to
> include them into my next branch as soon as possible so points of breakage can
> be fixed. There are indeed a few new users of GENERIC_GPIO (CC Romain, I sent a
> warning but saw no action so far) in the next tree and compilation will break
> for them.
Alternatively, Grant may want to pull all the patches I did so far -
they are in next for more than 10 days now and no complain has been
raised. Also it's probably better to keep all GPIO-related changes into
the same tree.
Alex.
next prev parent reply other threads:[~2013-03-29 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 13:11 [PATCH 0/3] gpio: remove GENERIC_GPIO completely Alexandre Courbot
2013-03-29 13:11 ` Alexandre Courbot
2013-03-29 13:11 ` [PATCH 1/3] Convert selectors of GENERIC_GPIO to GPIOLIB Alexandre Courbot
2013-03-29 13:11 ` Alexandre Courbot
2013-03-29 13:11 ` [PATCH 2/3] Remove GENERIC_GPIO config option Alexandre Courbot
2013-03-29 13:11 ` Alexandre Courbot
2013-03-29 13:11 ` Alexandre Courbot
2013-03-29 13:11 ` [PATCH 3/3] Rename CONFIG_GPIOLIB to CONFIG_GPIO Alexandre Courbot
2013-03-29 15:24 ` Alex Courbot [this message]
2013-03-29 15:24 ` [PATCH 0/3] gpio: remove GENERIC_GPIO completely Alex Courbot
2013-04-03 13:28 ` Linus Walleij
2013-04-03 13:28 ` Linus Walleij
2013-04-07 3:23 ` Chen Baozi
2013-04-07 3:23 ` Chen Baozi
2013-04-07 21:25 ` Alexandre Courbot
2013-04-07 21:25 ` Alexandre Courbot
2013-04-07 21:25 ` Alexandre Courbot
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=5155B24B.2030601@nvidia.com \
--to=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=gnurou@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romain.naour@openwide.fr \
/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.