rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: FUJITA Tomonori <fujita.tomonori@gmail.com>,
	rust-for-linux@vger.kernel.org,  benno.lossin@proton.me,
	tmgross@umich.edu
Subject: Re: [PATCH v3 1/2] rust: net::phy unified read/write API for C22 and C45 registers
Date: Mon, 3 Jun 2024 16:03:40 +0200	[thread overview]
Message-ID: <CANiq72myfWCyJP2MaDWzuYYvFF3-E3e-Ukowe0c4o0qRcBWSaA@mail.gmail.com> (raw)
In-Reply-To: <7551876f-a7ff-40e9-9458-8b4b205521e3@lunn.ch>

On Mon, Jun 3, 2024 at 4:02 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> I've not been monitoring kernel rust too much. What is the state of
> the build system changes? Can we put Rust code in the subsystems yet?

In progress.

Cheers,
Miguel

  reply	other threads:[~2024-06-03 14:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02 23:17 [PATCH v3 0/2] net::phy add unified API for C22 and C45 FUJITA Tomonori
2024-06-02 23:17 ` [PATCH v3 1/2] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-06-03 14:02   ` Andrew Lunn
2024-06-03 14:03     ` Miguel Ojeda [this message]
2024-06-06  8:41   ` Trevor Gross
2024-06-06 23:02     ` FUJITA Tomonori
2024-06-06 23:43       ` Trevor Gross
2024-06-06 23:59         ` FUJITA Tomonori
2024-06-02 23:17 ` [PATCH v3 2/2] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-06-03 14:09   ` Andrew Lunn
2024-06-03 14:39     ` FUJITA Tomonori
2024-06-03 14:45       ` Andrew Lunn
2024-06-06  8:52   ` Trevor Gross
2024-06-06 23:07     ` FUJITA Tomonori

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=CANiq72myfWCyJP2MaDWzuYYvFF3-E3e-Ukowe0c4o0qRcBWSaA@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=benno.lossin@proton.me \
    --cc=fujita.tomonori@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).