From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [Request pull] mvebu/fixes #3
Date: Fri, 23 Jan 2015 14:50:39 -0800 [thread overview]
Message-ID: <CAOesGMiHAOOuCohfD2cV6eywGFjJK580STNAiDo9nahF-twuBQ@mail.gmail.com> (raw)
In-Reply-To: <20150123224415.GI21727@lunn.ch>
On Fri, Jan 23, 2015 at 2:44 PM, Andrew Lunn <andrew@lunn.ch> wrote:
>> > mvebu fixes for 3.19. (Part 4)
>>
>> Subject says #3, tag says part 4. Hmm?
>
> Subject is wrong. This is #4.
>
> You seemed to of missed #3. At least i've not seen an email said you
> have pulled it. Could you please look back in your archive to Jan 17th
> for the real #3.
The one with 8f1e8ee28660018a935c7576b9af8ffe1feab54c in it? It's
merged, I merged it on the 18th.
-Olof
next prev parent reply other threads:[~2015-01-23 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 0:40 [Request pull] mvebu/fixes #3 Andrew Lunn
2015-01-23 22:10 ` Olof Johansson
2015-01-23 22:44 ` Andrew Lunn
2015-01-23 22:50 ` Olof Johansson [this message]
2015-01-23 22:51 ` Andrew Lunn
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=CAOesGMiHAOOuCohfD2cV6eywGFjJK580STNAiDo9nahF-twuBQ@mail.gmail.com \
--to=olof@lixom.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;
as well as URLs for NNTP newsgroup(s).