netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: "mengyuanlou@net-swift.com" <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, jiawenwu@trustnetic.com,
	duanqiangwen@net-swift.com
Subject: Re: [RESEND,PATCH net-next v9 5/6] net: ngbe: add sriov function support
Date: Tue, 25 Mar 2025 15:20:57 +0000	[thread overview]
Message-ID: <20250325152057.GS892515@horms.kernel.org> (raw)
In-Reply-To: <D3FEA7AF-1990-40DF-903C-30790ED782E9@net-swift.com>

On Tue, Mar 25, 2025 at 10:36:00AM +0800, mengyuanlou@net-swift.com wrote:
> > 2025年3月25日 03:21,Simon Horman <horms@kernel.org> 写道:
> > On Mon, Mar 24, 2025 at 10:00:32AM +0800, Mengyuan Lou wrote:

...

> That’s right.
> > If so, I believe this addresses Jakub's concerns.
> > 
> > And given that we are at v9 and the last feedback of substance was the
> > above comment from Jakub, I think this looks good.
> > 
> > Reviewed-by: Simon Horman <horms@kernel.org>
> > 
> > But I would like to say that there could be some follow-up to align
> > the comment and the names of the handlers:
> > 
> > * "other" seems to be used as a synonym for "misc".
> >  Perhaps ngbe_msix_misc() ?
> > * "common" seems to only process "misc" interrupts.
> >  Perhaps __ngbe_msix_misc() ?
> > * msic seems to be a misspelling of misc.
> > 
> 
> 
> >> +static irqreturn_t ngbe_msix_misc(int __always_unused irq, void *data)
> >> +{
> >>  ...
> >> + return __ngbe_msix_misc(wx, eicr);
> >> +}
> >> +
> >> +static irqreturn_t ngbe_misc_and_queue(int __always_unused irq, void *data)
> >> +{
> >>  ...
> >> + return __ngbe_msix_misc(wx, eicr);
> 
> 
> if (wx->num_vfs == 7)
> 	err = request_irq(wx->msix_entry->vector,
> 			  ngbe_misc_and_queue, 0, netdev->name, wx);
> else
> 	err = request_irq(wx->msix_entry->vector,
> 			  ngbe_msix_misc, 0, netdev->name, wx);
> 
> It’s more appropriate.
> 
> Thanks!

Yes, thanks.

And I also think it would also be nice to rename ngbe_msix_common()
as __ngbe_msix_misc().

But please hold off with any updates or follow-up as net-next is now closed
for the merge window.

Link: https://lore.kernel.org/netdev/20250324075539.2b60eb42@kernel.org/

...

  reply	other threads:[~2025-03-25 15:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250324020033.36225-1-mengyuanlou@net-swift.com>
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 1/6] net: libwx: Add mailbox api for wangxun pf drivers Mengyuan Lou
2025-03-24 19:30   ` Simon Horman
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 2/6] net: libwx: Add sriov api for wangxun nics Mengyuan Lou
2025-03-24 19:31   ` Simon Horman
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 3/6] net: libwx: Redesign flow when sriov is enabled Mengyuan Lou
2025-03-24 19:32   ` Simon Horman
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 4/6] net: libwx: Add msg task func Mengyuan Lou
2025-03-24 19:32   ` Simon Horman
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 5/6] net: ngbe: add sriov function support Mengyuan Lou
2025-03-24 19:21   ` Simon Horman
2025-03-25  2:36     ` mengyuanlou
2025-03-25 15:20       ` Simon Horman [this message]
2025-03-24  2:00 ` [RESEND,PATCH net-next v9 6/6] net: txgbe: " Mengyuan Lou
2025-03-24 19:32   ` 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=20250325152057.GS892515@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=duanqiangwen@net-swift.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kuba@kernel.org \
    --cc=mengyuanlou@net-swift.com \
    --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 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).