From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Kozlov Sergey <serjk@netup.ru>,
linux-media@vger.kernel.org, aospan1@gmail.com,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 1/5] [media] horus3a: Sony Horus3A DVB-S/S2 tuner driver
Date: Tue, 17 Mar 2015 23:55:08 -0300 [thread overview]
Message-ID: <20150317235508.21abc274@recife.lan> (raw)
In-Reply-To: <5508C2C8.4090407@iki.fi>
Em Wed, 18 Mar 2015 02:11:52 +0200
Antti Palosaari <crope@iki.fi> escreveu:
> On 03/05/2015 10:54 AM, Mauro Carvalho Chehab wrote:
> > Em Mon, 02 Feb 2015 12:22:32 +0300
> > Kozlov Sergey <serjk@netup.ru> escreveu:
>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index ddb9ac8..a3a1767 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -4365,6 +4365,15 @@ W: http://linuxtv.org
> >> S: Odd Fixes
> >> F: drivers/media/usb/hdpvr/
> >>
> >> +HORUS3A MEDIA DRIVER
> >
> > Not a big issue, but could you please rename it to:
> > MEDIA DRIVERS FOR HORUS3A
> >
> > We're trying to better organize the media entries at MAINTAINERS, at
> > least for the new drivers.
>
> What the *ell is that new rule? MAINTAINERS file clearly says entries
> should be alphabetical order,
Yes, whatever name is given, the MAINTAINERS entries should be in
alphabetical order.
> but on the other-hand there seems to be
> PCI and ARM specific stuff already grouped. Is that some new way?
Yeah, there is a tendency to try to group the entries on a similar
way on other subsystems.
So, Laurent proposed to do that for new drivers.
That's said, it makes no sense to rename the existing entries, as such
patch would likely make lots of people unhappy by causing a great number
of merge conflicts, but, as grouping the new entries seem to help
some people that manually looks at MAINTAINERS, it sounds a good
idea to do it for new drivers.
One advantage of grouping the entries for new drivers is that this
reduces the merge conflicts at MAINTAINERS, as it reduces the risk of
two subsystems to touch at the same part of the file.
Regards,
Mauro
prev parent reply other threads:[~2015-03-18 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 9:22 [PATCH 1/5] [media] horus3a: Sony Horus3A DVB-S/S2 tuner driver Kozlov Sergey
2015-03-05 8:54 ` Mauro Carvalho Chehab
2015-03-18 0:11 ` Antti Palosaari
2015-03-18 2:55 ` Mauro Carvalho Chehab [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=20150317235508.21abc274@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=aospan1@gmail.com \
--cc=crope@iki.fi \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=serjk@netup.ru \
/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).