From: Randy Dunlap <randy.dunlap@oracle.com>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, trivial@kernel.org
Subject: Re: [Patch] Trivial: fix "*er then" typos
Date: Fri, 22 Aug 2008 14:23:00 -0700 [thread overview]
Message-ID: <20080822142300.6654e4dd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080822160222.GF3053@hack.voiplan.pt>
On Fri, 22 Aug 2008 17:02:22 +0100 WANG Cong wrote:
>
> Obviously, these "*er then" should be "*er than".
>
> Signed-off-by: WANG Cong <wangcong@zeuux.org>
> Cc: trivial@kernel.org
Mostly good...
> diff --git a/drivers/media/video/usbvideo/ibmcam.c b/drivers/media/video/usbvideo/ibmcam.c
> index 59166b7..caf4306 100644
> --- a/drivers/media/video/usbvideo/ibmcam.c
> +++ b/drivers/media/video/usbvideo/ibmcam.c
> @@ -488,7 +488,7 @@ static enum ParseState ibmcam_parse_lines(
> * Now we are sure that entire line (representing all 'scanLength'
> * pixels from the camera) is available in the buffer. We
> * start copying the line left-aligned to the V4L buffer.
> - * If the camera line is shorter then we should pad the V4L
> + * If the camera line is shorter than we should pad the V4L
This one should remain as "then".
> * buffer with something (black) to complete the line.
> */
> assert(frame->data != NULL);
> @@ -703,7 +703,7 @@ static enum ParseState ibmcam_model2_320x240_parse_lines(
> * pixels from the camera) is available in the scratch buffer. We
> * start copying the line left-aligned to the V4L buffer (which
> * might be larger - not smaller, hopefully). If the camera
> - * line is shorter then we should pad the V4L buffer with something
> + * line is shorter than we should pad the V4L buffer with something
ditto.
> * (black in this case) to complete the line.
> */
> f = frame->data + (v4l_linesize * frame->curline);
> diff --git a/fs/ubifs/shrinker.c b/fs/ubifs/shrinker.c
> index f248533..bfe0920 100644
> --- a/fs/ubifs/shrinker.c
> +++ b/fs/ubifs/shrinker.c
> @@ -65,7 +65,7 @@ atomic_long_t ubifs_clean_zn_cnt;
> * @contention: if any contention, this is set to %1
> *
> * This function traverses TNC tree and frees clean znodes. It does not free
> - * clean znodes which younger then @age. Returns number of freed znodes.
> + * clean znodes which younger than @age. Returns number of freed znodes.
which are younger
> */
> static int shrink_tnc(struct ubifs_info *c, int nr, int age, int *contention)
> {
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
next prev parent reply other threads:[~2008-08-22 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 16:02 WANG Cong
2008-08-22 21:23 ` Randy Dunlap [this message]
2008-08-25 11:05 ` WANG Cong
2008-08-25 11:21 ` [Patch] Trivial: fix "*er then" typos and more WANG Cong
2008-08-27 22:08 ` Randy Dunlap
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=20080822142300.6654e4dd.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®