public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] bitmap: Fix a typo ("identify map")
Date: Mon, 14 Aug 2023 11:27:20 -0700	[thread overview]
Message-ID: <ZNpyCGCjcSz940Zl@yury-ThinkPad> (raw)
In-Reply-To: <20230814173708.1746905-1-j.neuschaefer@gmx.net>

On Mon, Aug 14, 2023 at 07:37:08PM +0200, Jonathan Neuschäfer wrote:
> A map in which each element is mapped to itself is called an "identity
> map".
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Applied in bitmap-for-next. Thanks!

> ---
> 
> v2:
> - Add R-b
> ---
>  lib/bitmap.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/bitmap.c b/lib/bitmap.c
> index ddb31015e38ae..24284caadbcc6 100644
> --- a/lib/bitmap.c
> +++ b/lib/bitmap.c
> @@ -988,7 +988,7 @@ static int bitmap_pos_to_ord(const unsigned long *buf, unsigned int pos, unsigne
>   * to @dst.
>   *
>   * The positions of unset bits in @old are mapped to themselves
> - * (the identify map).
> + * (the identity map).
>   *
>   * Apply the above specified mapping to @src, placing the result in
>   * @dst, clearing any bits previously set in @dst.
> @@ -1037,7 +1037,7 @@ EXPORT_SYMBOL(bitmap_remap);
>   * the position of the m-th set bit in @new, where m == n % w.
>   *
>   * The positions of unset bits in @old are mapped to themselves
> - * (the identify map).
> + * (the identity map).
>   *
>   * Apply the above specified mapping to bit position @oldbit, returning
>   * the new bit position.
> --
> 2.40.1

      reply	other threads:[~2023-08-14 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 17:37 [PATCH v2] bitmap: Fix a typo ("identify map") Jonathan Neuschäfer
2023-08-14 18:27 ` Yury Norov [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=ZNpyCGCjcSz940Zl@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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