From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] omap device tree changes for v4.4
Date: Thu, 15 Oct 2015 14:04:26 -0700 [thread overview]
Message-ID: <20151015210425.GQ10113@atomide.com> (raw)
In-Reply-To: <8058507.49AsgX8PR9@wuerfel>
* Arnd Bergmann <arnd@arndb.de> [151015 13:40]:
> On Wednesday 14 October 2015 14:38:59 Tony Lindgren wrote:
>
> > Note that this branch is against v4.3-rc4 as that contains critical
> > MMC related fixes to boot with MMC working on most omaps.
>
> While we are lucky this time as I based the branch on -rc4 anyway,
> a nicer way to do this would be to ensure that a fix you want
> to base on is based an older -rc, and then you base your own branch
> on top of that fix, to minimize the number of back-merged patches.
Sure that would be doable too at the cost of a few extra merges.
Regards,
Tony
next parent reply other threads:[~2015-10-15 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8058507.49AsgX8PR9@wuerfel>
2015-10-15 21:04 ` Tony Lindgren [this message]
2015-10-16 9:45 ` [GIT PULL 2/2] omap device tree changes for v4.4 Arnd Bergmann
2015-10-16 14:49 ` Tony Lindgren
2015-10-14 21:38 [GIT PULL 1/2] omap clean-up " Tony Lindgren
2015-10-14 21:38 ` [GIT PULL 2/2] omap device tree changes " 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=20151015210425.GQ10113@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).