public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Parav Pandit <pandit.parav@gmail.com>,
	virtio-comment@lists.linux.dev, Parav Pandit <parav@nvidia.com>
Subject: Re: [GIT PULL virtio 00/40] virtio master branch with fixes and admin commands
Date: Fri, 12 Jul 2024 06:47:43 -0400	[thread overview]
Message-ID: <20240712064201-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87o772c2x9.fsf@redhat.com>

On Fri, Jul 12, 2024 at 12:36:34PM +0200, Cornelia Huck wrote:
> On Thu, Jul 11 2024, Parav Pandit <pandit.parav@gmail.com> wrote:
> 
> > Hi Michael, Cornelia,
> >
> > The following changes since commit 37c6a406678a5ee891fdf5671298cb4fcfa517f2:
> >
> >   sound: add sampling rates 12000Hz and 24000Hz (2024-02-16 11:55:25 +0100)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/paravmellanox/virtio-spec.git tags/for_1.4
> >
> > for you to fetch changes up to 74bf759aef3bf10447aadcb841c66dc5e6a578d6:
> >
> >   virtio_pci_cap64: specify offset_hi, length_hi endianness (2024-07-11 20:54:20 +0300)
> >
> > ----------------------------------------------------------------
> > This tag contains virtio master branch and set of patches of administration commands, pci fix, blk config fix, and net description fixes
> >
> > - editorial changes froom master branch
> > - virtio blk and pci capabilities data type fixes
> > - virtio net header description update
> > - adminstration commands for flow filters
> > - administration commands for device parts
> >
> > Generated PDF and also the diff pdf were verified using makepdf.sh, makediffall.sh and makediffpdf.sh.
> >
> > ----------------------------------------------------------------
> > Cornelia Huck (12):
> >       edit: remove old changelog
> >       edit: add changelog for 1.3
> >       acknowledgements: update for 1.3
> >       editorial: update copyright date in PDF footer to 2023
> >       change revisions: diff from v1.2, current v1.3
> >       title: note that 1.3 supercedes 1.2
> >       revision: update date
> >       remove enumerate usage that makes the tool unhappy
> >       Revert "remove enumerate usage that makes the tool unhappy"
> >       editorial: various fixes for 1.3-csd01
> >       editorial: update "Computer Language Definitions" URL
> >       makediff: update list of cherry-picks
> >
> > Kröning (1):
> >       virtio_pci_cap64: specify offset_hi, length_hi endianness
> 
> Hm, something bad happened to the author field here (script confused?)
> Not fixable without a force push, though :(

Indeed.
I did a force push.
Parav, you will have to rebase your pull request, sorry.

-- 
MST


      reply	other threads:[~2024-07-12 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 20:23 [GIT PULL virtio 00/40] virtio master branch with fixes and admin commands Parav Pandit
2024-07-11 22:27 ` Michael S. Tsirkin
2024-07-12  4:31   ` Parav Pandit
2024-07-12 10:36 ` Cornelia Huck
2024-07-12 10:47   ` Michael S. Tsirkin [this message]

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=20240712064201-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=pandit.parav@gmail.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@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