mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>, reiserfs-devel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reiserfs: fix spelling mistake "enrty" -> "entry"
Date: Tue, 16 Apr 2019 18:47:36 +0530	[thread overview]
Message-ID: <240c2888-01a9-184f-7f29-eb603bdd36c4@codeaurora.org> (raw)
In-Reply-To: <20190416112549.25175-1-colin.king@canonical.com>


On 4/16/2019 4:55 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are a couple of spelling mistakes, fix these.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>


Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>

Cheers,
-Mukesh

> ---
>   fs/reiserfs/lbalance.c | 2 +-
>   fs/reiserfs/namei.c    | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/reiserfs/lbalance.c b/fs/reiserfs/lbalance.c
> index f5cebd70d903..e7cebd05a882 100644
> --- a/fs/reiserfs/lbalance.c
> +++ b/fs/reiserfs/lbalance.c
> @@ -1164,7 +1164,7 @@ void leaf_cut_from_buffer(struct buffer_info *bi, int cut_item_num,
>   		if (pos_in_item == 0) {
>   			/* change key */
>   			RFALSE(cut_item_num,
> -			       "when 0-th enrty of item is cut, that item must be first in the node, not %d-th",
> +			       "when 0-th entry of item is cut, that item must be first in the node, not %d-th",
>   			       cut_item_num);
>   			/* change item key by key of first entry in the item */
>   			set_le_ih_k_offset(ih, deh_offset(B_I_DEH(bh, ih)));
> diff --git a/fs/reiserfs/namei.c b/fs/reiserfs/namei.c
> index 97f3fc4fdd79..c97c36b4a31c 100644
> --- a/fs/reiserfs/namei.c
> +++ b/fs/reiserfs/namei.c
> @@ -536,7 +536,7 @@ static int reiserfs_add_entry(struct reiserfs_transaction_handle *th,
>   		pathrelse(&path);
>   		return -EBUSY;
>   	}
> -	/* adjust offset of directory enrty */
> +	/* adjust offset of directory entry */
>   	put_deh_offset(deh, SET_GENERATION_NUMBER(deh_offset(deh), gen_number));
>   	set_cpu_key_k_offset(&entry_key, deh_offset(deh));
>   

      reply	other threads:[~2019-04-16 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 11:25 Colin King
2019-04-16 13:17 ` Mukesh Ojha [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=240c2888-01a9-184f-7f29-eb603bdd36c4@codeaurora.org \
    --to=mojha@codeaurora.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@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 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®