From: Michal Kubiak <michal.kubiak@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <horms@kernel.org>, <andrew@lunn.ch>,
<netdev@vger.kernel.org>, <przemyslaw.kitszel@intel.com>,
<mengyuanlou@net-swift.com>, <duanqiangwen@net-swift.com>
Subject: Re: [PATCH net v3 2/4] net: txgbe: remove separate irq request for MSI and INTx
Date: Wed, 3 Jul 2024 16:53:21 +0200 [thread overview]
Message-ID: <ZoVl4YqVG4Hv94qU@localhost.localdomain> (raw)
In-Reply-To: <ZoVTJIGmBMP4gCD3@localhost.localdomain>
On Wed, Jul 03, 2024 at 03:33:24PM +0200, Michal Kubiak wrote:
> > if (!(pdev->msix_enabled)) {
> > - free_irq(pdev->irq, wx);
> > + if (!wx->misc_irq_domain)
> > + free_irq(pdev->irq, wx);
>
> Does it mean "pdev->irq" will never be freed if you set misc_irq_domain
> to "true"? It seems you set it to true always during the initializaion,
> in "txgbe_setup_misc_irq()"?
[...]
>
>
> I don't think that introducing a kind of global variable to determine the call
> context is a good idea.
> Also, it seems that member is always true after the "probe" context is
> completed, isn't it?
>
[...]
>
> Is there any chance that member will be set back to "false" after the
> initialization is completed?
>
>
> Thanks,
> Michal
>
OK, I think I understood that change better. You probably just want to
distinguish the calling your library function between "ngbe" and "txgbe"
drivers.
In such a case using a structure member in your board structure seems to
be justified. If so, please ignore my questions.
Anyway, I didn't notice that the patch is already applied to the tree
before I sent my comment. Apologies for that.
Thanks,
Michal
next prev parent reply other threads:[~2024-07-03 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 7:14 [PATCH net v3 0/4] net: txgbe: fix MSI and INTx interrupts Jiawen Wu
2024-07-01 7:14 ` [PATCH net v3 1/4] net: txgbe: initialize num_q_vectors for MSI/INTx interrupts Jiawen Wu
2024-07-02 15:21 ` Michal Kubiak
2024-07-03 1:45 ` Jiawen Wu
2024-07-01 7:14 ` [PATCH net v3 2/4] net: txgbe: remove separate irq request for MSI and INTx Jiawen Wu
2024-07-03 13:33 ` Michal Kubiak
2024-07-03 14:53 ` Michal Kubiak [this message]
2024-07-01 7:14 ` [PATCH net v3 3/4] net: txgbe: add extra handle for MSI/INTx into thread irq handle Jiawen Wu
2024-07-01 7:14 ` [PATCH net v3 4/4] net: txgbe: free isb resources at the right time Jiawen Wu
2024-07-02 14:10 ` [PATCH net v3 0/4] net: txgbe: fix MSI and INTx interrupts 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=ZoVl4YqVG4Hv94qU@localhost.localdomain \
--to=michal.kubiak@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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