From: Jakub Kicinski <kuba@kernel.org>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org,
Milena Olech <milena.olech@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Mina Almasry <almasrymina@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ijae Kim <ae878000@gmail.com>
Subject: Re: [Intel-wired-lan] [PATCH v3 net] idpf: disable PTM on probe failure and on remove
Date: Tue, 21 Jul 2026 17:47:21 -0700 [thread overview]
Message-ID: <20260721174721.3db8fe7d@kernel.org> (raw)
In-Reply-To: <20260721174642.7749143e@kernel.org>
On Tue, 21 Jul 2026 17:46:42 -0700 Jakub Kicinski wrote:
> On Mon, 20 Jul 2026 23:35:10 +0900 Myeonghun Pak wrote:
> > Subject: [PATCH v3 net] idpf: disable PTM on probe failure and on remove
>
> Please try not to change the subject of your patches when you respin.
> It breaks version tracking. Ideally you'd tag this as iwl not net.
> We don't apply intel NIC patches directly.
Of course this is for future reference. Do not repost this unless
someone gives you real feedback.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org,
Milena Olech <milena.olech@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Mina Almasry <almasrymina@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH v3 net] idpf: disable PTM on probe failure and on remove
Date: Tue, 21 Jul 2026 17:47:21 -0700 [thread overview]
Message-ID: <20260721174721.3db8fe7d@kernel.org> (raw)
In-Reply-To: <20260721174642.7749143e@kernel.org>
On Tue, 21 Jul 2026 17:46:42 -0700 Jakub Kicinski wrote:
> On Mon, 20 Jul 2026 23:35:10 +0900 Myeonghun Pak wrote:
> > Subject: [PATCH v3 net] idpf: disable PTM on probe failure and on remove
>
> Please try not to change the subject of your patches when you respin.
> It breaks version tracking. Ideally you'd tag this as iwl not net.
> We don't apply intel NIC patches directly.
Of course this is for future reference. Do not repost this unless
someone gives you real feedback.
next prev parent reply other threads:[~2026-07-22 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:35 [PATCH v3 net] idpf: disable PTM on probe failure and on remove Myeonghun Pak
2026-07-20 14:35 ` [Intel-wired-lan] " Myeonghun Pak
2026-07-22 0:46 ` Jakub Kicinski
2026-07-22 0:46 ` Jakub Kicinski
2026-07-22 0:47 ` Jakub Kicinski [this message]
2026-07-22 0:47 ` Jakub Kicinski
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=20260721174721.3db8fe7d@kernel.org \
--to=kuba@kernel.org \
--cc=ae878000@gmail.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhun512@gmail.com \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.