Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: linux-next: request to include linux-amlogic tree
Date: Thu, 09 Jun 2016 15:43:03 -0700	[thread overview]
Message-ID: <7h60tidlvs.fsf@baylibre.com> (raw)
In-Reply-To: <20160606010007.6941cc2d@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 6 Jun 2016 01:00:07 +1000")

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Kevin,
>
> On Fri, 3 Jun 2016 14:49:01 -0700 Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Please add the following tree/branch to linux-next.  This is used for
>> the kernel development of the ARM-based Amlogic SoCs:
>> 
>>    git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git
>> for-next
>
> Added from today.

Thanks.

> I assume that this will be merged via the arm-soc tree?

Yes.

> I also have just you as the contact - I can add more contacts if
> that makes sense.

Please also add Carlo Caione <carlo@caione.org>

Kevin

  reply	other threads:[~2016-06-09 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 21:49 linux-next: request to include linux-amlogic tree Kevin Hilman
2016-06-05 15:00 ` Stephen Rothwell
2016-06-09 22:43   ` Kevin Hilman [this message]
2016-06-13  2:03     ` Stephen Rothwell

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=7h60tidlvs.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=linus-amlogic@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