linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: remove unused device definitions
Date: Fri, 16 Dec 2016 10:28:48 +0100	[thread overview]
Message-ID: <ae8b13db-1150-0ef5-b97d-12ab54dbf151@pengutronix.de> (raw)
In-Reply-To: <3673316.UJiiIZbYgE@wuerfel>

On 12/16/2016 10:23 AM, Arnd Bergmann wrote:
> On Friday, December 16, 2016 10:10:49 AM CET Marc Kleine-Budde wrote:
>> On 12/16/2016 10:05 AM, Arnd Bergmann wrote:
>>> I stumbled over these during build testing, they are evidently
>>> not referenced anywhere any more.
>>>
>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>> ---
>>>  arch/arm/mach-imx/devices/platform-flexcan.c         |  9 ---------
>>>  arch/arm/mach-imx/devices/platform-sdhci-esdhc-imx.c | 10 ----------
>>>  2 files changed, 19 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-imx/devices/platform-flexcan.c b/arch/arm/mach-imx/devices/platform-flexcan.c
>>> index 55d61eaf63c6..8a1a2fc4ce10 100644
>>> --- a/arch/arm/mach-imx/devices/platform-flexcan.c
>>> +++ b/arch/arm/mach-imx/devices/platform-flexcan.c
>>> @@ -19,15 +19,6 @@
>>>  #define imx_flexcan_data_entry(soc, _id, _hwid, _size)			\
>>>  	[_id] = imx_flexcan_data_entry_single(soc, _id, _hwid, _size)
>>>  
>>> -#ifdef CONFIG_SOC_IMX25
>>> -const struct imx_flexcan_data imx25_flexcan_data[] __initconst = {
>>> -#define imx25_flexcan_data_entry(_id, _hwid)				\
>>> -	imx_flexcan_data_entry(MX25, _id, _hwid, SZ_16K)
>>> -	imx25_flexcan_data_entry(0, 1),
>>> -	imx25_flexcan_data_entry(1, 2),
>>> -};
>>> -#endif /* ifdef CONFIG_SOC_IMX25 */
>>> -
>>>  #ifdef CONFIG_SOC_IMX35
>>>  const struct imx_flexcan_data imx35_flexcan_data[] __initconst = {
>>>  #define imx35_flexcan_data_entry(_id, _hwid)				\
>>
>> What about the imx35 variant?
>>
> 
> It's used from here:
> 
> arch/arm/mach-imx/mach-pcm043.c:        imx35_add_flexcan1();

Yes, you're right. Sorry, I searched before my 2nd tee.

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   |

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161216/35018b9c/attachment.sig>

  reply	other threads:[~2016-12-16  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  9:05 [PATCH] ARM: imx: remove unused device definitions Arnd Bergmann
2016-12-16  9:10 ` Marc Kleine-Budde
2016-12-16  9:23   ` Arnd Bergmann
2016-12-16  9:28     ` Marc Kleine-Budde [this message]
2017-01-02  7:28 ` Shawn Guo

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=ae8b13db-1150-0ef5-b97d-12ab54dbf151@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).