linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	linux-iio <linux-iio@vger.kernel.org>
Subject: RE: [PATCH] MAINTAINERS: Remove bouncing email of Beniamin Bia
Date: Wed, 2 Sep 2020 05:56:41 +0000	[thread overview]
Message-ID: <DM6PR03MB441122FDB3323690166C21A0F92F0@DM6PR03MB4411.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAJKOXPd78m-3jMsFRa7ySREDdx+GMZ_YHMG3AcqCHTABLBwqVA@mail.gmail.com>

[yes, I know, bad-email format, but I wanted this to come from my work email]

Apologies also for the delay here. Things pile-up on my side and I defer things a bit.

Talked to Michael Hennerich about this [since he's the more senior contact at Analog].
We can replace the email from Beniamin Bia with Michael's.
Or, we can remove the "Orphan" blocks and just have the catch-all "drivers/iio/*/ad*" cover this driver and others that were upstreamed by Beniamin.

Either option is fine from us.

-----Original Message-----
From: Krzysztof Kozlowski <krzk@kernel.org> 
Sent: Saturday, August 29, 2020 5:58 PM
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Hennerich, Michael <Michael.Hennerich@analog.com>; linux-iio <linux-iio@vger.kernel.org>; Ardelean, Alexandru <alexandru.Ardelean@analog.com>
Subject: Re: [PATCH] MAINTAINERS: Remove bouncing email of Beniamin Bia

On Sat, 29 Aug 2020 at 16:54, Jonathan Cameron <jic23@kernel.org> wrote:

(...)

> > >  ANALOG DEVICES INC AD7091R5 DRIVER
> > > -M:     Beniamin Bia <beniamin.bia@analog.com>
> > >  L:     linux-iio@vger.kernel.org
> > > -S:     Supported
> > > +S:     Orphan
>
> Given it should be covered by the catch all for Analog devices IIO 
> drivers, either we should confirm if it should move to someone else at 
> Analog, or if we should just drop specifically listing this one.
> Listing it as Orphan when they are good at supporting their drivers 
> may give the wrong impression.
>
> +CC Alex to make sure people at Analog notice :)

Sure, good point. I wanted to start the discussion so the interested people might appear.

Best regards,
Krzysztof

  reply	other threads:[~2020-09-02  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 20:17 [PATCH] MAINTAINERS: Remove bouncing email of Beniamin Bia Krzysztof Kozlowski
2020-08-28  8:19 ` Andy Shevchenko
2020-08-29 14:54   ` Jonathan Cameron
2020-08-29 14:58     ` Krzysztof Kozlowski
2020-09-02  5:56       ` Ardelean, Alexandru [this message]
2020-09-02  7:49         ` Andy Shevchenko
2020-09-02 13:26           ` Jonathan Cameron
2020-09-02 13:35             ` Krzysztof Kozlowski
2020-09-02 13:42               ` 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=DM6PR03MB441122FDB3323690166C21A0F92F0@DM6PR03MB4411.namprd03.prod.outlook.com \
    --to=alexandru.ardelean@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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 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).