From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Marcelo Schmitt <marcelo.schmitt@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
dave.hansen@linux.intel.com, andy@kernel.org,
dlechner@baylibre.com, jic23@kernel.org, nuno.sa@analog.com
Subject: Re: [PATCH] MAINTAINERS: Update max30208 maintainership
Date: Sat, 9 Aug 2025 10:51:28 -0300 [thread overview]
Message-ID: <aJdSYIv8_QX0WwdI@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <CAHp75Vc1KgiDUUEjeEKdrSfom6NThPG-383O=sezydnrZLoGqg@mail.gmail.com>
On 08/08, Andy Shevchenko wrote:
> On Fri, Aug 8, 2025 at 9:02 PM Marcelo Schmitt
> <marcelo.schmitt@analog.com> wrote:
> >
> > Update MAX30208 temperature sensor driver maintainer.
> > The previous maintainer's email bounces and no longer works.
> > Also mark the driver as supported.
>
> Reported-by:
> Closes:
>
> ?
Reported-by: Dave Hansen <dave.hansen@linux.intel.com>
Closes: https://lore.kernel.org/linux-iio/20250808174901.4556B33A@davehans-spike.ostc.intel.com/
>
> Otherwise LGTM,
> Reviewed-by: Andy Shevchenko <andy@kernel.org>
>
> ...
>
> > -S: Maintained
> > +S: Supported
>
> Just curious, are you really having this as a day job task?
There is a request for MAX30210 support and so this driver may get extended to
also support that part. Though, even if we end up with a separate driver for
MAX30210, it feel unlikely to me that people lost interest in MAX30208
as that's still in production according to MAX30208's page [1].
[1]: https://www.analog.com/en/products/MAX30208.html
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2025-08-09 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 19:02 Marcelo Schmitt
2025-08-08 21:40 ` Andy Shevchenko
2025-08-09 13:51 ` Marcelo Schmitt [this message]
2025-08-09 13:53 ` Andy Shevchenko
2025-08-09 17:47 ` Jonathan Cameron
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=aJdSYIv8_QX0WwdI@debian-BULLSEYE-live-builder-AMD64 \
--to=marcelo.schmitt1@gmail.com \
--cc=andy.shevchenko@gmail.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.schmitt@analog.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
all inboxes | Powered by JetHome®