From: Leon Romanovsky <leon@kernel.org>
To: Yu Liao <liaoyu15@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, liwei391@huawei.com
Subject: Re: [PATCH net-next] pds_core: remove redundant pci_clear_master()
Date: Wed, 16 Aug 2023 09:38:20 +0300 [thread overview]
Message-ID: <20230816063820.GV22185@unreal> (raw)
In-Reply-To: <20230816013802.2985145-1-liaoyu15@huawei.com>
On Wed, Aug 16, 2023 at 09:38:02AM +0800, Yu Liao wrote:
> pci_disable_device() involves disabling PCI bus-mastering. So remove
> redundant pci_clear_master().
I would say that this commit message needs to be more descriptive and
explain why pci_disable_device() will actually disable PCI in these
flows.
According to the doc and code:
2263 * Note we don't actually disable the device until all callers of
2264 * pci_enable_device() have called pci_disable_device().
Thanks
>
> Signed-off-by: Yu Liao <liaoyu15@huawei.com>
> ---
> drivers/net/ethernet/amd/pds_core/main.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/amd/pds_core/main.c b/drivers/net/ethernet/amd/pds_core/main.c
> index 672757932246..ffe619cff413 100644
> --- a/drivers/net/ethernet/amd/pds_core/main.c
> +++ b/drivers/net/ethernet/amd/pds_core/main.c
> @@ -374,7 +374,6 @@ static int pdsc_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> return 0;
>
> err_out_clear_master:
> - pci_clear_master(pdev);
> pci_disable_device(pdev);
> err_out_free_ida:
> ida_free(&pdsc_ida, pdsc->uid);
> @@ -439,7 +438,6 @@ static void pdsc_remove(struct pci_dev *pdev)
> pci_release_regions(pdev);
> }
>
> - pci_clear_master(pdev);
> pci_disable_device(pdev);
>
> ida_free(&pdsc_ida, pdsc->uid);
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2023-08-16 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 1:38 [PATCH net-next] pds_core: remove redundant pci_clear_master() Yu Liao
2023-08-16 6:38 ` Leon Romanovsky [this message]
2023-08-16 9:39 ` Yu Liao
2023-08-16 10:39 ` Leon Romanovsky
2023-08-17 1:07 ` Yu Liao
2023-08-16 14:02 ` Nelson, Shannon
2023-08-17 1:11 ` Yu Liao
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=20230816063820.GV22185@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=liaoyu15@huawei.com \
--cc=liwei391@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).