From: Hans de Goede <hdegoede@redhat.com>
To: Lee Jones <lee@kernel.org>,
konstantin@linuxfoundation.org, baocheng.su@siemens.com,
tobias.schaffner@siemens.com, pavel@ucw.cz,
ilpo.jarvinen@linux.intel.com, wim@linux-watchdog.org,
linux@roeck-us.net,
Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
linux-watchdog@vger.kernel.org, felix.moessbauer@siemens.com,
christian.storm@siemens.com, quirin.gylstorff@siemens.com,
chao.zeng@siemens.com
Subject: Re: (subset) [PATCH 1/1] MAINTAINERS: replace bouncing maintainers
Date: Mon, 4 Nov 2024 11:04:47 +0100 [thread overview]
Message-ID: <0f27f32e-bf00-4f9d-a0b6-0625a6dae203@redhat.com> (raw)
In-Reply-To: <173048213838.1966999.11456105703949125929.b4-ty@kernel.org>
Hi Lee,
On 1-Nov-24 6:28 PM, Lee Jones wrote:
> On Mon, 28 Oct 2024 12:23:59 +0100, Benedikt Niedermayr wrote:
>> Since complaints about bouncing maintainers raised [1] we have now a
>> replacement for maintainers that stepped away from their duties.
>>
>> [1] https://www.spinics.net/lists/platform-driver-x86/msg47105.html
>>
>>
>
> Applied, thanks!
>
> [1/1] MAINTAINERS: replace bouncing maintainers
> commit: 64dd44a658065ab5595bbfe2cb4d8fd30c9e34a2
I'm not seeing this on either of:
https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/log/?h=for-leds-next
https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next
?
Note I'm fine with you picking this up, I just want to make sure that
it does not fall through the cracks and drop it from my own patch queue
since it also touches pdx86 MAINTAINERS entries.
Regards,
Hans
next prev parent reply other threads:[~2024-11-04 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 11:23 [PATCH 0/1] MAINTAINERS: replace bouncing maintainers Benedikt Niedermayr
2024-10-28 11:23 ` [PATCH 1/1] " Benedikt Niedermayr
2024-11-01 17:28 ` (subset) " Lee Jones
2024-11-04 10:04 ` Hans de Goede [this message]
2024-11-05 15:55 ` Lee Jones
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=0f27f32e-bf00-4f9d-a0b6-0625a6dae203@redhat.com \
--to=hdegoede@redhat.com \
--cc=baocheng.su@siemens.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=christian.storm@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=quirin.gylstorff@siemens.com \
--cc=tobias.schaffner@siemens.com \
--cc=wim@linux-watchdog.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