From: "G, GurucharanX" <gurucharanx.g@intel.com>
To: Joe Damato <jdamato@fastly.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector
Date: Fri, 14 Oct 2022 03:56:44 +0000 [thread overview]
Message-ID: <BYAPR11MB3367FA5154F38D11D5A1CAEEFC249@BYAPR11MB3367.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1665178723-52902-2-git-send-email-jdamato@fastly.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Joe Damato
> Sent: Saturday, October 8, 2022 3:09 AM
> To: intel-wired-lan@lists.osuosl.org
> Cc: netdev@vger.kernel.org; Joe Damato <jdamato@fastly.com>;
> kuba@kernel.org; davem@davemloft.net
> Subject: [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in
> i40e_q_vector
>
> Make it easy to figure out the IRQ number for a particular i40e_q_vector by
> storing the assigned IRQ in the structure itself.
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e.h | 1 +
> drivers/net/ethernet/intel/i40e/i40e_main.c | 1 +
> 2 files changed, 2 insertions(+)
>
Tested-by: Gurucharan <gurucharanx.g@intel.com> (A Contingent worker at Intel)
WARNING: multiple messages have this Message-ID (diff)
From: "G, GurucharanX" <gurucharanx.g@intel.com>
To: Joe Damato <jdamato@fastly.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector
Date: Fri, 14 Oct 2022 03:56:44 +0000 [thread overview]
Message-ID: <BYAPR11MB3367FA5154F38D11D5A1CAEEFC249@BYAPR11MB3367.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1665178723-52902-2-git-send-email-jdamato@fastly.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Joe Damato
> Sent: Saturday, October 8, 2022 3:09 AM
> To: intel-wired-lan@lists.osuosl.org
> Cc: netdev@vger.kernel.org; Joe Damato <jdamato@fastly.com>;
> kuba@kernel.org; davem@davemloft.net
> Subject: [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in
> i40e_q_vector
>
> Make it easy to figure out the IRQ number for a particular i40e_q_vector by
> storing the assigned IRQ in the structure itself.
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e.h | 1 +
> drivers/net/ethernet/intel/i40e/i40e_main.c | 1 +
> 2 files changed, 2 insertions(+)
>
Tested-by: Gurucharan <gurucharanx.g@intel.com> (A Contingent worker at Intel)
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-10-14 3:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 21:38 [next-queue v4 0/4] Add an i40e_napi_poll tracepoint Joe Damato
2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato
2022-10-07 21:38 ` [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector Joe Damato
2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato
2022-10-14 3:56 ` G, GurucharanX [this message]
2022-10-14 3:56 ` G, GurucharanX
2022-10-07 21:38 ` [next-queue v4 2/4] i40e: Record number TXes cleaned during NAPI Joe Damato
2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato
2022-10-14 3:54 ` G, GurucharanX
2022-10-14 3:54 ` G, GurucharanX
2022-10-07 21:38 ` [next-queue v4 3/4] i40e: Record number of RXes " Joe Damato
2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato
2022-10-14 3:55 ` G, GurucharanX
2022-10-14 3:55 ` G, GurucharanX
2022-10-07 21:38 ` [next-queue v4 4/4] i40e: Add i40e_napi_poll tracepoint Joe Damato
2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato
2022-10-14 3:56 ` G, GurucharanX
2022-10-14 3:56 ` G, GurucharanX
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=BYAPR11MB3367FA5154F38D11D5A1CAEEFC249@BYAPR11MB3367.namprd11.prod.outlook.com \
--to=gurucharanx.g@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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.