From: Maximilian Immanuel Brandtner <maxbr@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Amit Shah <amit@kernel.org>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
arnd@arndb.de, gregkh@linuxfoundation.org,
brueckner@linux.ibm.com, schnelle@linux.ibm.com
Subject: Re: [PATCH] virtio: console: Make resizing compliant with virtio spec
Date: Thu, 20 Mar 2025 18:19:38 +0100 [thread overview]
Message-ID: <3e28dc9eb03e2269e2c4613d415291cbda99dfad.camel@linux.ibm.com> (raw)
In-Reply-To: <20250320151901.4906e2a9.pasic@linux.ibm.com>
On Thu, 2025-03-20 at 15:19 +0100, Halil Pasic wrote:
> On Thu, 20 Mar 2025 15:09:57 +0100
> Halil Pasic <pasic@linux.ibm.com> wrote:
>
> > > I already implemented it in my patch v2 (just waiting for Amit to
> > > confirm the new commit message). But if you want to split it you
> > > can
> > > create a seperate patch for it as well (I don't really mind
> > > either
> > > way).
> > >
>
> Your v2 has not been posted yet, or? I can't find it in my Inbox.
>
> I understand that you have confirmed that the byte order handling is
> needed but missing, right?
Yes, I wanted to first hear back from Amit whether he liked the new
commit message, but seeing as he hasn't yet replied I'll just post it
now. I've confirmed that the endianness handling is necessary, but not
implementated. I've looked all the way down into hvc_console() up until
tty_do_resize(), but there are no endianess adjustments up until that
point aka I'm pretty certain the endianness is broken.
I'll post my v2 without the endianness fix then
>
> >
> > It is conceptually a different bug and warrants a patch and a
> > commit
> > message of its own. At least IMHO.
next prev parent reply other threads:[~2025-03-20 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 9:21 [PATCH] virtio: console: Make resizing compliant with virtio spec Maximilian Immanuel Brandtner
2025-03-03 11:54 ` Amit Shah
2025-03-05 9:53 ` Maximilian Immanuel Brandtner
2025-03-05 12:13 ` Niklas Schnelle
2025-03-05 12:15 ` Niklas Schnelle
2025-03-05 12:33 ` Maximilian Immanuel Brandtner
2025-03-10 13:04 ` Maximilian Immanuel Brandtner
2025-03-18 9:51 ` Amit Shah
2025-03-18 10:07 ` Maximilian Immanuel Brandtner
2025-03-18 14:25 ` Amit Shah
2025-03-19 8:54 ` Maximilian Immanuel Brandtner
2025-03-19 9:12 ` Amit Shah
2025-03-19 13:00 ` Maximilian Immanuel Brandtner
2025-03-19 15:00 ` Michael S. Tsirkin
2025-03-19 17:13 ` Halil Pasic
2025-03-19 21:21 ` Michael S. Tsirkin
2025-03-20 7:12 ` Maximilian Immanuel Brandtner
2025-03-20 10:41 ` Halil Pasic
2025-03-20 11:53 ` Maximilian Immanuel Brandtner
2025-03-20 14:09 ` Halil Pasic
2025-03-20 14:19 ` Halil Pasic
2025-03-20 17:19 ` Maximilian Immanuel Brandtner [this message]
2025-03-20 7:23 ` Maximilian Immanuel Brandtner
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=3e28dc9eb03e2269e2c4613d415291cbda99dfad.camel@linux.ibm.com \
--to=maxbr@linux.ibm.com \
--cc=amit@kernel.org \
--cc=arnd@arndb.de \
--cc=brueckner@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--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 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).