All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>
Cc: linux-gpio@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PULL gpio-for-next] gpio: make flags mandatory for gpiod_get functions
Date: Wed, 15 Jul 2015 08:28:25 +0200	[thread overview]
Message-ID: <20150715062825.GC1426@pengutronix.de> (raw)
In-Reply-To: <20150708105138.GD1426@pengutronix.de>

Hello Linus, hello Alexandre,

On Wed, Jul 08, 2015 at 12:51:38PM +0200, Uwe Kleine-König wrote:
> On Mon, Jul 06, 2015 at 11:07:59AM +0200, Uwe Kleine-König wrote:
> > now that all patches that were in next hit Linus Torvalds' tree and
> > v4.2-rc1 is out here comes the promised pull request that makes usage of
> > the flags parameter mandatory for gpiod_get et al:
> > 
> > The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
> > 
> >   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.pengutronix.de/git/ukl/linux.git tags/gpiod-flags-for-4.3
> > 
> > for you to fetch changes up to b17d1bf16cc72a374a48d748940f700009d40ff4:
> > 
> >   gpio: make flags mandatory for gpiod_get functions (2015-07-06 10:39:24 +0200)
> gentle ping!
the (or at least my) plan was to get this into next early after the
merge window for 4.2 closes. Now we're already at -rc2. Can you please
comment?

As of next-20150715 there don't seem to be any new users of gpiod
without flags btw.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-07-15  6:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 21:36 [PATCH] gpio: make flags mandatory for gpiod_get functions Uwe Kleine-König
2015-06-21  6:51 ` Alexandre Courbot
2015-07-06  9:07 ` [PULL gpio-for-next] " Uwe Kleine-König
2015-07-06  9:07   ` Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 01/10] drm/msm/dp: use flags argument of devm_gpiod_get to set direction Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 02/10] drm/tilcdc: panel: make better use of gpiod API Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 05/10] media: i2c/adp1653: set enable gpio to output Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 06/10] NFC: nxp-nci_i2c: use flags argument of devm_gpiod_get_index Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 07/10] phy: tusb1210: make better use of gpiod API Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 08/10] usb: dwc3: pci: " Uwe Kleine-König
     [not found]   ` <20150706090759.GS11824-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-07-06  9:09     ` [PATCH gpio-for-next 03/10] iio: light: stk3310: use flags argument of devm_gpiod_get Uwe Kleine-König
2015-07-06  9:09       ` Uwe Kleine-König
2015-07-06  9:35       ` Breana, Tiberiu A
2015-07-06  9:35         ` Breana, Tiberiu A
2015-07-06  9:09     ` [PATCH gpio-for-next 04/10] iio: magn: bmc150: " Uwe Kleine-König
2015-07-06  9:09       ` Uwe Kleine-König
2015-07-06  9:09     ` [PATCH gpio-for-next 09/10] usb: pass flags parameter to gpiod_get functions Uwe Kleine-König
2015-07-06  9:09   ` [PATCH gpio-for-next 10/10] gpio: make flags mandatory for " Uwe Kleine-König
2015-07-08 10:51   ` [PULL gpio-for-next] " Uwe Kleine-König
2015-07-15  6:28     ` Uwe Kleine-König [this message]
2015-07-15  6:39       ` Alexandre Courbot
2015-07-17 12:28         ` Linus Walleij
2015-07-20  6:56           ` Uwe Kleine-König
2015-07-20  7:41             ` Linus Walleij
2015-07-20  7:51               ` Uwe Kleine-König
2015-07-20  8:28             ` Linus Walleij

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=20150715062825.GC1426@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=gnurou@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    /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.