From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.15 0/2] Fixup IOMMU list in MAINTAINERS
Date: Wed, 23 Aug 2023 11:05:37 -0700 [thread overview]
Message-ID: <20d49c8d-f99e-248a-2122-8a5877de5171@linux.microsoft.com> (raw)
In-Reply-To: <2023082353-renderer-hypocrite-5935@gregkh>
On 8/23/23 11:01, Greg KH wrote:
> On Wed, Aug 23, 2023 at 05:57:04PM +0000, Easwar Hariharan wrote:
>> The IOMMU list has moved and emails to the old list bounce. Bring stable
>> in alignment with mainline.
>>
>> Joerg Roedel (1):
>> MAINTAINERS: Remove iommu@lists.linux-foundation.org
>
> Who uses MAINTAINERS for submitting new patches? No one should,
> otherwise we would be syncing these types of changes backwards all the
> time :(
>
> So why is this needed?
>
> confused,
>
> greg k-h
I did, here[0] with cc-cmd=scripts/get_maintainer.pl. :) I'll keep the
fact that I'm not supposed to in mind for the future. :)
Thanks,
Easwar
[0]:
https://lore.kernel.org/stable/20230802170227.1590187-1-eahariha@linux.microsoft.com/T/#t
next prev parent reply other threads:[~2023-08-23 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 17:57 [PATCH 5.15 0/2] Fixup IOMMU list in MAINTAINERS Easwar Hariharan
2023-08-23 17:57 ` [PATCH 5.15 1/2] MAINTAINERS: update maintainer list of DMA MAPPING BENCHMARK Easwar Hariharan
2023-08-23 17:57 ` [PATCH 5.15 2/2] MAINTAINERS: Remove iommu@lists.linux-foundation.org Easwar Hariharan
2023-08-23 18:01 ` [PATCH 5.15 0/2] Fixup IOMMU list in MAINTAINERS Greg KH
2023-08-23 18:05 ` Easwar Hariharan [this message]
2023-08-23 18:35 ` Greg KH
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=20d49c8d-f99e-248a-2122-8a5877de5171@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.