Linux USB
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Jason Colapietro <jason@suedeai.ai>,
	shuah@kernel.org, valentina.manea.m@gmail.com
Cc: greg@kroah.com, i@zenithal.me, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v7] usbip: make remote list honor parsable output
Date: Fri, 20 Nov 2026 13:38:43 -0700	[thread overview]
Message-ID: <dda50295-e49d-4424-bd80-32da6d562966@linuxfoundation.org> (raw)
In-Reply-To: <CA+Z0x2L9ho_Yq-BCSy2hBhQP6Yp9pmMaC741_YSk==0vS_gmeA@mail.gmail.com>

On 11/16/26 20:35, Jason Colapietro wrote:
> Hi Shuah and all,
> 
> Checking back on v7 and the October 1 validation report. Is there
> anything still needed from me before review can proceed, or does the
> two-VM test setup and before/after output address your request?


Thank you for running the tests I asked for.

However, the reason I am pausing on this is, it isn't clear
to me what really needs fixing.

Can you explain in your own words what happens if this patch
isn't applied? What breaks? I see the very long changelog that
appears to be coming from the AI tool you used.

thanks,
-- Shuah

      reply	other threads:[~2026-11-20 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  8:36 [PATCH v7] usbip: make remote list honor parsable output Jason Colapietro
2026-09-14 17:43 ` Jason Colapietro
2026-09-23  8:44   ` Shuah Khan
2026-09-27  4:00     ` Jason Colapietro
2026-10-01 12:49       ` Shuah Khan
2026-10-01 12:53         ` Shuah Khan
2026-10-01 16:13           ` jasoncola1
2026-10-24  4:07             ` jasoncola1
2026-11-17  3:35               ` Jason Colapietro
2026-11-20 20:38                 ` Shuah Khan [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=dda50295-e49d-4424-bd80-32da6d562966@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=greg@kroah.com \
    --cc=i@zenithal.me \
    --cc=jason@suedeai.ai \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=valentina.manea.m@gmail.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