netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<andrew+netdev@lunn.ch>, <horms@kernel.org>
Subject: Re: [PATCH net-next 2/2] MAINTAINERS: downgrade Ethernet NIC drivers without CI reporting
Date: Fri, 10 Jan 2025 16:58:05 +0100	[thread overview]
Message-ID: <7ccdec6d-ddba-49ac-b78d-035a33af047b@intel.com> (raw)
In-Reply-To: <20250110005223.3213487-2-kuba@kernel.org>

From: Jakub Kicinski <kuba@kernel.org>
Date: Thu,  9 Jan 2025 16:52:20 -0800

> Per previous change downgrade all NIC drivers (discreet, embedded,

                                                 ^^^^^^^^

discrete?

> SoC components, virtual) which don't report test results to CI
> from Supported to Maintained.
> 
> Also include all components or building blocks of NIC drivers
> (separate entries for "shared" code, subsystem support like PTP
> or entries for specific offloads etc.)
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Acked-by: Alexander Lobakin <aleksander.lobakin@intel.com>

I really hope our (Intel's) CI/CD folks will wake up soon.

> ---
>  MAINTAINERS | 106 ++++++++++++++++++++++++++--------------------------
>  1 file changed, 53 insertions(+), 53 deletions(-)

Thanks,
Olek

  parent reply	other threads:[~2025-01-10 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  0:52 [PATCH net-next 1/2] docs: netdev: document requirements for Supported status Jakub Kicinski
2025-01-10  0:52 ` [PATCH net-next 2/2] MAINTAINERS: downgrade Ethernet NIC drivers without CI reporting Jakub Kicinski
2025-01-10 10:39   ` Simon Horman
2025-01-10 15:58   ` Alexander Lobakin [this message]
2025-01-10 10:39 ` [PATCH net-next 1/2] docs: netdev: document requirements for Supported status Simon Horman

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=7ccdec6d-ddba-49ac-b78d-035a33af047b@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).