RE: [PATCH v9 0/1] virtio-media: Add device specification

Parav Pandit <[email protected]>
Newsgroups dev.linux.lists.virtio-comment
Message-ID <CY8PR12MB7195B3BA93D4040519D9CB32DC49A@CY8PR12MB7195.namprd12.prod.outlook.com>
> From: Albert Esteve <[email protected]>
> Sent: 09 July 2025 03:31 PM
> 
> On Wed, Jul 9, 2025 at 11:49 AM Parav Pandit <[email protected]> wrote:
> >
> >
> > > From: Matias Ezequiel Vara Larsen <[email protected]>
> > > Sent: 09 July 2025 03:14 PM
> > >
> > > On Wed, Jul 09, 2025 at 11:34:55AM +0200, Albert Esteve wrote:
> > > > New attempt of including virtio-media device specification.
> > > >
> > > > v8->v9:
> > > > - Rebased to virtio-1.4
> > >
> > > I wonder if it wouldn't be better to just send a patch that fixes
> > > the series instead of the whole series again. Such a change would be
> > > a non editorial change thus not requiring to vote again. The v8 has
> > > been already voted and accepted.
> > >
> > > Matias
> > >
> >
> > Right. I was able to apply v9 without merge conflict.
> > Even though, I prefer what Matias suggested to send the fixup patch so that
> v9 does not need to go through the review and vote again.
> 
> I'm ok with that. I assumed that as it had no changes from v8 whatsoever, it
> would not require a vote. If it does, let's disregard this new version.
> 
If its editorial change, it does not require a vote.

> What do you mean for a fixup patch? New patch series with just the
> changeset required to eliminate the conflict from v8?
> 
I was looking for something that I apply locally to resolve the merge conflict myself.
That way, its basically just v8 + fixup.

So basically a short diff that you did manually, which I can also do before merging it.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.