public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: pmalani@chromium.org, bleung@chromium.org, groeck@chromium.org,
	tzungbi@kernel.org, linux-kernel@vger.kernel.org,
	chrome-platform@lists.linux.dev
Subject: [GIT PULL] chrome-platform fixes for v6.3-rc4
Date: Fri, 24 Mar 2023 11:40:22 +0800	[thread overview]
Message-ID: <ZB0bphQcL7KLRuV6@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

Linus,

Please pull chrome-platform fixes for v6.3-rc4.

Thanks,
TzungBi.

The following changes since commit b0d8a67715dae445c065c83a40a581d6563a341f:

  platform/chrome: cros_ec_typec: Fix spelling mistake (2023-02-08 18:21:03 +0000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-fixes-for-v6.3-rc4

for you to fetch changes up to b20cf3f89c56b5f6a38b7f76a8128bf9f291bbd3:

  platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl (2023-03-24 10:56:28 +0800)

----------------------------------------------------------------
chrome-platform fixes for v6.3-rc4

Fix a kernel data leak vulnerability.

----------------------------------------------------------------
Tzung-Bi Shih (1):
      platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl

 drivers/platform/chrome/cros_ec_chardev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2023-03-24  3:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  3:40 Tzung-Bi Shih [this message]
2023-03-24 16:31 ` [GIT PULL] chrome-platform fixes for v6.3-rc4 pr-tracker-bot

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=ZB0bphQcL7KLRuV6@google.com \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmalani@chromium.org \
    --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