public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Carlo Caione <carlo@caione.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	linux-amlogic@lists.infradead.org,
	Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: updated Amlogic repo used for linux-next
Date: Fri, 28 May 2021 11:32:01 -0700	[thread overview]
Message-ID: <7h8s3yso9q.fsf@baylibre.com> (raw)
In-Reply-To: <20210528083821.72dda431@canb.auug.org.au>

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

> Hi Kevin,
>
> On Thu, 27 May 2021 11:36:50 -0700 Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Please update the tree used for Amlogic SoC kernel development
>> (suggested patch below[1].)
>> 
>> We've switched to a maintainer group for this tree which is now
>> co-maintained by myself and Neil (cc'd)
>> 
>> [1]
>> diff --git a/Next/Trees b/Next/Trees
>> index 2d22ca1d2911..1794b9144f3a 100644
>> --- a/Next/Trees
>> +++ b/Next/Trees
>> @@ -103,7 +103,7 @@ arm64		git	git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co
>>  arm-perf		git	git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git#for-next/perf
>>  arm-soc		git	git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#for-next
>>  actions		git	git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git#for-next
>> -amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next
>> +amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git#for-next
>>  aspeed		git	git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git#for-next
>>  at91		git	git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
>>  drivers-memory	git	https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git#for-next
>
> I have updated the tree URL and added Neil as a contact.

Thank you.

> I still have Carlo (cc'd) listed as a contact, is that correct?

You can drop Carlo.  He stepped down as co-maintainer awhile back.

Thanks,

Kevin

  reply	other threads:[~2021-05-28 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 18:36 updated Amlogic repo used for linux-next Kevin Hilman
2021-05-27 22:38 ` Stephen Rothwell
2021-05-28 18:32   ` Kevin Hilman [this message]
2021-05-28 21:59     ` Stephen Rothwell
2021-05-31  7:18   ` Neil Armstrong

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=7h8s3yso9q.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=carlo@caione.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=sfr@canb.auug.org.au \
    /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