From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL REQUEST] aspeed arch changes for 4.7
Date: Mon, 09 May 2016 14:58:59 +0200 [thread overview]
Message-ID: <4204804.jrcJPq4h9P@wuerfel> (raw)
In-Reply-To: <CACPK8Xd6i0Fh79YBmF3FO--vfO+hEUxfTsTDyDxqUushhScRwg@mail.gmail.com>
On Monday 09 May 2016 22:11:43 Joel Stanley wrote:
> On Mon, May 9, 2016 at 9:59 PM, Joel Stanley <joel@jms.id.au> wrote:
> > Hello,
> >
> > This is the initial pull request for the Aspeed BMC SoCs.
>
> As you can see, this being my first time and all, I chose to use the
> "PULL REQUEST" tag instead of the more traditional "GIT PULL".
>
> I'll be sure to get it correct next time.
No worries, this sticks out enough in my inbox so I don't miss it.
I'm planning to merge the arch/arm/ bits today or tomorrow, hopefully
all the drivers can also make it in time for the merge window.
Arnd
next prev parent reply other threads:[~2016-05-09 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 12:29 [PULL REQUEST] aspeed arch changes for 4.7 Joel Stanley
2016-05-09 12:41 ` Joel Stanley
2016-05-09 12:58 ` Arnd Bergmann [this message]
2016-05-09 14:16 ` Arnd Bergmann
2016-05-09 14:34 ` Joel Stanley
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=4204804.jrcJPq4h9P@wuerfel \
--to=arnd@arndb.de \
--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