From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 1/1] phy: add support for stingray PAXB PHY controller
Date: Thu, 9 Apr 2020 09:41:28 -0400 [thread overview]
Message-ID: <20200409134128.GC8031@bill-the-cat> (raw)
In-Reply-To: <20200402103812.7775-1-rayagonda.kokatanur@broadcom.com>
On Thu, Apr 02, 2020 at 04:08:12PM +0530, Rayagonda Kokatanur wrote:
> From: Srinath Mannam <srinath.mannam@broadcom.com>
>
> Add support for stingray PAXB PHY controller driver.
> This driver supports maximum 8 PAXB phys using pipemux data.
>
> Signed-off-by: Srinath Mannam <srinath.mannam@broadcom.com>
> Signed-off-by: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
> Reviewed-by: Stefan Roese <sr@denx.de>
> ---
> Changes from v2:
> -Address review comments from Stefan Roese,
> Rearrange the include files.
> Remove dm/device.h as its included part of dm.h.
>
> Changes from v1:
> -Address review comments from Stefan Roese,
> Use GENMASK() instead of hard code value.
> Remove unwanted struct declaration.
> Get pr_err() into single line.
>
> drivers/phy/Kconfig | 7 ++
> drivers/phy/Makefile | 1 +
> drivers/phy/phy-bcm-sr-pcie.c | 177 ++++++++++++++++++++++++++++++++++
The patch itself is fine but I think shows another problem. Can you
please add a patch that lists something relevant in the top-level
MAINTAINERS file and list this and all of the other drivers, etc, that
wouldn't just be listed in the board MAINATINERS file? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200409/5e1ed4d0/attachment.sig>
next prev parent reply other threads:[~2020-04-09 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 10:38 [PATCH v3 1/1] phy: add support for stingray PAXB PHY controller Rayagonda Kokatanur
2020-04-09 13:41 ` Tom Rini [this message]
2020-04-12 15:16 ` Rayagonda Kokatanur
2020-06-25 17:27 ` Rayagonda Kokatanur
2020-06-26 20:01 ` Tom Rini
2020-07-30 3:58 ` Rayagonda Kokatanur
2020-10-01 14:09 ` Tom Rini
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=20200409134128.GC8031@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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