linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: SeongJae Park <sj@kernel.org>, akpm@linux-foundation.org
Cc: willy@infradead.org, paulmck@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] mm/slab: trivial fixup for SLAB_TYPESAFE_BY_RCU example code snippet
Date: Wed, 7 Jun 2023 13:40:37 +0200	[thread overview]
Message-ID: <8701bb94-07c4-f552-aecd-0a6a2621f5ab@suse.cz> (raw)
In-Reply-To: <20230417190450.1682-1-sj@kernel.org>


On 4/17/23 21:04, SeongJae Park wrote:
> Changes from v3
> (https://lore.kernel.org/linux-mm/20230417173238.22237-1-sj@kernel.org/)
> - Yet more wordsmith of the second patch's commit message
>   (Matthew Wilcox)
> 
> Changes from v2
> (https://lore.kernel.org/linux-mm/20230415033159.4249-1-sj@kernel.org/)
> - Wordsmith commit message of the second patch (Valstimil Babka)
> 
> Changes from v1
> (https://lore.kernel.org/linux-mm/20230415003754.1852-1-sj@kernel.org/)
> - Update label (s/again/begin/) correctly (Matthew Wilcox)
> - Add missed rcu_read_unlock()
> 
> This patchset is for trivial fixup for SLAB_TYPESAFE_BY_RCU example code
> snippet, namely adding missed semicolon and breaking RCU read-side
> critical section into smaller ones.

Oops, almost forgot to merge this, now done, with Paul's R-b's, in
slab/for-6.5/cleanup. Thanks!

> SeongJae Park (2):
>   mm/slab: add a missing semicolon on SLAB_TYPESAFE_BY_RCU example code
>   mm/slab: break up RCU readers on SLAB_TYPESAFE_BY_RCU example code
> 
>  include/linux/slab.h | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 


      parent reply	other threads:[~2023-06-07 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 19:04 SeongJae Park
2023-04-17 19:04 ` [PATCH v4 1/2] mm/slab: add a missing semicolon on SLAB_TYPESAFE_BY_RCU example code SeongJae Park
2023-04-17 19:04 ` [PATCH v4 2/2] mm/slab: break up RCU readers " SeongJae Park
2023-04-24 18:34   ` Paul E. McKenney
2023-06-07 11:40 ` Vlastimil Babka [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=8701bb94-07c4-f552-aecd-0a6a2621f5ab@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@kernel.org \
    --cc=sj@kernel.org \
    --cc=willy@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