From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Guenter Roeck <linux@roeck-us.net>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mark Rutland <mark.rutland@arm.com>,
Matt Turner <mattst88@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Richard Henderson <rth@twiddle.net>,
Sean Christopherson <seanjc@google.com>,
Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [GIT PULL] bounds fixes for v5.18-rc1
Date: Wed, 23 Mar 2022 13:44:56 +0200 [thread overview]
Message-ID: <YjsIOGpYwN10n60u@paasikivi.fi.intel.com> (raw)
In-Reply-To: <202203210843.0E70F58@keescook>
Hi Kees,
On Mon, Mar 21, 2022 at 08:52:31AM -0700, Kees Cook wrote:
> media: omap3isp: Use struct_group() for memcpy() region
This patch has been applied to linux-media tree about a month ago. It may
have taken a bit more time than usual to get to linux-next though.
Please try to remember to agree with maintainers in advance when merging
patches via non-default routes.
Thanks.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2022-03-23 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:52 [GIT PULL] bounds fixes for v5.18-rc1 Kees Cook
2022-03-22 3:06 ` pr-tracker-bot
2022-03-23 11:44 ` Sakari Ailus [this message]
2022-03-23 14:51 ` Kees Cook
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=YjsIOGpYwN10n60u@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=keescook@chromium.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mattst88@gmail.com \
--cc=mchehab@kernel.org \
--cc=peterhuewe@gmx.de \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
--cc=seanjc@google.com \
--cc=stefanb@linux.ibm.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).