On Wed, 15 Jul 2020 12:26:20 -0400 Collin Walling <wall...@linux.ibm.com> wrote:
> On 7/15/20 12:04 PM, Cornelia Huck wrote: > > On Wed, 15 Jul 2020 11:36:35 -0400 > > Collin Walling <wall...@linux.ibm.com> wrote: > > > >> Polite ping. Patches have been sitting on the list for a few weeks now, > >> and it doesn't look like any further changes are requested (hopefully I > >> didn't miss something). > > > > The only thing I had was (I think) the logging of the length you just > > replied to. We can still tweak things like that later, of course. > > > > As these patches depend on a headers sync, I could not yet queue them. > > I can keep a preliminary version on a branch. I assume that the header > > changes will go in during the next kernel merge window? (If I missed > > something, apologies for that.) > > > > Gotcha. Thanks for the update :) > > There was an email on the KVM list a couple of days that made one change > to the Linux header. Just changed the integer used for the DIAG cap, > which should be reflected in QEMU as well. > > https://www.spinics.net/lists/kvm/msg220548.html > > Should I respin this patch series to include the new ack's and account > for the header sync? No need for that, my tooling picks up acks and the headers update needs to be replaced with a sync against a proper Linux version anyway. I've queued the patches on a local branch, and the only patch that did not apply cleanly was the headers patch, which will get replaced later anyway :) Just ping me when the kernel patches hit upstream, then I'll do a header sync against the next -rc and queue the patches on s390-next.
