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 10:57:09 -0400 [thread overview]
Message-ID: <20251006105608-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a4e912547211eed865bdf769647936c1e3034e4e.camel@gmail.com>
On Mon, Oct 06, 2025 at 04:15:10PM +0200, Filip Hejsek wrote:
> On Mon, 2025-10-06 at 06:29 -0400, Michael S. Tsirkin wrote:
> > 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?
>
> I'm kinda confused by this question, because I thought you already
> understood the situation.
Yes - I just noticed this backport request stood unanswered and
I thought it's a good idea to make stable maintainers know it's
not yet the time to do the backport.
Sorry if I did it in a confusing way.
> I sent this backport request after a discussion with Max in the revert
> thread, from which I got the impression that the virtio spec
> maintainers were unwilling to change the spec to match the Linux
> implementation. That impression might have been wrong though.
>
> When you sent Linus a pull request containing the revert, I realized
> that there was no consensus about which side should be fixed (spec or
> Linux) and told you that I think it should be reverted only if the spec
> is also changed. You then sent a spec change patch [1] to the virtio
> mailing list.
>
> I'm not familiar with how decisions about the virtio spec are made, so
> I don't know if that change is going to be accepted or not.
>
> [1]: https://lore.kernel.org/virtio-comment/7b939d85ec0b532bae4c16bb927edddcf663bb48.1758212319.git.mst@redhat.com/t/
>
> Best regards,
> Filip Hejsek
next prev parent reply other threads:[~2025-10-06 14:57 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
2025-10-06 14:15 ` Filip Hejsek
2025-10-06 14:57 ` Michael S. Tsirkin [this message]
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=20251006105608-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.