Hi Aaron,

The 0-day robot reported a git-am "Patch format detection failed" error on
my patch "conntrack: Log one line per connection at purge." (Message-Id: <
[email protected]>, patchwork #2333166).

I wasn't able to reproduce this locally. git am applies the exact patch
cleanly against the current master merge-base (10fb3d831), and
checkpatch.py reports 0 errors and 0 warnings. The raw message itself is
plain 7-bit ASCII with standard git-send-email headers, nothing unusual.

While investigating, I fetched the same patch from patchwork's own mbox
endpoint and got back a transient "502 Proxy Error" from
https://www.google.com/url?q=http://patchwork.ozlabs.org&source=gmail&ust=1794163855121000&sa=E
instead of the patch content. That makes me suspect the robot may have hit
the same infrastructure hiccup while fetching the patch to run git-am on,
rather than there being an actual defect in the patch.

Could you take another look, or let me know if it would help to just resend
it? Happy to do whichever is easier on your end.

Thanks
Thilak Raj S

On Mon, Nov 02, 2026 01:05 AM, 0-day Robot <[email protected]> wrote:

> Bleep bloop.  Greetings Thilak Raj Surendra Babu, I am a robot and I have
> tried out your patch.
> Thanks for your contribution.
>
> I encountered some error that I wasn't expecting.  See the details below.
>
>
> git-am:
> Patch format detection failed.
>
>
> Patch skipped due to previous failure.
>
> Please check this out.  If you feel there has been an error, please email
> [email protected]
>
> Thanks,
> 0-day Robot
>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to