From: Dave Hansen <dave.hansen@intel.com>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>,
linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH] MAINTAINERS: Update max30208 for bouncing maintainer
Date: Fri, 8 Aug 2025 11:35:05 -0700 [thread overview]
Message-ID: <5975a032-af5c-49e9-9c85-9fed941658fd@intel.com> (raw)
In-Reply-To: <aJZBvi2cXN6LZEFb@debian-BULLSEYE-live-builder-AMD64>
On 8/8/25 11:28, Marcelo Schmitt wrote:
> I'd like to take maintainership of that one.
Great! So I think the best thing for you to do would be send a fresh
patch to the same folks that I sent my patch, along with a proper
changelog and Signed-off-by: you.
prev parent reply other threads:[~2025-08-08 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 17:49 [PATCH] MAINTAINERS: Update max30208 for bouncing maintainer Dave Hansen
2025-08-08 18:28 ` Marcelo Schmitt
2025-08-08 18:35 ` Dave Hansen [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=5975a032-af5c-49e9-9c85-9fed941658fd@intel.com \
--to=dave.hansen@intel.com \
--cc=andy@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=nuno.sa@analog.com \
/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 NNTP newsgroup(s).