mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Sander Vanheule <sander@svanheule.net>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] cpumask: UP optimisation fixes follow-up
Date: Tue, 9 Aug 2022 21:55:10 -0700	[thread overview]
Message-ID: <YvM6LjJCMK4ZKrxK@yury-laptop> (raw)
In-Reply-To: <cover.1660066581.git.sander@svanheule.net>

On Tue, Aug 09, 2022 at 07:36:32PM +0200, Sander Vanheule wrote:
> As an older version of the UP optimisation fixes was merged, not all
> review feedback has been implemented.  These patches implement the
> feedback received on the merged version [1], and the respin [2], for
> changes related to include/linux/cpumask.h and lib/cpumask.c.
> 
> [1] https://lore.kernel.org/lkml/cover.1656777646.git.sander@svanheule.net/
> [2] https://lore.kernel.org/lkml/cover.1659077534.git.sander@svanheule.net/
> 
> Sander Vanheule (3):
>   cpumask: align signatures of UP implementations
>   lib/cpumask: add inline cpumask_next_wrap() for UP
>   lib/cpumask: drop always-true preprocessor guard

Acked-by: Yury Norov <yury.norov@gmail.com>

Applying at bitmap-for-next, after some testing.

Thanks,
Yury

>  include/linux/cpumask.h | 26 +++++++++++++++++++++++---
>  lib/Makefile            |  3 ++-
>  lib/cpumask.c           |  2 --
>  3 files changed, 25 insertions(+), 6 deletions(-)
> 
> -- 
> 2.37.1

  parent reply	other threads:[~2022-08-10  4:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 17:36 Sander Vanheule
2022-08-09 17:36 ` [PATCH v1 1/3] cpumask: align signatures of UP implementations Sander Vanheule
2022-08-09 17:36 ` [PATCH v1 2/3] lib/cpumask: add inline cpumask_next_wrap() for UP Sander Vanheule
2022-08-09 17:36 ` [PATCH v1 3/3] lib/cpumask: drop always-true preprocessor guard Sander Vanheule
2022-08-10  4:55 ` Yury Norov [this message]
2022-08-10  8:18   ` [PATCH v1 0/3] cpumask: UP optimisation fixes follow-up Sander Vanheule
2022-08-10  8:39     ` Yury Norov
2022-08-10  8:42       ` Sander Vanheule

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=YvM6LjJCMK4ZKrxK@yury-laptop \
    --to=yury.norov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=sander@svanheule.net \
    /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®