From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] omap fixes for -rc series and merge window
Date: Fri, 7 Oct 2011 21:11:35 +0200 [thread overview]
Message-ID: <201110072111.35418.arnd@arndb.de> (raw)
In-Reply-To: <20111003185237.GI6324@atomide.com>
On Monday 03 October 2011, Tony Lindgren wrote:
> Please pull omap fixes from:
>
> git://github.com/tmlind/linux.git fixes
>
> Out of these the first three commits would be nice to get
> into the -rc series with the first two causing boot issues
> and the musb fixing an ugly warning.
>
> Note however the recent commit message update on the third patch.
> I added Bjarne's SOB to the third patch because of the earlier
> reference.
>
> The last two are mostly cosmetic and not so urgent.
Hi Tony,
I've pulled them all into the fixes branch for now, but I'm not sure
if I still want to send another pull request. If I do, I'll have to
rebase that branch and put some into the next/fixes branch instead
as I already have patches that I don't want to send for 3.1 any
more. Are the patches all fixes against 3.1 only or do some of them
also apply to older releases?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for -rc series and merge window
Date: Fri, 7 Oct 2011 21:11:35 +0200 [thread overview]
Message-ID: <201110072111.35418.arnd@arndb.de> (raw)
In-Reply-To: <20111003185237.GI6324@atomide.com>
On Monday 03 October 2011, Tony Lindgren wrote:
> Please pull omap fixes from:
>
> git://github.com/tmlind/linux.git fixes
>
> Out of these the first three commits would be nice to get
> into the -rc series with the first two causing boot issues
> and the musb fixing an ugly warning.
>
> Note however the recent commit message update on the third patch.
> I added Bjarne's SOB to the third patch because of the earlier
> reference.
>
> The last two are mostly cosmetic and not so urgent.
Hi Tony,
I've pulled them all into the fixes branch for now, but I'm not sure
if I still want to send another pull request. If I do, I'll have to
rebase that branch and put some into the next/fixes branch instead
as I already have patches that I don't want to send for 3.1 any
more. Are the patches all fixes against 3.1 only or do some of them
also apply to older releases?
Arnd
next prev parent reply other threads:[~2011-10-07 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:52 [GIT PULL] omap fixes for -rc series and merge window Tony Lindgren
2011-10-03 18:52 ` Tony Lindgren
2011-10-07 19:11 ` Arnd Bergmann [this message]
2011-10-07 19:11 ` Arnd Bergmann
2011-10-07 19:20 ` Tony Lindgren
2011-10-07 19:20 ` Tony Lindgren
2011-10-07 20:12 ` Arnd Bergmann
2011-10-07 20:12 ` 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=201110072111.35418.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.