From: Jakub Kicinski <kuba@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Meghana Malladi <m-malladi@ti.com>,
Richard Cochran <richardcochran@gmail.com>, <lokeshvutla@ti.com>,
<vigneshr@ti.com>, <javier.carrasco.cruz@gmail.com>,
<diogo.ivo@siemens.com>, <horms@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<srk@ti.com>, Roger Quadros <rogerq@kernel.org>,
<danishanwar@ti.com>
Subject: Re: Plan to validate supported flags in PTP core (Was: Re: [PATCH net v2 0/2] Fixes for perout configuration in IEP driver)
Date: Mon, 10 Mar 2025 17:25:41 +0100 [thread overview]
Message-ID: <20250310172541.30896e20@kernel.org> (raw)
In-Reply-To: <f7072ca6-47a7-4278-be5d-7cbd240fcd35@intel.com>
On Fri, 7 Mar 2025 15:48:27 -0800 Jacob Keller wrote:
> Would a series with individual patches for the 3 special cases + one
> patch to handle all the drivers that have no explicit flag check be
> acceptable? Or should I do individual patches for each driver and just
> break the series up? Or are we ok with just fixing this in next with the
> .supported_extts_flags change?
A mass rejection of unsupported settings feels like a net-next material
in general. Handling the more complex cases individually and the rest in
a big patch makes sense.
next prev parent reply other threads:[~2025-03-10 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 6:26 [PATCH net v2 0/2] Fixes for perout configuration in IEP driver Meghana Malladi
2025-02-19 6:27 ` [PATCH net v2 1/2] net: ti: icss-iep: Fix pwidth configuration for perout signal Meghana Malladi
2025-02-19 6:27 ` [PATCH net v2 2/2] net: ti: icss-iep: Fix phase offset " Meghana Malladi
2025-02-19 23:37 ` [PATCH net v2 0/2] Fixes for perout configuration in IEP driver Jacob Keller
2025-02-21 1:24 ` Jakub Kicinski
2025-02-21 22:22 ` Jacob Keller
2025-03-07 23:48 ` Plan to validate supported flags in PTP core (Was: Re: [PATCH net v2 0/2] Fixes for perout configuration in IEP driver) Jacob Keller
2025-03-10 16:25 ` Jakub Kicinski [this message]
2025-03-10 21:27 ` Jacob Keller
2025-02-25 9:42 ` [PATCH net v2 0/2] Fixes for perout configuration in IEP driver Malladi, Meghana
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=20250310172541.30896e20@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.