From: Linus Torvalds <torvalds@linux-foundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: virtualization@lists.linux.dev, acpica-devel@lists.linux.dev,
bridge@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update lists.linuxfoundation.org migrated lists
Date: Wed, 8 Nov 2023 12:45:17 -0800 [thread overview]
Message-ID: <CAHk-=wg7TrK=kb9ZTEh4Cd+AOkY+ZBvvARsPy-xHyugU5eKMiQ@mail.gmail.com> (raw)
In-Reply-To: <20231107-lists-lf-org-move-v1-1-b19b499a93fb@linuxfoundation.org>
On Tue, 7 Nov 2023 at 12:00, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> Normally, these would go through individual subsystems, but it's one of
> those one-off changes that don't really bubble up in a natural way. If
> you would like to pull this in through someone else's tree, please let
> me know to whom I should send this instead.
Oh, I still take patches, and this is fine and makes sense. Applied,
Linus
prev parent reply other threads:[~2023-11-08 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 20:00 [PATCH] MAINTAINERS: update lists.linuxfoundation.org migrated lists Konstantin Ryabitsev
2023-11-08 20:45 ` Linus Torvalds [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='CAHk-=wg7TrK=kb9ZTEh4Cd+AOkY+ZBvvARsPy-xHyugU5eKMiQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=acpica-devel@lists.linux.dev \
--cc=bridge@lists.linux.dev \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).