From: "Michael S. Tsirkin" <mst@redhat.com>
To: Filip Hejsek <filip.hejsek@gmail.com>
Cc: stable@vger.kernel.org,
Maximilian Immanuel Brandtner <maxbr@linux.ibm.com>,
Daniel Verkamp <dverkamp@chromium.org>,
Amit Shah <amit@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
virtualization@lists.linux.dev
Subject: Re: Backport request for commit 5326ab737a47 ("virtio_console: fix order of fields cols and rows")
Date: Mon, 6 Oct 2025 06:29:15 -0400 [thread overview]
Message-ID: <20251006062851-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f839e710b4ede119aa9ad1f2a8e8bcc7fcc00233.camel@gmail.com>
On Thu, Sep 18, 2025 at 01:13:24AM +0200, Filip Hejsek wrote:
> Hi,
>
> I would like to request backporting 5326ab737a47 ("virtio_console: fix
> order of fields cols and rows") to all LTS kernels.
>
> I'm working on QEMU patches that add virtio console size support.
> Without the fix, rows and columns will be swapped.
>
> As far as I know, there are no device implementations that use the
> wrong order and would by broken by the fix.
>
> Note: A previous version [1] of the patch contained "Cc: stable" and
> "Fixes:" tags, but they seem to have been accidentally left out from
> the final version.
>
> [1]: https://lore.kernel.org/all/20250320172654.624657-1-maxbr@linux.ibm.com/
>
> Thanks,
> Filip Hejsek
But I thought we are reverting it?
--
MST
next prev parent reply other threads:[~2025-10-06 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 23:13 Backport request for commit 5326ab737a47 ("virtio_console: fix order of fields cols and rows") Filip Hejsek
2025-09-18 15:58 ` Filip Hejsek
2025-09-18 16:19 ` Michael S. Tsirkin
2025-10-06 10:29 ` Michael S. Tsirkin [this message]
2025-10-06 14:15 ` Filip Hejsek
2025-10-06 14:57 ` Michael S. Tsirkin
2025-12-23 21:36 ` Filip Hejsek
2025-12-23 21:51 ` Michael S. Tsirkin
2026-01-08 13:19 ` Greg Kroah-Hartman
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=20251006062851-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amit@kernel.org \
--cc=dverkamp@chromium.org \
--cc=filip.hejsek@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=maxbr@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.