All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Chen-Yu Tsai <wens@csie.org>, Rhyland Klein <rklein@nvidia.com>,
	Marc Dietrich <marvin24@gmx.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCHv3 0/5] net: rfkill: gpio: cleanup and a few new acpi ids
Date: Fri, 11 Apr 2014 09:26:13 +0200	[thread overview]
Message-ID: <1397201173.4420.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5345680F.3040903@wwwdotorg.org>

On Wed, 2014-04-09 at 09:32 -0600, Stephen Warren wrote:

> > 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?
> 
> I can't predict the future, but the chances are pretty slim - that file
> is pretty tiny and doesn't have much churn.
> 
> The best approach is to put this series in its own topic branch. Then,
> if any conflict does come up, I can simply merge the branch into the
> Tegra treee and apply the conflicting patches on top.

Ok, I'll do that. Shout now if you don't want these patches merged :)

johannes

WARNING: multiple messages have this Message-ID (diff)
From: johannes@sipsolutions.net (Johannes Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/5] net: rfkill: gpio: cleanup and a few new acpi ids
Date: Fri, 11 Apr 2014 09:26:13 +0200	[thread overview]
Message-ID: <1397201173.4420.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5345680F.3040903@wwwdotorg.org>

On Wed, 2014-04-09 at 09:32 -0600, Stephen Warren wrote:

> > 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?
> 
> I can't predict the future, but the chances are pretty slim - that file
> is pretty tiny and doesn't have much churn.
> 
> The best approach is to put this series in its own topic branch. Then,
> if any conflict does come up, I can simply merge the branch into the
> Tegra treee and apply the conflicting patches on top.

Ok, I'll do that. Shout now if you don't want these patches merged :)

johannes

  reply	other threads:[~2014-04-11  7:26 UTC|newest]

Thread overview: 35+ 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 ` Heikki Krogerus
2014-04-01 14:02 ` Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 1/5] ARM: tegra: remove obsolete gpio entries Heikki Krogerus
2014-04-01 14:02   ` Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 2/5] net: rfkill: gpio: remove unused and obsolete platform parameters Heikki Krogerus
2014-04-01 14:02   ` Heikki Krogerus
     [not found]   ` <1396360976-28657-3-git-send-email-heikki.krogerus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-04-10 16:26     ` Linus Walleij
2014-04-10 16:26       ` Linus Walleij
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   ` Heikki Krogerus
2014-04-01 14:02   ` 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   ` Heikki Krogerus
2014-04-01 14:02 ` [PATCHv3 5/5] net: rfkill: gpio: hard-code the gpio names Heikki Krogerus
2014-04-01 14:02   ` Heikki Krogerus
     [not found]   ` <1396360976-28657-6-git-send-email-heikki.krogerus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-04-10 16:27     ` Linus Walleij
2014-04-10 16:27       ` Linus Walleij
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-02  9:36   ` Alexandre Courbot
     [not found] ` <1396360976-28657-1-git-send-email-heikki.krogerus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-04-08  8:37   ` Johannes Berg
2014-04-08  8:37     ` Johannes Berg
2014-04-08  8:37     ` Johannes Berg
2014-04-09 10:01     ` Heikki Krogerus
2014-04-09 10:01       ` Heikki Krogerus
2014-04-09 15:32       ` Stephen Warren
2014-04-09 15:32         ` Stephen Warren
2014-04-09 15:32         ` Stephen Warren
2014-04-11  7:26         ` Johannes Berg [this message]
2014-04-11  7:26           ` Johannes Berg
2014-04-11  7:32   ` Johannes Berg
2014-04-11  7:32     ` 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=1397201173.4420.0.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arnd@arndb.de \
    --cc=gnurou@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marvin24@gmx.de \
    --cc=netdev@vger.kernel.org \
    --cc=rklein@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=wens@csie.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.