From: Simon Horman <horms@kernel.org>
To: Nelson Escobar <neescoba@cisco.com>
Cc: netdev@vger.kernel.org, satishkh@cisco.com, johndale@cisco.com
Subject: Re: [Patch net-next 1/5] enic: Create enic_wq/rq structures to bundle per wq/rq data
Date: Tue, 22 Oct 2024 17:35:46 +0100 [thread overview]
Message-ID: <20241022163546.GD402847@kernel.org> (raw)
In-Reply-To: <20241022041707.27402-2-neescoba@cisco.com>
On Mon, Oct 21, 2024 at 09:17:03PM -0700, Nelson Escobar wrote:
> Bundling the wq/rq specific data into dedicated enic_wq/rq structures
> cleans up the enic structure and simplifies future changes related to
> wq/rq.
>
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> Signed-off-by: John Daley <johndale@cisco.com>
> Signed-off-by: Satish Kharat <satishkh@cisco.com>
Reviewed-by: Simon Horman <horms@kernel.org>
In future please use ./scripts/get_maintainer.pl FILE.patch
to generate the CC list for a patch. Likewise for this
entire patchset. b4 can help with this.
next prev parent reply other threads:[~2024-10-22 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 4:17 [Patch net-next 0/5] Use all the resources configured on VIC Nelson Escobar
2024-10-22 4:17 ` [Patch net-next 1/5] enic: Create enic_wq/rq structures to bundle per wq/rq data Nelson Escobar
2024-10-22 16:35 ` Simon Horman [this message]
2024-10-22 4:17 ` [Patch net-next 2/5] enic: Make MSI-X I/O interrupts come after the other required ones Nelson Escobar
2024-10-22 16:36 ` Simon Horman
2024-10-22 4:17 ` [Patch net-next 3/5] enic: Save resource counts we read from HW Nelson Escobar
2024-10-22 16:36 ` Simon Horman
2024-10-22 4:17 ` [Patch net-next 4/5] enic: Allocate arrays in enic struct based on VIC config Nelson Escobar
2024-10-22 16:36 ` Simon Horman
2024-10-22 16:57 ` Kalesh Anakkur Purayil
2024-10-22 4:17 ` [Patch net-next 5/5] enic: Adjust used MSI-X wq/rq/cq/interrupt resources in a more robust way Nelson Escobar
2024-10-22 16:36 ` 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=20241022163546.GD402847@kernel.org \
--to=horms@kernel.org \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=satishkh@cisco.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).