linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation
Date: Thu, 19 Sep 2019 06:52:12 -0300	[thread overview]
Message-ID: <20190919065212.112af4be@coco.lan> (raw)
In-Reply-To: <20190919065447.GF2959@kadam>

Em Thu, 19 Sep 2019 09:56:44 +0300
Dan Carpenter <dan.carpenter@oracle.com> escreveu:

> On Wed, Sep 18, 2019 at 10:57:28AM -0300, Mauro Carvalho Chehab wrote:
> > > > +Patches for the media subsystem should be sent to the media mailing list
> > > > +at linux-media@vger.kernel.org as plain text only e-mail. Emails with
> > > > +HTML will be automatically rejected by the mail server. There's no need
> > > > +to copy the maintainer or sub-maintainer(s).    
> > > 
> > > There's too much traffic on mailing lists for me to follow everything, I
> > > much prefer being CC'ed on patches.  
> > 
> > Well, by using patchwork, the best is to take a look on it at least for
> > the patches that you're interested. You could script something using
> > pwclient in order to make it easier.
> > 
> > Anyway, not sure if the other sub-maintainers see the same way. From my side,
> > I prefer not to be c/c, as this is just more noise, as I just rely on
> > patchwork for media patches. What about changing this to:
> > 
> > 	Patches for the media subsystem should be sent to the media mailing list
> > 	at linux-media@vger.kernel.org as plain text only e-mail. Emails with
> > 	HTML will be automatically rejected by the mail server. It could be wise 
> > 	to also copy the sub-maintainer(s).  
> 
> The documentation should say "Use get_maintainer.pl" and do what it
> says.  Everything else is too complicated.

Works for me.

> Occasionally staging maintainers will complain that they aren't CC'd
> even though the staging/driver/README says to CC them and I am tell them
> "No, the responsibility is for you to add yourself to MAINTAINERS.  It
> doesn't matter what the documentation says, you messed up so you need to
> stop getting annoyed with newbies for not reading the documentation when
> it's your fault you weren't CC'd."
> 
> When I sent a patch, I use get_maintainer.pl then I add whoever the
> wrote the commit from the Fixes tag.  Then I remove Colin King and Kees
> Cook from the CC list because they worked all over the tree and I know
> them.  I also normally remove LKML if there is another mailing list but
> at least one subsystem uses LKML for patchwork so this isn't safe.

I use get_maintainer.pl myself, but when submitting some patches
(like documentation ones), I need to manually clean the list, as
it is not uncommon to have a really long c/c list.

> 
> So the safest instructions are "Use get_matainer.pl and add the person
> who wrote the commit in the Fixes tag".
> 
> regards,
> dan carpenter
> 
> 
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss



Thanks,
Mauro

  parent reply	other threads:[~2019-09-19  9:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com>
2019-09-13 16:19 ` [PATCH] media: add a subsystem profile documentation Mauro Carvalho Chehab
2019-09-17  3:35   ` single maintainer profile directory (was Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation) Kees Cook
2019-09-17 13:28     ` Mauro Carvalho Chehab
2019-09-17 16:33       ` Kees Cook
2019-09-18 11:23         ` [Ksummit-discuss] single maintainer profile directory (was " Mauro Carvalho Chehab
2019-09-18 17:39           ` Kees Cook
2019-09-18 18:35             ` Mauro Carvalho Chehab
2019-09-21 19:13           ` Jonathan Corbet
2019-09-21 19:45             ` Mauro Carvalho Chehab
2019-09-23 22:45             ` Kees Cook
2019-09-18 12:36   ` [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation Laurent Pinchart
2019-09-18 13:57     ` Mauro Carvalho Chehab
2019-09-18 17:27       ` Laurent Pinchart
2019-09-18 18:48         ` Mauro Carvalho Chehab
2019-09-19  7:08           ` Dan Carpenter
2019-09-20  5:29             ` Joe Perches
2019-09-20 14:09               ` Daniel Vetter
2019-09-19  6:56       ` Dan Carpenter
2019-09-19  7:22         ` Geert Uytterhoeven
2019-09-19  8:49           ` Jani Nikula
2019-09-19  8:58             ` Geert Uytterhoeven
2019-09-19  9:52               ` Jani Nikula
2019-09-20 14:53           ` Laurent Pinchart
2019-09-20 14:59             ` Doug Anderson
2019-09-21  8:56               ` Jani Nikula
2019-09-23 15:58                 ` Doug Anderson
2019-09-23 16:04                   ` Jonathan Corbet
2019-09-19  9:52         ` Mauro Carvalho Chehab [this message]
2019-09-25 17:13         ` Joe Perches
2019-09-25 18:40           ` Kees Cook
2019-09-26 15:14             ` Joe Perches
2019-09-26 15:53               ` Kees Cook
2019-09-26 16:02                 ` Joe Perches
2019-09-26 16:24                   ` Kees Cook
2019-09-26 10:25           ` Geert Uytterhoeven
2019-09-18 13:59     ` [PATCH v2] " Mauro Carvalho Chehab
2019-09-18 14:07       ` André Almeida
2019-09-18 14:11         ` 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=20190919065212.112af4be@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-media@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).