From: Arnd Bergmann <arnd@arndb.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] MAINTAINERS: aspeed: Update git tree URL
Date: Fri, 11 Nov 2022 10:23:48 +0100 [thread overview]
Message-ID: <115eb408-1c59-49d6-9fca-c7b56431f472@app.fastmail.com> (raw)
In-Reply-To: <CACPK8XdkXaVXzabFM-g6xQ1CBjZheiP9oFrYk5o1__QR7WBcdw@mail.gmail.com>
On Fri, Nov 11, 2022, at 06:58, Joel Stanley wrote:
> On Thu, 10 Nov 2022 at 01:34, Zev Weiss <zev@bewilderbeest.net> wrote:
>>
>> The description for joel/aspeed.git on git.kernel.org currently says:
>>
>> Old Aspeed tree. Please see joel/bmc.git
>>
>> Let's update MAINTAINERS accordingly.
>>
>> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
>
> Thanks!
>
> Acked-by: Joel Stanley <joel@jms.id.au>
>
> Arnd, does the soc team have a branch for these?
>
I usually treat updates to the MAITNAINERS file as bugfixes and
merge them for the current release, as there is generally no risk
of regressions, and it's better to have up-to-date information
in the release kernel.
Arnd
prev parent reply other threads:[~2022-11-11 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 1:34 [PATCH] MAINTAINERS: aspeed: Update git tree URL Zev Weiss
2022-11-11 5:58 ` Joel Stanley
2022-11-11 9:23 ` Arnd Bergmann [this message]
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=115eb408-1c59-49d6-9fca-c7b56431f472@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-aspeed@lists.ozlabs.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