public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Manuel Ebner <manuelebner@mailbox.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, Kees Cook <kees@kernel.org>
Cc: linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
	linux-sound@vger.kernel.org, rcu@vger.kernel.org,
	linux-media@vger.kernel.org, linux-mm@kvack.org,
	Manuel Ebner <manuelebner@mailbox.org>
Subject: Re: [PATCH v4 0/3] Documentation: adopt new coding style of type-aware kmalloc-family
Date: Sun, 03 May 2026 08:56:13 -0600	[thread overview]
Message-ID: <87o6iwczjm.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260429070759.309110-3-manuelebner@mailbox.org>

Manuel Ebner <manuelebner@mailbox.org> writes:

> Update the documentation to reflect new type-aware kmalloc-family as
> suggested in commit 2932ba8d9c99 ("slab: Introduce kmalloc_obj()
> and family")

OK, I have applied this series.  While doing so, I restored the "gfp"
parameter in the changelog portion where it had been mistakenly removed.

Thanks,

jon

  parent reply	other threads:[~2026-05-03 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  7:08 [PATCH v4 0/3] Documentation: adopt new coding style of type-aware kmalloc-family Manuel Ebner
2026-04-29  7:14 ` [PATCH v4 1/3] " Manuel Ebner
2026-04-29  8:00   ` Vlastimil Babka
2026-04-30  0:53   ` SeongJae Park
2026-04-30  1:00     ` SeongJae Park
2026-05-01  9:12       ` Manuel Ebner
2026-04-29  7:27 ` [PATCH v4 3/3] Documentation: deprecated.rst: kmalloc-family: mark argument as optional Manuel Ebner
2026-04-29  8:01   ` Vlastimil Babka
2026-04-30  1:03   ` SeongJae Park
2026-05-01  9:19     ` Manuel Ebner
2026-05-03 14:56 ` Jonathan Corbet [this message]
2026-05-03 15:47   ` [PATCH v4 0/3] Documentation: adopt new coding style of type-aware kmalloc-family Manuel Ebner
2026-05-03 15:51     ` Jonathan Corbet

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=87o6iwczjm.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=manuelebner@mailbox.org \
    --cc=rcu@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@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