From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Avihai Horon <avihaih@nvidia.com>,
qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Yishai Hadas <yishaih@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>
Subject: Re: [PATCH 2/9] vfio: Fix compilation errors caused by VFIO migration v1 deprecation
Date: Thu, 12 May 2022 20:32:22 -0300 [thread overview]
Message-ID: <20220512233222.GH1343366@nvidia.com> (raw)
In-Reply-To: <20220512151140.0de06d87.alex.williamson@redhat.com>
On Thu, May 12, 2022 at 03:11:40PM -0600, Alex Williamson wrote:
> On Thu, 12 May 2022 15:25:32 -0300
> Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > On Thu, May 12, 2022 at 11:57:10AM -0600, Alex Williamson wrote:
> > > > @@ -767,9 +767,10 @@ static void vfio_migration_state_notifier(Notifier *notifier, void *data)
> > > > case MIGRATION_STATUS_CANCELLED:
> > > > case MIGRATION_STATUS_FAILED:
> > > > bytes_transferred = 0;
> > > > - ret = vfio_migration_set_state(vbasedev,
> > > > - ~(VFIO_DEVICE_STATE_SAVING | VFIO_DEVICE_STATE_RESUMING),
> > > > - VFIO_DEVICE_STATE_RUNNING);
> > > > + ret = vfio_migration_set_state(
> > > > + vbasedev,
> > > > + ~(VFIO_DEVICE_STATE_V1_SAVING | VFIO_DEVICE_STATE_V1_RESUMING),
> > > > + VFIO_DEVICE_STATE_V1_RUNNING);
> > >
> > > Yikes! Please follow the line wrapping used elsewhere. There's no need
> > > to put the first arg on a new line and subsequent wrapped lines should
> > > be indented to match the previous line, or at least to avoid wrapping
> > > itself. Here we can use something like:
> >
> > This is generated by clang-format with one of the qmeu styles, it
> > follows the documented guide:
> >
> > In case of function, there are several variants:
> >
> > - 4 spaces indent from the beginning
> > - align the secondary lines just after the opening parenthesis of the
> > first
> >
> > clang-format selected the first option due to its optimization
> > algorithm.
> >
> > Knowing nothing about qmeu, I am confused??
>
> Maybe someone needs to throw more AI models at clang-format so that it
> considers the more readable option? QEMU does a lot wrong with style
> imo, and maybe it's technically compliant as written, but I think what
> I proposed is also compliant, as well as more readable and more
> consistent with the existing file. Thanks,
Let Avihai know any indenting you don't like he will fix it.
IIRC clang scores line-breaking an expression as worse than going to
the smaller indent. Personally I would agree with this.
Thanks,
Jason
next prev parent reply other threads:[~2022-05-12 23:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 15:43 [PATCH 0/9] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2022-05-12 15:43 ` [PATCH 1/9] linux-headers: Update headers to v5.18-rc6 Avihai Horon
2022-05-12 15:43 ` [PATCH 2/9] vfio: Fix compilation errors caused by VFIO migration v1 deprecation Avihai Horon
2022-05-12 17:57 ` Alex Williamson
2022-05-12 18:25 ` Jason Gunthorpe
2022-05-12 21:11 ` Alex Williamson
2022-05-12 23:32 ` Jason Gunthorpe [this message]
2022-05-13 7:08 ` Cornelia Huck
2022-05-12 15:43 ` [PATCH 3/9] vfio/migration: Fix NULL pointer dereference bug Avihai Horon
2022-05-16 11:15 ` Juan Quintela
2022-05-17 12:28 ` Avihai Horon
2022-05-18 11:36 ` Juan Quintela
2022-05-12 15:43 ` [PATCH 4/9] vfio/migration: Skip pre-copy if dirty page tracking is not supported Avihai Horon
2022-05-16 11:22 ` Juan Quintela
2022-05-16 20:22 ` Alex Williamson
2022-05-16 23:08 ` Jason Gunthorpe
2022-05-17 16:00 ` Alex Williamson
2022-05-17 16:08 ` Jason Gunthorpe
2022-05-17 17:22 ` Alex Williamson
2022-05-17 17:39 ` Jason Gunthorpe
2022-05-18 3:46 ` Alex Williamson
2022-05-18 17:01 ` Jason Gunthorpe
2022-05-18 11:39 ` Juan Quintela
2022-05-18 15:50 ` Jason Gunthorpe
2022-05-24 15:11 ` Avihai Horon
2022-05-20 10:58 ` Joao Martins
2022-05-23 6:11 ` Avihai Horon
2022-05-23 9:45 ` Joao Martins
2022-05-12 15:43 ` [PATCH 5/9] migration/qemu-file: Add qemu_file_get_to_fd() Avihai Horon
2022-05-16 11:31 ` Juan Quintela
2022-05-17 12:36 ` Avihai Horon
2022-05-18 11:54 ` Juan Quintela
2022-05-18 15:42 ` Jason Gunthorpe
2022-05-18 16:00 ` Daniel P. Berrangé
2022-05-18 16:16 ` Jason Gunthorpe
2022-05-12 15:43 ` [PATCH 6/9] vfio/migration: Implement VFIO migration protocol v2 Avihai Horon
2022-05-23 18:14 ` Joao Martins
2022-05-24 15:35 ` Avihai Horon
2022-05-12 15:43 ` [PATCH 7/9] vfio/migration: Reset device if setting recover state fails Avihai Horon
2022-05-12 15:43 ` [PATCH 8/9] vfio: Alphabetize migration section of VFIO trace-events file Avihai Horon
2022-05-12 15:43 ` [PATCH 9/9] docs/devel: Align vfio-migration docs to VFIO migration v2 Avihai Horon
2022-05-12 18:02 ` [PATCH 0/9] vfio/migration: Implement VFIO migration protocol v2 Alex Williamson
2022-05-13 7:04 ` Cornelia Huck
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=20220512233222.GH1343366@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=maorg@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=targupta@nvidia.com \
--cc=yishaih@nvidia.com \
/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).