rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Lossin <benno.lossin@proton.me>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>,
	rust-for-linux@vger.kernel.org
Cc: andrew@lunn.ch, tmgross@umich.edu
Subject: Re: [RFC PATCH v4 0/2] net::phy add unified API for C22 and C45 registers
Date: Fri, 14 Jun 2024 12:53:33 +0000	[thread overview]
Message-ID: <7faa2f7c-32a6-4eb0-86e0-29f962fa47c7@proton.me> (raw)
In-Reply-To: <20240607052113.69026-1-fujita.tomonori@gmail.com>

On 07.06.24 07:21, FUJITA Tomonori wrote:
> add unified API for C22 and C45, reading/writing registers and
> genphy_read_status().
> 
> We could add methods specifically C45 like read/write_c45 and
> genphy_c45_read_status. Instead, this implements the unified API for
> C22 and C45 with a new reg module.
> 
> v4:
> - make reg module sealed
> - improve the comments
> - add examples
> - use error::to_result() to simplify some functions
> v3: https://lore.kernel.org/all/20240603.233954.1644803151268035787.fujita.tomonori@gmail.com/T/
> - move reg module to a new file (with MAINTAINERS updated)
> - rewrite commit log and subjects
> - rename Access trait to Register
> - add build error message for build_assert!
> - define the complete MMD list
> - drop new func for Mmd
> - remove trait GenPhyOps
> v2: https://lore.kernel.org/all/20240601043535.53545-2-fujita.tomonori@gmail.com/T/
> - add genphy helper support and split the patch
> - create a 'reg' module
> - define C22 according to the specs
> - handle C22 vendor specific registers
> - add const for C45 MMD
> v1: https://lore.kernel.org/all/20240530.145258.456915814420167538.fujita.tomonori@gmail.com/T/
> 
> FUJITA Tomonori (2):
>   rust: net::phy unified read/write API for C22 and C45 registers
>   rust: net::phy unified genphy_read_status function for C22 and C45
>     registers
> 
>  MAINTAINERS                      |   1 +
>  drivers/net/phy/ax88796b_rust.rs |   7 +-
>  rust/kernel/net/phy.rs           |  44 ++-----
>  rust/kernel/net/phy/reg.rs       | 219 +++++++++++++++++++++++++++++++
>  rust/uapi/uapi_helper.h          |   1 +
>  5 files changed, 234 insertions(+), 38 deletions(-)
>  create mode 100644 rust/kernel/net/phy/reg.rs
> 
> 
> base-commit: c790275b5edf5d8280ae520bda7c1f37da460c00
> --
> 2.34.1
> 

Both patches:

Reviewed-by: Benno Lossin <benno.lossin@proton.me>

---
Cheers,
Benno


  parent reply	other threads:[~2024-06-14 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  5:21 [RFC PATCH v4 0/2] net::phy add unified API for C22 and C45 registers FUJITA Tomonori
2024-06-07  5:21 ` [RFC PATCH v4 1/2] rust: net::phy unified read/write " FUJITA Tomonori
2024-06-13 17:59   ` Trevor Gross
2024-06-13 23:32     ` FUJITA Tomonori
2024-06-14  8:30       ` Benno Lossin
2024-06-14  9:57         ` FUJITA Tomonori
2024-06-07  5:21 ` [RFC PATCH v4 2/2] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-06-13 18:00   ` Trevor Gross
2024-06-14 12:53 ` Benno Lossin [this message]
2024-06-15  7:39   ` [RFC PATCH v4 0/2] net::phy add unified API " 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=7faa2f7c-32a6-4eb0-86e0-29f962fa47c7@proton.me \
    --to=benno.lossin@proton.me \
    --cc=andrew@lunn.ch \
    --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).