From: Jiri Pirko <jiri@resnulli.us>
To: Praveen Kaligineedi <pkaligineedi@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
Jeroen de Borst <jeroendb@google.com>
Subject: Re: [PATCH net-next 1/1] gve: Fix gve interrupt names
Date: Wed, 1 Feb 2023 10:11:25 +0100 [thread overview]
Message-ID: <Y9osvYPMdw3uKjA1@nanopsycho> (raw)
In-Reply-To: <20230131213714.588281-1-pkaligineedi@google.com>
Tue, Jan 31, 2023 at 10:37:14PM CET, pkaligineedi@google.com wrote:
>IRQs are currently requested before the netdevice is registered
>and a proper name is assigned to the device. Changing interrupt
>name to avoid using the format string in the name.
>
>Fixes: 893ce44df565 ("gve: Add basic driver framework for Compute Engine Virtual NIC")
>Signed-off-by: Praveen Kaligineedi <pkaligineedi@google.com>
>Reviewed-by: Jeroen de Borst <jeroendb@google.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2023-02-01 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 21:37 [PATCH net-next 1/1] gve: Fix gve interrupt names Praveen Kaligineedi
2023-02-01 9:11 ` Jiri Pirko [this message]
2023-02-02 5:18 ` 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=Y9osvYPMdw3uKjA1@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jeroendb@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkaligineedi@google.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).