From: Brian Norris <computersforpeace@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jffs2: fix spelling mistake: "requestied" -> "requested"
Date: Wed, 19 Apr 2017 11:36:34 -0700 [thread overview]
Message-ID: <20170419183634.GA20555@google.com> (raw)
In-Reply-To: <20170223003400.9617-1-colin.king@canonical.com>
On Thu, Feb 23, 2017 at 12:34:00AM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> trivial fix to spelling mistake in JFFS2_ERROR message
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> fs/jffs2/readinode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/jffs2/readinode.c b/fs/jffs2/readinode.c
> index 06a71db..40f3fd4 100644
> --- a/fs/jffs2/readinode.c
> +++ b/fs/jffs2/readinode.c
> @@ -1366,7 +1366,7 @@ int jffs2_do_read_inode(struct jffs2_sb_info *c, struct jffs2_inode_info *f,
> jffs2_add_ino_cache(c, f->inocache);
> }
> if (!f->inocache) {
> - JFFS2_ERROR("requestied to read an nonexistent ino %u\n", ino);
> + JFFS2_ERROR("requested to read an nonexistent ino %u\n", ino);
Also:
s/an nonexistent/a nonexisten/
Made that fixup and pushed to l2-mtd.git. Thanks.
Brian
> return -ENOENT;
> }
>
> --
> 2.10.2
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2017-04-19 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 0:34 [PATCH] jffs2: fix spelling mistake: "requestied" -> "requested" Colin King
2017-04-19 18:36 ` Brian Norris [this message]
2017-04-19 18:38 ` Brian Norris
2017-04-19 18:40 ` Colin Ian King
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=20170419183634.GA20555@google.com \
--to=computersforpeace@gmail.com \
--cc=colin.king@canonical.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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