Re: [PATCH 1/2] can: peak_usb: validate URB length in pcan_usb_fd_decode_buf()

[Berkant Koc]

Vincent,

Thanks for the input on both points. Let me work through them and
share where I land.

> Your message doesn't follow the mailing list etiquette
> [...]
> kernel mailing lists exclusively require that all communication is
> sent as interleaved quoted replies.

For context: the previous message was a tool-disclosure reply you'd
requested via private CC, not a patch revision. I had treated those
two formats differently. Going forward, I'll keep both in interleaved-
quoted format on-list, as in this reply.

> Is this answer also AI generated? If yes, please don't directly copy
> paste AI answers to the mailing list. We expect you to add value to
> the AI generated output.

To set the record straight: the tool-description paragraph is template
text I maintain under version control for tool-disclosure requests
across multiple maintainer threads, not LLM output. The methodology
section (peak_usb seed commit, pattern scan across
drivers/net/can/usb/, manual reproduction with synthetic short URBs)
was hand-written from my notes at submission time.

Agreed that posting unaltered template text on-list reads the same as
LLM-paste from a reader's perspective. I'll rewrite tool-disclosure
sections in-thread from now on so the substance is fresh per maintainer.

> Ack. Please use that tag.

Confirmed. v2 of the peak_usb series will carry:

  Assisted-by: Claude:claude-opus-4-7 berkoc-pipeline

in the trailer. Same convention going forward across all my
submissions, in line with the kernel AI-tooling policy.

Appreciate the feedback. I revert back to you with the v2 of the
peak_usb series and look forward to your review.

Best regards,
Berkant