From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tiberiu Breana <tiberiu.a.breana@intel.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Sascha Hauer <kernel@pengutronix.de>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: light: stk3310: use flags argument of devm_gpiod_get
Date: Mon, 15 Jun 2015 10:35:06 +0200 [thread overview]
Message-ID: <20150615083506.GZ18985@pengutronix.de> (raw)
In-Reply-To: <CACRpkdaLUGyZEB0gK--s-H0t8NCw8JuKWHJgCzmx4H=pQJekFQ@mail.gmail.com>
Hi Linus,
On Mon, Jun 15, 2015 at 10:16:46AM +0200, Linus Walleij wrote:
> On Fri, Jun 12, 2015 at 9:51 AM, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
>
> > Note I plan to make the flags parameter mandatory for 4.3. So unless
> > this change gets into 4.2, would it be ok to let it go in via the gpio
> > tree?
>
> Sounds like a plan. If you will have a patch set with the remaining
> consumers fixed and then remove the non-flagged functions
> on top, let's merge that into the GPIO tree for linux-next right after
> the 4.2 merge window so we can terminate this task.
That's exactly my plan.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2015-06-15 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 7:51 [PATCH] iio: light: stk3310: use flags argument of devm_gpiod_get Uwe Kleine-König
2015-06-13 18:06 ` Jonathan Cameron
2015-06-13 19:11 ` Uwe Kleine-König
2015-06-13 20:47 ` Jonathan Cameron
2015-06-15 8:16 ` Linus Walleij
2015-06-15 8:35 ` Uwe Kleine-König [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=20150615083506.GZ18985@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=gnurou@gmail.com \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tiberiu.a.breana@intel.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