From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Joe Perches <joe@perches.com>,
Eugen Hristev <eugen.hristev@microchip.com>,
Josh Wu <josh.wu@atmel.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove stale file entry for the Atmel ISI driver
Date: Mon, 1 Oct 2018 13:51:01 -0300 [thread overview]
Message-ID: <20181001135101.536b4c22@coco.lan> (raw)
In-Reply-To: <7150c1de00db05ec3c1a53611c156fb823d7f345.camel@perches.com>
Em Sun, 30 Sep 2018 02:40:35 -0700
Joe Perches <joe@perches.com> escreveu:
> On Sun, 2018-09-30 at 06:30 -0300, Mauro Carvalho Chehab wrote:
> > Em Sun, 30 Sep 2018 09:54:48 +0300
> > Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> >
> > > include/media/atmel-isi got removed three years ago without the
> > > MAINTAINERS file being updated. Remove the stale entry.
> > >
> > > Fixes: 40a78f36fc92 ("[media] v4l: atmel-isi: Remove support for platform data")
> > > Reported-by: Joe Perches <joe@perches.com>
> > > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > ---
> > > MAINTAINERS | 1 -
> > > 1 file changed, 1 deletion(-)
> > >
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > > @@ -2497,7 +2497,6 @@ M: Ludovic Desroches <ludovic.desroches@microchip.com>
> > > L: linux-media@vger.kernel.org
> > > S: Supported
> > > F: drivers/media/platform/atmel/atmel-isi.c
> > > -F: include/media/atmel-isi.h
> >
> > I guess the right fix would be to replace it by:
> >
> > F: drivers/media/platform/atmel/atmel-isi.h
>
> Or replace both F entries with:
>
> F: drivers/media/platform/atmel/atmel-isi.*
>
> Or combine the 2 MICROCHIP sections into one
>
> MICROCHIP ISC DRIVER
> M: Eugen Hristev <eugen.hristev@microchip.com>
> L: linux-media@vger.kernel.org
> S: Supported
> F: drivers/media/platform/atmel/atmel-isc.c
> F: drivers/media/platform/atmel/atmel-isc-regs.h
> F: devicetree/bindings/media/atmel-isc.txt
>
> MICROCHIP ISI DRIVER
> M: Eugen Hristev <eugen.hristev@microchip.com>
> L: linux-media@vger.kernel.org
> S: Supported
> F: drivers/media/platform/atmel/atmel-isi.c
> F: include/media/atmel-isi.h
>
> and maybe use something like:
>
> MICROCHIP MEDIA DRIVERS
> M: Eugen Hristev <eugen.hristev@microchip.com>
> L:
> linux-media@vger.kernel.org
> S: Supported
> F: drivers/media/platform/atmel/
> F: devicetree/bindings/media/atmel-isc.txt
Yeah, combining both of them seems a good alternative to me.
Eugen/Ludovic/Josh,
Comments?
Regards,
Mauro
>
>
Thanks,
Mauro
next prev parent reply other threads:[~2018-10-01 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 6:54 [PATCH] MAINTAINERS: Remove stale file entry for the Atmel ISI driver Laurent Pinchart
2018-09-30 9:30 ` Mauro Carvalho Chehab
2018-09-30 9:40 ` Joe Perches
2018-10-01 16:51 ` Mauro Carvalho Chehab [this message]
2018-10-02 6:15 ` Eugen Hristev
2018-10-02 6:35 ` Ludovic Desroches
2018-10-04 18:45 ` Mauro Carvalho Chehab
2018-10-04 20:06 ` Laurent Pinchart
2018-10-05 18:41 ` Mauro Carvalho Chehab
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=20181001135101.536b4c22@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=joe@perches.com \
--cc=josh.wu@atmel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ludovic.desroches@microchip.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