devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Russ Weight <russ.weight@linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
	Dent Project <dentproject@linuxfoundation.org>
Subject: Re: [PATCH net-next v2 3/8] net: pse-pd: Introduce PSE types enumeration
Date: Mon, 4 Dec 2023 13:51:31 +0100	[thread overview]
Message-ID: <20231204125131.GE981228@pengutronix.de> (raw)
In-Reply-To: <20231201-feature_poe-v2-3-56d8cac607fa@bootlin.com>

On Fri, Dec 01, 2023 at 06:10:25PM +0100, Kory Maincent wrote:
> +u32 pse_get_types(struct pse_control *psec);

I would add here some helper function. Something like:
pse_has_podl() or pse_has_c33()

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2023-12-04 12:51 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 17:10 [PATCH net-next v2 0/8] net: Add support for Power over Ethernet (PoE) Kory Maincent
2023-12-01 17:10 ` [PATCH net-next v2 1/8] net: pse-pd: Rectify and adapt the naming of admin_cotrol member of struct pse_control_config Kory Maincent
2023-12-03 18:19   ` Andrew Lunn
2023-12-04 12:19   ` Oleksij Rempel
2023-12-01 17:10 ` [PATCH net-next v2 2/8] ethtool: Expand Ethernet Power Equipment with c33 (PoE) alongside PoDL Kory Maincent
2023-12-03 18:27   ` Andrew Lunn
2023-12-04 12:27   ` Oleksij Rempel
2023-12-06  2:45   ` Bagas Sanjaya
2023-12-06  8:35     ` Köry Maincent
2023-12-06  4:23   ` kernel test robot
2023-12-01 17:10 ` [PATCH net-next v2 3/8] net: pse-pd: Introduce PSE types enumeration Kory Maincent
2023-12-03 18:31   ` Andrew Lunn
2023-12-04 12:43     ` Oleksij Rempel
2023-12-03 18:38   ` Andrew Lunn
2023-12-04 14:00     ` Köry Maincent
2023-12-04 12:51   ` Oleksij Rempel [this message]
2023-12-04 13:55     ` Köry Maincent
2023-12-01 17:10 ` [PATCH net-next v2 4/8] net: ethtool: pse-pd: Expand pse commands with the PSE PoE interface Kory Maincent
2023-12-03 18:45   ` Andrew Lunn
2023-12-04 15:28     ` Köry Maincent
2023-12-04 15:29     ` Oleksij Rempel
2023-12-06  4:18   ` Bagas Sanjaya
2023-12-01 17:10 ` [PATCH net-next v2 5/8] netlink: specs: Modify pse attribute prefix Kory Maincent
2023-12-01 17:10 ` [PATCH net-next v2 6/8] netlink: specs: Expand the pse netlink command with PoE interface Kory Maincent
2023-12-01 17:10 ` [PATCH net-next v2 7/8] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller Kory Maincent
2023-12-04 23:08   ` Oleksij Rempel
2023-12-05  6:36     ` Oleksij Rempel
2023-12-05 10:15       ` Köry Maincent
2023-12-05 13:31         ` Köry Maincent
2023-12-05 14:21           ` Oleksij Rempel
2023-12-05 15:23             ` Köry Maincent
2023-12-08  9:06               ` Köry Maincent
2023-12-05 12:54       ` Mark Brown
2023-12-01 17:10 ` [PATCH net-next v2 8/8] net: pse-pd: Add PD692x0 PSE controller driver Kory Maincent
2023-12-03 19:34   ` Andrew Lunn
2024-01-16  9:49     ` Köry Maincent
2024-01-16 13:18       ` Andrew Lunn
2024-01-16 14:12         ` Köry Maincent
2023-12-03 21:11   ` Christophe JAILLET
2023-12-04 22:16     ` Köry Maincent
2023-12-05 18:01       ` Christophe JAILLET
2023-12-06  8:41         ` Köry Maincent
2023-12-04 22:59   ` Oleksij Rempel
2023-12-05  6:45     ` Oleksij Rempel
2023-12-05 12:55       ` Mark Brown
2023-12-05 14:02         ` Oleksij Rempel
2023-12-05 15:57           ` Mark Brown
2023-12-21 15:36             ` Köry Maincent
2023-12-21 15:43               ` Mark Brown
2023-12-21 16:10                 ` Köry Maincent
2023-12-21 16:20                   ` Mark Brown
2023-12-21 17:19                     ` Köry Maincent
2023-12-21 17:34                       ` Mark Brown
2023-12-21 17:42                     ` Oleksij Rempel
2023-12-21 18:05                       ` Mark Brown
2023-12-22  7:54                         ` Oleksij Rempel
2023-12-05 21:35   ` kernel test robot

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=20231204125131.GE981228@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kory.maincent@bootlin.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=russ.weight@linux.dev \
    --cc=thomas.petazzoni@bootlin.com \
    /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).