public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: stable@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: HID: Stable backport request (all viable versions)
Date: Mon, 13 Mar 2023 09:08:34 +0000	[thread overview]
Message-ID: <20230313090834.GA1217438@google.com> (raw)
In-Reply-To: <CAHk-=wii6BZtVKYfvQCQqbE3+t1_yAb-ea80-3PcJ4KxgpfHkA@mail.gmail.com>

Dear Stable,

On Sun, 12 Mar 2023, Linus Torvalds wrote:

> It's another Sunday afternoon. which must mean another rc release.
>
> This one looks fairly normal, although if you look at the diffs, they
> are dominated by the removal of a staging driver (r8188eu) that has
> been superceded by a proper driver. That removal itself is 90% of the
> diffs.
>
> But if you filter that out, it all looks normal. Still more than two
> thirds in drivers, but hey, that's pretty normal. It's mostly gpu and
> networking as usual, but there's various other driver fixes in there
> too.
>
> Outside of that regular driver noise (and the unusual driver removal
> noise) it's a little bit of everything: core networking, arch fixes,
> documentation, filesystems (btrfs, xfs, and ext4, but also some core
> vfs fixes). And io_uring and some tooling.
>
> The full shortlog is appended, for the adventurous souls that want to
> get that kind of details. The release feels fairly normal so far, but
> it's early days. Please keep testing and reporting any issues,
>
>                  Linus
>
> ---

> Lee Jones (2):
>       HID: core: Provide new max_buffer_size attribute to over-ride the default
>       HID: uhid: Over-ride the default maximum data buffer value with our own

These 2 are now in Mainline:

  b1a37ed00d790 HID: core: Provide new max_buffer_size attribute to over-ride the default
  1c5d4221240a2 HID: uhid: Over-ride the default maximum data buffer value with our own

Please could you add them to Stable, as far bask as they'll go please.

I'll take a look at any conflicts.

--
Lee Jones [李琼斯]

  parent reply	other threads:[~2023-03-13  9:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 23:45 Linux 6.3-rc2 Linus Torvalds
2023-03-13  8:11 ` Build regressions/improvements in v6.3-rc2 Geert Uytterhoeven
2023-03-13  8:16   ` Geert Uytterhoeven
2023-03-13  9:08 ` Lee Jones [this message]
2023-03-13 10:51   ` HID: Stable backport request (all viable versions) Greg KH
2023-03-13 15:53 ` Linux 6.3-rc2 Guenter Roeck
2023-03-13 18:21   ` Linus Torvalds
2023-03-13 20:30     ` Guenter Roeck
2023-03-13 22:16       ` Linus Torvalds
2023-03-13 22:49         ` Guenter Roeck
2023-03-13 23:11     ` Frederic Weisbecker
2023-03-13 23:17       ` Linus Torvalds
2023-03-13 23:25         ` Frederic Weisbecker
2023-03-14  0:52       ` Guenter Roeck
2023-03-14 11:18         ` Frederic Weisbecker
2023-03-14 11:40           ` Peter Zijlstra
2023-03-14 12:01             ` Ard Biesheuvel
2023-03-14 12:27               ` Peter Zijlstra
2023-03-14 14:40           ` Guenter Roeck
2023-03-14 16:16           ` Guenter Roeck
2023-03-19 14:06   ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-14 14:11     ` Linux regression tracking #update (Thorsten Leemhuis)

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=20230313090834.GA1217438@google.com \
    --to=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.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