From: Andrew Lunn <andrew@lunn.ch>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: txgbe: Add build support for txgbe
Date: Sat, 28 May 2022 03:29:40 +0200 [thread overview]
Message-ID: <YpF7BJOV9B+VHB7h@lunn.ch> (raw)
In-Reply-To: <20220527063157.486686-1-jiawenwu@trustnetic.com>
> +
> +err_sw_init:
> + devm_iounmap(&pdev->dev, adapter->io_addr);
You should not need this. That is the point of the devm_ API, it gets
released automatically either when probe fails, or after the release
method is called.
> +static struct pci_driver txgbe_driver = {
> + .name = txgbe_driver_name,
> + .id_table = txgbe_pci_tbl,
> + .probe = txgbe_probe,
> + .remove = txgbe_remove,
> + .shutdown = txgbe_shutdown,
> +};
> +
> +/**
> + * txgbe_init_module - Driver Registration Routine
> + *
> + * txgbe_init_module is the first routine called when the driver is
> + * loaded. All it does is register with the PCI subsystem.
> + **/
> +static int __init txgbe_init_module(void)
> +{
> + int ret;
> +
> + ret = pci_register_driver(&txgbe_driver);
> + return ret;
> +}
> +
> +module_init(txgbe_init_module);
> +
> +/**
> + * txgbe_exit_module - Driver Exit Cleanup Routine
> + *
> + * txgbe_exit_module is called just before the driver is removed
> + * from memory.
> + **/
> +static void __exit txgbe_exit_module(void)
> +{
> + pci_unregister_driver(&txgbe_driver);
> +}
It looks like you should be able to use module_pci_driver().
Andrew
prev parent reply other threads:[~2022-05-28 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 6:31 [PATCH net-next v3] net: txgbe: Add build support for txgbe Jiawen Wu
2022-05-27 7:54 ` kernel test robot
2022-05-27 16:44 ` Leon Romanovsky
[not found] ` <001501d873ec$e4f13a00$aed3ae00$@trustnetic.com>
2022-05-30 12:28 ` Leon Romanovsky
2022-05-28 1:29 ` Andrew Lunn [this message]
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=YpF7BJOV9B+VHB7h@lunn.ch \
--to=andrew@lunn.ch \
--cc=jiawenwu@trustnetic.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).