From: Joe Perches <joe@perches.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: 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 02:39:44 -0700 [thread overview]
Message-ID: <1473759584.11006.42.camel@perches.com> (raw)
In-Reply-To: <87poo8taqc.fsf@intel.com>
On Tue, 2016-09-13 at 12:22 +0300, Jani Nikula wrote:
> > 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.
Thanks, checkpatch already does exactly that.
$ ./scripts/checkpatch.pl -git 43efd1edc63534d3a7486a0548c8aedf8b1128d1
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#86:
deleted file mode 100644
total: 0 errors, 1 warnings, 56 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
Commit 43efd1edc635 ("[media] get rid of Documentation/video4linux/lifeview.txt") has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
or another way:
$ git log --stat -p --format=email -1 -M 43efd1edc63534d3a7486a0548c8aedf8b1128d1 | ./scripts/checkpatch.pl -
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#84:
deleted file mode 100644
total: 0 errors, 1 warnings, 56 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
Your patch has style problems, please review.
>
prev parent reply other threads:[~2016-09-13 9:40 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
2016-09-13 9:39 ` Joe Perches [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=1473759584.11006.42.camel@perches.com \
--to=joe@perches.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.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 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.