From: Joe Perches <joe@perches.com>
To: Eric Anholt <eric@anholt.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] staging: bcm2835-v4l2: Apply spelling fixes from checkpatch.
Date: Mon, 30 Jan 2017 17:38:38 -0800 [thread overview]
Message-ID: <1485826718.20550.14.camel@perches.com> (raw)
In-Reply-To: <87inowfh55.fsf@eliezer.anholt.net>
On Mon, 2017-01-30 at 12:05 -0800, Eric Anholt wrote:
> Joe Perches <joe@perches.com> writes:
>
> > On Fri, 2017-01-27 at 13:55 -0800, Eric Anholt wrote:
> > > Generated with checkpatch.pl --fix-inplace and git add -p out of the
> > > results.
> >
> > Maybe another.
> >
> > > diff --git a/drivers/staging/media/platform/bcm2835/mmal-vchiq.c b/drivers/staging/media/platform/bcm2835/mmal-vchiq.c
> >
> > []
> > > @@ -239,7 +239,7 @@ static int bulk_receive(struct vchiq_mmal_instance *instance,
> > > pr_err("buffer list empty trying to submit bulk receive\n");
> > >
> > > /* todo: this is a serious error, we should never have
> > > - * commited a buffer_to_host operation to the mmal
> > > + * committed a buffer_to_host operation to the mmal
> > > * port without the buffer to back it up (underflow
> > > * handling) and there is no obvious way to deal with
> > > * this - how is the mmal servie going to react when
> >
> > Perhaps s/servie/service/ ?
>
> I was trying to restrict this patch to just the fixes from checkpatch.
That's the wrong thing to do if you're fixing
spelling defects. checkpatch is just one mechanism
to identify some, and definitely not all, typos and
spelling defects.
If you fixing, fix. Don't just rely on the brainless
tools, use your decidedly non-mechanical brain.
next prev parent reply other threads:[~2017-01-31 1:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:54 [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver Eric Anholt
2017-01-27 21:54 ` [PATCH 1/6] staging: Import the BCM2835 MMAL-based " Eric Anholt
2017-02-03 18:59 ` Mauro Carvalho Chehab
2017-02-05 22:15 ` Dave Stevenson
2017-02-05 23:13 ` Michael Zoran
2017-02-06 8:30 ` Greg Kroah-Hartman
2017-02-06 12:37 ` Mauro Carvalho Chehab
2017-02-06 15:01 ` Dave Stevenson
2017-02-06 9:08 ` Hans Verkuil
2017-02-06 11:37 ` Dave Stevenson
2017-02-06 12:58 ` Hans Verkuil
2017-02-06 15:21 ` Dave Stevenson
2017-02-06 16:00 ` Hans Verkuil
2017-02-10 9:47 ` Hans Verkuil
2017-02-06 12:59 ` Hans Verkuil
2017-01-27 21:54 ` [PATCH 2/6] staging: bcm2835-v4l2: Update the driver to the current VCHI API Eric Anholt
2017-01-27 21:55 ` [PATCH 3/6] staging: bcm2835-v4l2: Add a build system for the module Eric Anholt
2017-01-29 14:12 ` Michael Zoran
2017-02-03 19:01 ` Mauro Carvalho Chehab
2017-01-27 21:55 ` [PATCH 4/6] staging: bcm2835-v4l2: Add a TODO file for improvements we need Eric Anholt
2017-01-27 21:55 ` [PATCH 5/6] staging: bcm2835-v4l2: Apply many whitespace fixes from checkpatch Eric Anholt
2017-01-27 21:55 ` [PATCH 6/6] staging: bcm2835-v4l2: Apply spelling " Eric Anholt
2017-01-27 22:30 ` Joe Perches
2017-01-30 20:05 ` Eric Anholt
2017-01-31 1:38 ` Joe Perches [this message]
2017-01-31 18:30 ` Eric Anholt
2017-01-31 18:49 ` Joe Perches
2017-03-15 14:01 ` [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver Mauro Carvalho Chehab
2017-03-15 21:50 ` Stefan Wahren
2017-03-15 22:01 ` Eric Anholt
2017-03-16 1:08 ` Mauro Carvalho Chehab
2017-03-16 1:46 ` Michael Zoran
2017-03-16 9:29 ` Mauro Carvalho Chehab
2017-03-18 0:34 ` Eric Anholt
2017-03-19 16:58 ` Mauro Carvalho Chehab
2017-03-19 17:04 ` Michael Zoran
2017-03-20 1:11 ` Mauro Carvalho Chehab
2017-03-20 10:58 ` Mauro Carvalho Chehab
2017-03-20 11:08 ` Michael Zoran
2017-03-20 14:58 ` Mauro Carvalho Chehab
2017-03-20 15:11 ` Michael Zoran
2017-03-20 15:33 ` Mauro Carvalho Chehab
2017-03-20 15:40 ` Michael Zoran
2017-03-20 11:57 ` Stefan Wahren
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=1485826718.20550.14.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@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).