From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] omap non-urgent fixes for v3.19
Date: Thu, 20 Nov 2014 08:03:52 -0800 [thread overview]
Message-ID: <20141120160352.GN7046@atomide.com> (raw)
In-Reply-To: <201411201046.44262.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [141120 01:48]:
> On Tuesday 11 November 2014, Tony Lindgren wrote:
> > ----------------------------------------------------------------
> > Fixes for omap3 that are not urgent. Mostly to remove unnecessary
> > noise during the boot with pointless errors and warnings.
> >
>
>
> Pulled into next/fixes-non-critical. We didn't have any other patches in there,
> so I started out with -rc3 to avoid the back-merge problem. Any reason why
> you didn't base this on -rc1 like the other branches?
I was probably originally planning to have the dmesg warning
and error fixes merged into omap-for-v3.18/fixes branch and
have that automatically fast forward to -rc3 without rebasing.
No other dependency that I can think of.
Regards,
Tony
next prev parent reply other threads:[~2014-11-20 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pull-1415725783-562282>
2014-11-11 17:14 ` [GIT PULL 2/2] omap prcm clean-up for v3.19 Tony Lindgren
2014-11-11 17:14 ` Tony Lindgren
2014-11-20 9:46 ` [GIT PULL 1/2] omap non-urgent fixes " Arnd Bergmann
2014-11-20 16:03 ` Tony Lindgren [this message]
[not found] ` <pull-1415725783-562282-2>
2014-11-20 11:08 ` [GIT PULL 2/2] omap prcm clean-up " Arnd Bergmann
2014-11-20 15:52 ` Tony Lindgren
2014-11-11 17:14 [GIT PULL 1/2] omap non-urgent fixes " Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2014-11-11 17:14 Tony Lindgren
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=20141120160352.GN7046@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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).