All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Donald Hunter <donald.hunter@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	Riana Tauro <riana.tauro@intel.com>
Subject: Re: building ynl afaics requires updating the UAPI headers first
Date: Mon, 22 Jun 2026 14:56:04 -0700	[thread overview]
Message-ID: <20260622145604.524949ec@kernel.org> (raw)
In-Reply-To: <f88cfe04-c817-4383-866b-530c5bc5bd95@leemhuis.info>

On Mon, 22 Jun 2026 18:33:29 +0200 Thorsten Leemhuis wrote:
> On 6/22/26 18:05, Jakub Kicinski wrote:
> > On Fri, 19 Jun 2026 09:28:47 +0200 Thorsten Leemhuis wrote:  
> >> On 6/19/26 02:06, Jakub Kicinski wrote:  
> >>> Can't repro for some reason, but we probably need something like 
> >>> commit 46e9b0224475abc to add the explicit include rule.    
> >>
> >> Thx for the pointer. So I guess you mean something like the below,
> >> which did the trick for me. Will submit this as properly, unless
> >> someone points out something stupid in it.  
>  [...]  
> 
> No, because the funny thing is: now I fail to reproduce it myself. And I
> don't know why, as 24h earlier when you had written "Can't repro for
> some reason" I had once more checked that I could trigger this by
> downgrading Fedora's kernel-headers package to a version from some weeks
> ago. Not sure what changed since then.
> 
> Want me to sent it nevertheless?

Yes, let's get it in place, it can't hurt AFAIU.

      reply	other threads:[~2026-06-22 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 13:39 building ynl afaics requires updating the UAPI headers first Thorsten Leemhuis
2026-06-19  0:06 ` Jakub Kicinski
2026-06-19  7:28   ` Thorsten Leemhuis
2026-06-22 16:05     ` Jakub Kicinski
2026-06-22 16:33       ` Thorsten Leemhuis
2026-06-22 21:56         ` Jakub Kicinski [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=20260622145604.524949ec@kernel.org \
    --to=kuba@kernel.org \
    --cc=donald.hunter@gmail.com \
    --cc=linux@leemhuis.info \
    --cc=netdev@vger.kernel.org \
    --cc=riana.tauro@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.