From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<David.Laight@ACULAB.COM>, <andrew@lunn.ch>,
<brett.creeley@amd.com>, <drivers@pensando.io>
Subject: Re: [PATCH v2 net-next 2/8] ionic: Keep interrupt affinity up to date
Date: Wed, 19 Jun 2024 17:43:17 -0700 [thread overview]
Message-ID: <20240619174317.6ca8a401@kernel.org> (raw)
In-Reply-To: <20240619003257.6138-3-shannon.nelson@amd.com>
On Tue, 18 Jun 2024 17:32:51 -0700 Shannon Nelson wrote:
> + if (!affinity_masks)
> + return -ENOMEM;
There's a tab here instead of a space
next prev parent reply other threads:[~2024-06-20 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 0:32 [PATCH v2 net-next 0/8] ionic: rework fix for doorbell miss Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 1/8] ionic: remove missed doorbell per-queue timer Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 2/8] ionic: Keep interrupt affinity up to date Shannon Nelson
2024-06-20 0:43 ` Jakub Kicinski [this message]
2024-06-20 1:30 ` Jakub Kicinski
2024-06-20 16:47 ` Nelson, Shannon
2024-06-19 0:32 ` [PATCH v2 net-next 3/8] ionic: add private workqueue per-device Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 4/8] ionic: add work item for missed-doorbell check Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 5/8] ionic: add per-queue napi_schedule for doorbell check Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 6/8] ionic: check for queue deadline in doorbell_napi_work Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 7/8] ionic: Use an u16 for rx_copybreak Shannon Nelson
2024-06-19 0:32 ` [PATCH v2 net-next 8/8] ionic: Only run the doorbell workaround for certain asic_type Shannon Nelson
2024-06-20 1:40 ` [PATCH v2 net-next 0/8] ionic: rework fix for doorbell miss patchwork-bot+netdevbpf
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=20240619174317.6ca8a401@kernel.org \
--to=kuba@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=andrew@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.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.