From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Faiz Abbas <faiz_abbas@ti.com>,
wg@grandegger.com, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
nsekhar@ti.com, fcooper@ti.com, robh@kernel.org,
Wenyou.Yang@microchip.com, sergei.shtylyov@cogentembedded.com,
linux-omap@vger.kernel.org, b29396@freescale.com
Subject: Re: [PATCH v8 3/5] can: m_can: Move allocation of net device to probe
Date: Tue, 16 Jan 2018 14:03:04 +0100 [thread overview]
Message-ID: <caa11848-3c69-1229-e4b8-09e51cebe739@pengutronix.de> (raw)
In-Reply-To: <1516102634-6771-4-git-send-email-faiz_abbas@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 1396 bytes --]
On 01/16/2018 12:37 PM, Faiz Abbas wrote:
> With the version no longer required to allocate the net device, it can
> be moved to probe and the alloc_m_can_dev() function can be simplified.
>
> Therefore, move the allocation of net device to probe and change
> alloc_m_can_dev() to setup_m_can_dev().
>
> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
> ---
> drivers/net/can/m_can/m_can.c | 30 +++++++++++++-----------------
> 1 file changed, 13 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
> index 893edbb..ebb74de 100644
> --- a/drivers/net/can/m_can/m_can.c
> +++ b/drivers/net/can/m_can/m_can.c
> @@ -1207,25 +1207,20 @@ static bool m_can_niso_supported(const struct m_can_priv *priv)
> return !niso_timeout;
> }
>
> -static struct net_device *alloc_m_can_dev(struct platform_device *pdev,
> - void __iomem *addr, u32 tx_fifo_size)
> +static int setup_m_can_dev(struct platform_device *pdev, struct net_device *dev,
> + void __iomem *addr)
Renamed to m_can_dev_setup() for consistent namespace.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-16 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:37 [PATCH v8 0/5] Add MCAN Support for Dra76 platform Faiz Abbas
2018-01-16 11:37 ` [PATCH v8 1/5] dt-bindings: can: m_can: Document new can transceiver binding Faiz Abbas
2018-01-16 11:37 ` [PATCH v8 2/5] dt-bindings: can: can-transceiver: Document new binding Faiz Abbas
2018-01-16 11:37 ` [PATCH v8 3/5] can: m_can: Move allocation of net device to probe Faiz Abbas
2018-01-16 13:03 ` Marc Kleine-Budde [this message]
2018-01-16 14:00 ` Marc Kleine-Budde
2018-01-16 11:37 ` [PATCH v8 4/5] can: m_can: Add PM Support Faiz Abbas
2018-01-16 12:57 ` Marc Kleine-Budde
2018-01-16 11:37 ` [PATCH v8 5/5] can: m_can: Support higher speed CAN-FD bitrates Faiz Abbas
2018-01-16 14:12 ` [PATCH v8 0/5] Add MCAN Support for Dra76 platform Marc Kleine-Budde
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=caa11848-3c69-1229-e4b8-09e51cebe739@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Wenyou.Yang@microchip.com \
--cc=b29396@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=fcooper@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=wg@grandegger.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
all inboxes | Powered by JetHome®