From: Simon Horman <horms@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Build commit for Patchwork?
Date: Thu, 16 Oct 2025 17:25:37 +0100 [thread overview]
Message-ID: <aPEcgcsqFJAEYD_2@horms.kernel.org> (raw)
In-Reply-To: <CAGXJAmwrPr46Ju-ZiLa7prnNFAcGr7Hu-vpk1B6-Q9Ks8fu8wQ@mail.gmail.com>
On Thu, Oct 16, 2025 at 09:07:09AM -0700, John Ousterhout wrote:
> Is there a way to tell which commit Patchwork uses for its builds?
>
> Patchwork builds are generating this error:
>
> ‘struct flowi_common’ has no member named ‘flowic_tos’; did you mean
> ‘flowic_oif’?
>
> (https://netdev.bots.linux.dev/static/nipa/1012035/14269094/build_32bit/stderr)
>
> but the member flowic_tos seems to be present in all recent commits
> that I can find.
Hi John,
I'm not sure that it's explicitly exposed.
But if you look at one of the builds for the 1st patch of the series
then it will start with a baseline build (that is, build of the
tree the patch-set is applied on top of).
In this case, looking at the URL below, which is linked from
the first patch in the series in Patchwork, I see.
cb85ca4c0a34 ("Merge branch 'net-airoha-npu-introduce-support-for-airoha-7583-npu'")
https://netdev.bots.linux.dev/static/nipa/1012035/14269097/build_32bit/stdout
next prev parent reply other threads:[~2025-10-16 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 16:07 Build commit for Patchwork? John Ousterhout
2025-10-16 16:25 ` Simon Horman [this message]
2025-10-16 16:57 ` Ilya Maximets
2025-10-16 19:55 ` Jakub Kicinski
2025-10-16 20:45 ` Andrew Lunn
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=aPEcgcsqFJAEYD_2@horms.kernel.org \
--to=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
/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;
as well as URLs for NNTP newsgroup(s).