From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Joe Perches <joe@perches.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: Updating MAINTAINERS and Documentation/video4linux F: patterns
Date: Tue, 13 Sep 2016 06:36:25 -0300 [thread overview]
Message-ID: <20160913063625.5fbd6584@vento.lan> (raw)
In-Reply-To: <87poo8taqc.fsf@intel.com>
Em Tue, 13 Sep 2016 12:22:51 +0300
Jani Nikula <jani.nikula@linux.intel.com> escreveu:
> On Sat, 10 Sep 2016, Joe Perches <joe@perches.com> wrote:
> > After all the moving of video4linux Documentation file locations
> > around and converting .txt files to .rst, can you please update
> > the appropriate MAINTAINERS sections and F: patterns?
>
> Hmm, for patches doing rename/create/delete, checkpatch could look at
> MAINTAINERS and remind the user if a MAINTAINERS update is needed.
Good point. Checkpatch does that already, as I remember from time to
time I receive such warnings when a new driver is created, renamed or
removed. I didn't notice it on my patchset though.
Perhaps it excludes Documentation/ from the check logic.
Regards,
Mauro
PS.: In the specific case of media docs, I submitted a patch
yesterday addressing those renames.
next prev parent reply other threads:[~2016-09-13 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 23:29 Updating MAINTAINERS and Documentation/video4linux F: patterns Joe Perches
2016-09-13 9:22 ` Jani Nikula
2016-09-13 9:36 ` Mauro Carvalho Chehab [this message]
2016-09-13 9:39 ` Joe Perches
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=20160913063625.5fbd6584@vento.lan \
--to=mchehab@s-opensource.com \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-doc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.