From: Sander Vanheule <sander@svanheule.net>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH] regmap: mdio: Reject invalid clause-22 addresses
Date: Mon, 07 Jun 2021 13:12:01 +0200 [thread overview]
Message-ID: <db0b921442d76ab64c52330a50664efd6d37c311.camel@svanheule.net> (raw)
In-Reply-To: <20210607110355.GA5705@sirena.org.uk>
On Mon, 2021-06-07 at 12:03 +0100, Mark Brown wrote:
> On Sat, Jun 05, 2021 at 10:31:18AM +0200, Sander Vanheule wrote:
> > Currently a regmap configuration for regmap-mdio must have a register
> > address width of 5 bits (cf. clause-22 register access). This is not
> > enforced on the provided register addresses, which would enable
> > clause-45 MDIO bus access, if the right bit packing is used.
>
> Please don't send new patches in reply to old patch serieses, it makes
> it hard to follow what's going on and what the current state of things
> is and makes it easy for things to get missed when threads get cleaned
> out.
Sorry, my bad. I usually have an updated cover letter in between updated
patches, but this was only one patch. I'll include a LKML-link to the previous
version(s) in the future, to keep an easy reference around.
Best,
Sander
next prev parent reply other threads:[~2021-06-07 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 18:25 [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Sander Vanheule
2021-06-03 18:25 ` [RFC PATCH 1/2] regmap: mdio: Clean up invalid clause-22 addresses Sander Vanheule
2021-06-03 18:25 ` [RFC PATCH 2/2] regmap: mdio: Add clause-45 support Sander Vanheule
2021-06-04 17:25 ` [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Mark Brown
2021-06-04 18:16 ` Sander Vanheule
2021-06-07 11:54 ` Mark Brown
2021-06-07 12:06 ` Sander Vanheule
2021-06-07 12:14 ` Andy Shevchenko
2021-06-04 20:38 ` Andrew Lunn
2021-06-04 23:55 ` Andrew Lunn
2021-06-05 8:31 ` [PATCH] regmap: mdio: Reject invalid clause-22 addresses Sander Vanheule
2021-06-07 11:03 ` Mark Brown
2021-06-07 11:12 ` Sander Vanheule [this message]
2021-06-09 11:51 ` Sander Vanheule
2021-06-08 16:06 ` [RFC PATCH 0/2] Clause-22/Clause-45 MDIO regmap support Mark Brown
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=db0b921442d76ab64c52330a50664efd6d37c311.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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).