From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PULL gpio-for-next] gpio: make flags mandatory for gpiod_get functions
Date: Mon, 20 Jul 2015 08:56:05 +0200 [thread overview]
Message-ID: <20150720065605.GP7013@pengutronix.de> (raw)
In-Reply-To: <CACRpkdbDtg=Ssod4K881juitv4fu3iPO8TkE+ZqEALKMqeTwDA@mail.gmail.com>
Hello Linus,
On Fri, Jul 17, 2015 at 02:28:25PM +0200, Linus Walleij wrote:
> On Wed, Jul 15, 2015 at 8:39 AM, Alexandre Courbot <gnurou@gmail.com> wrote:
> > I'm all for taking this into -next ASAP then. Linus has control over
> > the tree though, so his action is required.
>
> I am pushing it today.
>
> I finally found this message in my messy inbox. I'm a bit up over my
> ears in patches...
This somehow failed. My tag is merged in your devel branch, but this
contains several commits missing in your for-next. Is this intended?
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
next prev parent reply other threads:[~2015-07-20 6:56 UTC|newest]
Thread overview: 22+ 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: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
[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: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 ` [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 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
2015-07-06 9:09 ` [PATCH gpio-for-next 10/10] gpio: make flags mandatory for gpiod_get functions 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
2015-07-15 6:39 ` Alexandre Courbot
2015-07-17 12:28 ` Linus Walleij
2015-07-20 6:56 ` Uwe Kleine-König [this message]
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=20150720065605.GP7013@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 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).