[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=_6HsRbMGgWcyKqX-W=xpmw0njGoVRvRRe-c23o7sJyA@mail.gmail.com>
Date: Mon, 30 Oct 2023 13:07:07 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Boqun Feng <boqun.feng@...il.com>, FUJITA Tomonori <fujita.tomonori@...il.com>,
benno.lossin@...ton.me, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu, wedsonaf@...il.com
Subject: Re: [PATCH net-next v7 1/5] rust: core abstractions for network PHY drivers
On Sun, Oct 29, 2023 at 8:39 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> We have probably missed the merge window for v6.7. So there is around
Definitely missed. We aim to send our PRs in advance of the merge
window, e.g. this cycle it has already been sent.
But even if it wasn't, for `rust-next`, feature patches should be sent
early in the cycle anyway.
> 9 weeks to the next merge window. If a working bindgen is likely to be
> available by then, we should not bother with a workaround, just wait.
In general, it is better to avoid workarounds if something is going to
be implemented properly. However, `bindgen` is a third-party project
which we do not control.
In the case of the exhaustiveness check, they looked interested in the
feature, which is why I wanted to avoid the workaround if possible.
In this instance though, we don't even know yet what they think about
the feature we requested. We will give them some time to see what they
think, and then decide based on that.
Cheers,
Miguel
Powered by blists - more mailing lists