From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: peter.maydell@linaro.org, cjia@nvidia.com,
mjrosato@linux.ibm.com,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, kwankhede@nvidia.com,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] Revert series: virtiofsd: Announce submounts to the guest
Date: Wed, 28 Oct 2020 09:45:28 +0000 [thread overview]
Message-ID: <20201028094528.GC3701@work-vm> (raw)
In-Reply-To: <4edc7be0-cc34-6ea1-c88b-3b9888089fe2@redhat.com>
* Max Reitz (mreitz@redhat.com) wrote:
> On 28.10.20 08:55, Stefan Hajnoczi wrote:
> > On Tue, Oct 27, 2020 at 08:13:28PM -0600, Alex Williamson wrote:
> >> This reverts the following commits due to their basis on a bogus
> >> linux kernel header update:
> >
> > What was the issue? Did the sub-mounts series include kernel header
> > changes that haven't landed in Linux yet?
>
> Yes.
>
> The kernel series was applied, however, Miklos fixed some things in the
> process, and then Dave applied the virtiofsd series assuming that it
> would be OK now that the kernel series is in.
>
> So what could have gone better is e.g.:
>
> (1) I could have marked the virtiofsd series as RFC until I know the
> definitive state of the kernel series.
>
> (2) I could have given an explicit NAK to the virtiofsd series once I
> noted that I need to write a v2, and not bury that somewhere deep in the
> kernel side thread (https://marc.info/?l=fuse-devel&m=160087601428180).
Yeh that one would have been useful.
Unfortunately Miklos's changes were such that it didn't break your code;
I did give it a smoke test with 5.10-rc1 and saw that it was doing the submounts OK.
Dave
> (3) I should have noticed Dave applying the virtiofsd series (Monday
> evening) and intervened. But my inbox full from PTO plus trying to
> perhaps get the FUSE export series done for 5.2 led to me just not noticing.
>
> Max
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-10-28 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 2:13 [PATCH] Revert series: virtiofsd: Announce submounts to the guest Alex Williamson
2020-10-28 7:55 ` Stefan Hajnoczi
2020-10-28 9:39 ` Max Reitz
2020-10-28 9:45 ` Dr. David Alan Gilbert [this message]
2020-10-28 9:40 ` Dr. David Alan Gilbert
2020-10-28 14:30 ` Peter Maydell
2020-10-28 9:44 ` Max Reitz
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=20201028094528.GC3701@work-vm \
--to=dgilbert@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=mjrosato@linux.ibm.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.