linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v3.2-rc2
Date: Wed, 23 Nov 2011 15:11:27 -0800	[thread overview]
Message-ID: <20111123231127.GJ31337@atomide.com> (raw)
In-Reply-To: <21329850.CZjvquqxJn@wuerfel>

* Arnd Bergmann <arnd@arndb.de> [111123 13:47]:
> On Wednesday 23 November 2011 14:03:58 Tony Lindgren wrote:
> > 
> > The earlier patches are based on the earlier fixes (while waiting
> > for them to get merged). So that's certainly not a random commit.
> > Or at least was not at that time  I can rebase those too anyways
> > now that the earlier fixes are merged.
> 
> No need to do that unless you are rebasing them anyway. IMHO
> it's fine if you have all your bug fixes in one branch based
> on the previous bug fixes you sent, but it's of course also
> fine to start a fresh branch for each pull request.
> 
> In general, I would recommend not rebasing when you have the
> choice, because that means your patches are not as well tested.

Well I can keep only four of them because of the pull on a random
commit. Looks like four of them apply to v3.1, will send them
off to stable at vger.kernel.org and send you two new pull requests.

Tony

  reply	other threads:[~2011-11-23 23:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 19:44 [GIT PULL] omap fixes for v3.2-rc2 Tony Lindgren
2011-11-23 21:15 ` Arnd Bergmann
2011-11-23 22:03   ` Tony Lindgren
2011-11-23 22:22     ` Arnd Bergmann
2011-11-23 23:11       ` Tony Lindgren [this message]
2011-11-24  0:42         ` 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=20111123231127.GJ31337@atomide.com \
    --to=tony@atomide.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).