public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: FUJITA Tomonori <fujita.tomonori@gmail.com>,
	davem@davemloft.net, edumazet@google.com,
	rust-for-linux@vger.kernel.org, andrew@lunn.ch,
	hkallweit1@gmail.com, tmgross@umich.edu, aliceryhl@google.com,
	boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
	benno.lossin@proton.me, a.hindborg@kernel.org, ojeda@kernel.org,
	alex.gaynor@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] rust: net::phy fix module autoloading
Date: Tue, 17 Dec 2024 16:11:29 +0100	[thread overview]
Message-ID: <b701482d-760a-437b-b3fb-915dc3fc2296@redhat.com> (raw)
In-Reply-To: <20241217065439.25e383fe@kernel.org>



On 12/17/24 15:54, Jakub Kicinski wrote:
> On Tue, 17 Dec 2024 09:54:11 +0100 Paolo Abeni wrote:
>> @Jakub: I still can't reproduce the nipa (rust) build failures locally.
> 
> I'll look into it. Just in case you already investigated the same thing
> I would - have you tried the rust build script from NIPA or just to
> build manually? 

I tried both (I changed the build dir in the script to fit my setup). I
could not see the failure in any case - on top of RHEL 9.

/P


  reply	other threads:[~2024-12-17 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 13:00 [PATCH net v2] rust: net::phy fix module autoloading FUJITA Tomonori
2024-12-17  8:54 ` Paolo Abeni
2024-12-17 14:54   ` Jakub Kicinski
2024-12-17 15:11     ` Paolo Abeni [this message]
2024-12-17 15:44       ` Jakub Kicinski
2024-12-17 16:51         ` Jakub Kicinski
2024-12-18  2:24           ` FUJITA Tomonori
2024-12-18 10:04           ` Paolo Abeni
2024-12-18 19:58             ` Jakub Kicinski
2024-12-17  9:00 ` patchwork-bot+netdevbpf

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=b701482d-760a-437b-b3fb-915dc3fc2296@redhat.com \
    --to=pabeni@redhat.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=andrew@lunn.ch \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.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