From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, dhowells@redhat.com,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
doebel@amazon.de
Subject: Re: [PATCH v2 5.15.y] ring-buffer: Remove ring_buffer_read_prepare_sync()
Date: Tue, 30 Jun 2026 18:23:10 -0400 [thread overview]
Message-ID: <stable-reply-item003-ringbuf-515-20260630181642@kernel.org> (raw)
In-Reply-To: <20260630060321.1494832-1-doebel@amazon.de>
> [doebel@amazon.de: move patch section using guard() macro into a
> separate block to address declaration after statement warning.]
> Signed-off-by: Bjoern Doebel <doebel@amazon.de>
Queued for 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-30 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 12:23 [PATCH 5.15.y] ring-buffer: Remove ring_buffer_read_prepare_sync() Bjoern Doebel
2026-06-25 10:41 ` Sasha Levin
2026-06-25 22:19 ` Bjoern Doebel
2026-06-30 6:03 ` [PATCH v2 " Bjoern Doebel
2026-06-30 22:23 ` Sasha Levin [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=stable-reply-item003-ringbuf-515-20260630181642@kernel.org \
--to=sashal@kernel.org \
--cc=dhowells@redhat.com \
--cc=doebel@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@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