All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] ARM: cleanups of io includes
Date: Wed, 28 Mar 2012 12:34:10 +0000	[thread overview]
Message-ID: <201203281234.10632.arnd@arndb.de> (raw)
In-Reply-To: <CAOesGMjwZOON9kFNvaEq8QhSvjAgsJT_J1Ysb9-AbePd6g+-rQ@mail.gmail.com>

On Wednesday 28 March 2012, Olof Johansson wrote:
> If you prefer to let it sit in linux-next for a day or two before
> going in, that's fine. But I verified that the original build problem
> introduced was fixed before I sent it out.
> 
> Unfortunately, PXA is also broken due to the regulator changes
> mentioned in the above referenced mail, which is already upstream and
> unrelated to the changes in this branch.
> 
> Linus; the rest of the pull requests should be OK to go in
> independently of this, so please go ahead with those if you don't
> mind. The only changes to those branches in the last few days is the
> merge resolution I did to the drivers2 branch/tag.

Yes, sounds good. I've also verified that none of the other branches
depends on this one.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Olof Johansson <olof@lixom.net>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 1/5] ARM: cleanups of io includes
Date: Wed, 28 Mar 2012 12:34:10 +0000	[thread overview]
Message-ID: <201203281234.10632.arnd@arndb.de> (raw)
In-Reply-To: <CAOesGMjwZOON9kFNvaEq8QhSvjAgsJT_J1Ysb9-AbePd6g+-rQ@mail.gmail.com>

On Wednesday 28 March 2012, Olof Johansson wrote:
> If you prefer to let it sit in linux-next for a day or two before
> going in, that's fine. But I verified that the original build problem
> introduced was fixed before I sent it out.
> 
> Unfortunately, PXA is also broken due to the regulator changes
> mentioned in the above referenced mail, which is already upstream and
> unrelated to the changes in this branch.
> 
> Linus; the rest of the pull requests should be OK to go in
> independently of this, so please go ahead with those if you don't
> mind. The only changes to those branches in the last few days is the
> merge resolution I did to the drivers2 branch/tag.

Yes, sounds good. I've also verified that none of the other branches
depends on this one.

	Arnd

  reply	other threads:[~2012-03-28 12:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  7:13 [GIT PULL 0/5] Second batch of arm-soc changes Olof Johansson
2012-03-28  7:13 ` Olof Johansson
2012-03-28  7:13 ` [GIT PULL 1/5] ARM: cleanups of io includes Olof Johansson
2012-03-28  8:25   ` Russell King - ARM Linux
2012-03-28  8:25     ` Russell King - ARM Linux
2012-03-28  9:05     ` Olof Johansson
2012-03-28  9:05       ` Olof Johansson
2012-03-28 12:34       ` Arnd Bergmann [this message]
2012-03-28 12:34         ` Arnd Bergmann
2012-03-28 19:28       ` Russell King - ARM Linux
2012-03-28 19:28         ` Russell King - ARM Linux
2012-03-30  0:09         ` Linus Torvalds
2012-03-30  0:09           ` Linus Torvalds
2012-03-30  0:27           ` Olof Johansson
2012-03-30  0:27             ` Olof Johansson
2012-03-30  0:34             ` Olof Johansson
2012-03-30  0:34               ` Olof Johansson
2012-03-28  7:13 ` [GIT PULL 2/5] ARM: More SoC driver updates Olof Johansson
2012-03-28  7:14 ` [GIT PULL 3/5] ARM: More SoC support updates Olof Johansson
2012-03-28  7:14 ` [GIT PULL 4/5] ARM: More device tree " Olof Johansson
2012-03-28 19:36   ` Linus Torvalds
2012-03-28 19:36     ` Linus Torvalds
2012-03-28 20:58     ` Arnd Bergmann
2012-03-28 20:58       ` Arnd Bergmann
2012-03-28  7:14 ` [GIT PULL 5/5] drivers/clk: common clock framework Olof Johansson
2012-03-28 14:26 ` [GIT PULL 0/5] Second batch of arm-soc changes Rob Herring
2012-03-28 14:26   ` Rob Herring
2012-03-28 14:59   ` Arnd Bergmann
2012-03-28 14:59     ` Arnd Bergmann

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=201203281234.10632.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 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.