netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Behera, VIVEK" <vivek.behera@siemens.com>
Cc: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
	"Keller, Jacob E" <jacob.e.keller@intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 iwl-net] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function
Date: Wed, 10 Dec 2025 17:57:42 +0900	[thread overview]
Message-ID: <20251210175742.3dba9318@kernel.org> (raw)
In-Reply-To: <AS1PR10MB5392FCA415A38B9DD7BB5F218FA0A@AS1PR10MB5392.EURPRD10.PROD.OUTLOOK.COM>

On Wed, 10 Dec 2025 07:50:55 +0000 Behera, VIVEK wrote:
> Changes in v5:
> - Updated comment style from multi-star to standard /* */ as suggested by  Aleksandr.
> 
> From ab2583ff8a17405d3aa6caf4df1c4fdfb21f5e98 Mon Sep 17 00:00:00 2001
> From: Vivek Behera <vivek.behera@siemens.com>
> Date: Fri, 5 Dec 2025 10:26:05 +0100
> Subject: [PATCH v5] [iwl-net] igc: Fix trigger of incorrect irq in
>  igc_xsk_wakeup function

The formatting of your submissions is all wrong. And you don't follow
our guidance:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html

Perhaps drop netdev@ and linux-kernel@ from the CC and Intel folks can
help guide/teach you on their own list. Until you have the posting
down..

  reply	other threads:[~2025-12-10  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 12:39 [PATCH] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function Behera, VIVEK
     [not found] ` <IA3PR11MB8986860C6B817F4130A4E0DBE5A7A@IA3PR11MB8986.namprd11.prod.outlook.com>
2025-12-06 12:03   ` Behera, VIVEK
2025-12-07 15:46 ` [PATCH v2] igc: Enhance xsk wakeup for split IRQ and fix PTP TX wakeup Behera, VIVEK
2025-12-08 23:53 ` [PATCH] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function Jacob Keller
2025-12-09  6:03   ` Behera, VIVEK
2025-12-09  6:46     ` [PATCH v3 iwl-net] " Behera, VIVEK
2025-12-09  8:05       ` Loktionov, Aleksandr
2025-12-10  7:09         ` AW: [PATCH v4 " Behera, VIVEK
2025-12-10  7:16         ` [PATCH v3 " Loktionov, Aleksandr
2025-12-10  7:50           ` AW: [PATCH v5 " Behera, VIVEK
2025-12-10  8:57             ` Jakub Kicinski [this message]
2025-12-10 10:16             ` Kurt Kanzenbach
2025-12-10 16:41             ` [Intel-wired-lan] " Paul Menzel
2025-12-10 10:15       ` [PATCH v3 " Kwapulinski, Piotr

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=20251210175742.3dba9318@kernel.org \
    --to=kuba@kernel.org \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vivek.behera@siemens.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).