linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: Yury Norov <yury.norov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [GIT PULL] MM updates for 5.20-rc1
Date: Sun, 07 Aug 2022 22:11:23 +0200	[thread overview]
Message-ID: <9b191d64cc5285eebda1ccf24241bae30c128961.camel@svanheule.net> (raw)
In-Reply-To: <Yu9KPCxGYUUROdlC@yury-laptop>

Hi Yury, Andrew,

On Sat, 2022-08-06 at 22:14 -0700, Yury Norov wrote:
> Hi Andrew,
> 
> > Sander Vanheule (5):
> >       x86/cacheinfo: move shared cache map definitions
> >       cpumask: add UP optimised for_each_*_cpu versions
> >       cpumask: Fix invalid uniprocessor mask assumption
> >       lib/test: introduce cpumask KUnit test suite
> >       cpumask: update cpumask_next_wrap() signature
> 
> I think, Sander has a new version for this:
> 
> https://lore.kernel.org/all/YuV1J7Zt+NzkrWeV@yury-laptop/T/#ma2d7613315f331fac83d8bd5ae22ef740945569ao

Looks like v4 was merged with the non-MM updates:

https://lore.kernel.org/all/165989506499.6057.14827201987918707189.pr-tracker-bot@kernel.org/

I'll have to write a follow-up to cover the v4/v5 differences, since there were
still some significant changes.

Best,
Sander


  reply	other threads:[~2022-08-07 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07  5:14 Yury Norov
2022-08-07 20:11 ` Sander Vanheule [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-03 20:35 Andrew Morton
2022-08-05 23:20 ` Linus Torvalds
2022-08-06  0:05   ` Andrew Morton
2022-08-05 23:32 ` Linus Torvalds
2022-08-06  0:04   ` Roman Gushchin
2022-08-06  0:07     ` Andrew Morton
2022-08-06  1:43       ` Joe Perches
2022-08-05 23:40 ` pr-tracker-bot

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=9b191d64cc5285eebda1ccf24241bae30c128961.camel@svanheule.net \
    --to=sander@svanheule.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yury.norov@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