public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss•qualcomm.com>
To: Petr Mladek <pmladek@suse•com>, Arnd Bergmann <arnd@kernel•org>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	Masahiro Yamada <masahiroy@kernel•org>,
	Josh Poimboeuf <jpoimboe@kernel•org>,
	Jiri Kosina <jikos@kernel•org>, Miroslav Benes <mbenes@suse•cz>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, Arnd Bergmann <arnd@arndb•de>,
	Joe Lawrence <joe.lawrence@redhat•com>,
	Christophe Leroy <christophe.leroy@csgroup•eu>,
	Easwar Hariharan <eahariha@linux•microsoft.com>,
	live-patching@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH 03/10] samples/livepatch: add module descriptions
Date: Tue, 25 Mar 2025 08:03:04 -0700	[thread overview]
Message-ID: <978e72a6-0da4-4eb2-9c18-5b42db543160@oss.qualcomm.com> (raw)
In-Reply-To: <Z-J--iv8LzgArWAX@pathway.suse.cz>

On 3/25/2025 3:01 AM, Petr Mladek wrote:
> Arnd, should I push this via the livepatch tree or would you prefer to push
> the entire patchset together? Both ways work for me.

My past experience was to let individual maintainers take the ones that apply
to their trees, and then Andrew can pick up the stragglers.

/jeff

  reply	other threads:[~2025-03-25 15:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 17:32 [PATCH 01/10] exportfs: add module description Arnd Bergmann
2025-03-24 17:32 ` [PATCH 02/10] ASN.1: " Arnd Bergmann
2025-04-06 18:21   ` Geert Uytterhoeven
2025-03-24 17:32 ` [PATCH 03/10] samples/livepatch: add module descriptions Arnd Bergmann
2025-03-25 10:01   ` Petr Mladek
2025-03-25 15:03     ` Jeff Johnson [this message]
2025-03-24 17:32 ` [PATCH 04/10] fpga: tests: " Arnd Bergmann
2025-03-25 17:06   ` Marco Pagani
2025-04-25  4:27     ` Xu Yilun
2025-03-24 17:32 ` [PATCH 05/10] xenbus: add module description Arnd Bergmann
2025-03-27 16:43   ` Jürgen Groß
2025-03-24 17:32 ` [PATCH 06/10] zlib: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 07/10] ucs2_string: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 08/10] kunit: add module description for backtrace suppression test Arnd Bergmann
2025-03-24 17:32 ` [PATCH 09/10] mm/kasan: add module decription Arnd Bergmann
2025-03-24 22:00   ` Andrey Konovalov
2025-03-24 17:32 ` [PATCH 10/10] kunit: slub: add module description Arnd Bergmann
2025-03-25 14:58 ` (subset) [PATCH 01/10] exportfs: " Christian Brauner

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=978e72a6-0da4-4eb2-9c18-5b42db543160@oss.qualcomm.com \
    --to=jeff.johnson@oss$(echo .)qualcomm.com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=arnd@kernel$(echo .)org \
    --cc=christophe.leroy@csgroup$(echo .)eu \
    --cc=eahariha@linux$(echo .)microsoft.com \
    --cc=jikos@kernel$(echo .)org \
    --cc=joe.lawrence@redhat$(echo .)com \
    --cc=jpoimboe@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=live-patching@vger$(echo .)kernel.org \
    --cc=masahiroy@kernel$(echo .)org \
    --cc=mbenes@suse$(echo .)cz \
    --cc=pmladek@suse$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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