From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v3.12
Date: Fri, 20 Sep 2013 13:58:27 -0400 [thread overview]
Message-ID: <20130920175827.GC11119@titan.lakedaemon.net> (raw)
In-Reply-To: <CAOesGMi769sEAuf9SaZV_3+HPetDnv-wTb=Ckm1+YxzbZobPGA@mail.gmail.com>
On Fri, Sep 20, 2013 at 10:36:32AM -0700, Olof Johansson wrote:
> On Thu, Sep 19, 2013 at 8:46 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> > Guys,
> >
> > We have a relatively long list of fixes this time around. The two
> > of_node_put()'s were left over from before the merge window (part of
> > mvebu/fixes-non-critical).
> >
> > The two for the Armada XP clocks are to fix booting v3.12-rc1 since the
> > corresponding driver changes were merged at the last minute. These were
> > originally part of mvebu/dt for v3.12, but have since become fixes.
> >
> > The other two just cropped up since v3.12-rc1 dropped.
>
>
> Pulled, thanks.
>
> I noticed a couple of the patches had conflict messages in the patch
> description. They're sometimes useful on merges but less so on patches
> (likely just from needing fixups when cherry-picked?). Not a big deal,
> but something to keep in mind in the future.
Yes, I left them in because I was moving them from one merge window to
another and decided to err on the side of 'more info is better' in case
a bisect came across them.
I can leave them out as well. I have no strong opinion on it.
thx,
Jason.
next prev parent reply other threads:[~2013-09-20 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 3:46 [GIT PULL] ARM: mvebu: fixes for v3.12 Jason Cooper
2013-09-20 17:36 ` Olof Johansson
2013-09-20 17:58 ` Jason Cooper [this message]
2013-10-02 13:51 ` Ezequiel Garcia
2013-10-02 20:09 ` Olof Johansson
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=20130920175827.GC11119@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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