From: heikki.krogerus@linux.intel.com (Heikki Krogerus)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/5] net: rfkill: gpio: cleanup and a few new acpi ids
Date: Wed, 9 Apr 2014 13:01:47 +0300 [thread overview]
Message-ID: <20140409100147.GB3083@xps8300> (raw)
In-Reply-To: <1396946275.5936.2.camel@jlt4.sipsolutions.net>
Hi,
On Tue, Apr 08, 2014 at 10:37:55AM +0200, Johannes Berg wrote:
> On Tue, 2014-04-01 at 17:02 +0300, Heikki Krogerus wrote:
> > I hope this one is OK with everyone.
>
> It's fine with me. Are you expecting me to pick up any of these patches,
> or do you want them to go through some other tree? Either way is fine
> with me, but the first patch looks like something I probably shouldn't
> be taking.
The second patch depends on it.
Stephen! Are you expecting any changes to board-paz00.c in this kernel
cycle? If not, I think it would be easiest if Johannes, you take the
whole set. What do you guys think?
Thanks,
--
heikki
next prev parent reply other threads:[~2014-04-09 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 14:02 [PATCHv3 0/5] net: rfkill: gpio: cleanup and a few new acpi ids Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 1/5] ARM: tegra: remove obsolete gpio entries Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 2/5] net: rfkill: gpio: remove unused and obsolete platform parameters Heikki Krogerus
2014-04-10 16:26 ` Linus Walleij
2014-04-01 14:02 ` [PATCHv3 3/5] net: rfkill: gpio: add ACPI ID for GPS module on Lenovo Miix2 Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 4/5] net: rfkill: gpio: add ACPI IDs for a Broadcom bluetooth chip Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 5/5] net: rfkill: gpio: hard-code the gpio names Heikki Krogerus
2014-04-10 16:27 ` Linus Walleij
2014-04-02 9:36 ` [PATCHv3 0/5] net: rfkill: gpio: cleanup and a few new acpi ids Alexandre Courbot
2014-04-08 8:37 ` Johannes Berg
2014-04-09 10:01 ` Heikki Krogerus [this message]
2014-04-09 15:32 ` Stephen Warren
2014-04-11 7:26 ` Johannes Berg
2014-04-11 7:32 ` Johannes Berg
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=20140409100147.GB3083@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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).