From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: keystone: add TI SCI protocol support for v4.10
Date: Wed, 30 Nov 2016 22:09:04 +0100 [thread overview]
Message-ID: <5602219.0b9asep0uZ@wuerfel> (raw)
In-Reply-To: <6f67f67f-7489-6d62-c2c2-9bba440cfabc@ti.com>
On Wednesday, November 30, 2016 7:59:26 PM CET Tero Kristo wrote:
>
> Thanks Arnd, that looks good to me.
>
> I'll figure out how to add branch description next time when I am going
> to be sending a pull-request directly to you guys.
>
>
You should get a prompt when you sign the tag.
Actually my preference would be for you to forward this to Santosh:
There are a lot of little details to know about the submission
process to for arm-soc, and it's easier for us if fewer people
have to be aware of them.
Arnd
next prev parent reply other threads:[~2016-11-30 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 9:30 [GIT PULL] ARM: keystone: add TI SCI protocol support for v4.10 Tero Kristo
2016-11-28 16:42 ` Tero Kristo
2016-11-30 16:43 ` Arnd Bergmann
2016-11-30 17:59 ` Tero Kristo
2016-11-30 21:09 ` Arnd Bergmann [this message]
2016-11-30 22:47 ` santosh.shilimkar at oracle.com
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=5602219.0b9asep0uZ@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