[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLUPR0101MB15548ADB26B57D7944530FEFD0380@BLUPR0101MB1554.prod.exchangelabs.com>
Date: Thu, 30 Nov 2017 16:59:14 +0000
From: Hartley Sweeten <HartleyS@...ionengravers.com>
To: Lukasz Majewski <lukma@...x.de>,
Alexander Sverdlin <alexander.sverdlin@...il.com>,
Arnd Bergmann <arnd@...db.de>,
"arndbergmann@...il.com" <arndbergmann@...il.com>
CC: Russell King <linux@...linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Olof Johansson <olof@...om.net>,
"Linus Walleij" <linus.walleij@...aro.org>
Subject: RE: [PATCH v3 1/6] ARM: ep93xx: ts72xx: Use DEFINE_RES_MEM macros
where applicable
On Wednesday, November 29, 2017 5:45 PM, Lukasz Majewski wrote:
> This commit cleans up the code by using dedicated macros instead of full definitions.
>
> Signed-off-by: Lukasz Majewski <lukma@...x.de>
> Acked-by: Alexander Sverdlin <alexander.sverdlin@...il.com>
<snip>
> @@ -187,16 +187,8 @@ static struct platform_device ts72xx_rtc_device = { };
>
> static struct resource ts72xx_wdt_resources[] = {
> - {
> - .start = TS72XX_WDT_CONTROL_PHYS_BASE,
> - .end = TS72XX_WDT_CONTROL_PHYS_BASE + SZ_4K - 1,
> - .flags = IORESOURCE_MEM,
> - },
> - {
> - .start = TS72XX_WDT_FEED_PHYS_BASE,
> - .end = TS72XX_WDT_FEED_PHYS_BASE + SZ_4K - 1,
> - .flags = IORESOURCE_MEM,
> - },
> + DEFINE_RES_MEM(TS72XX_WDT_CONTROL_PHYS_BASE, SZ_4K),
> + DEFINE_RES_MEM(TS72XX_WDT_FEED_PHYS_BASE, SZ_4K),
> };
Lukasz,
The chunk above is already cleaned up in linux-next by:
commit 97c3bca922468996c864917c9a8ea6a410233985
ARM: ep93xx: tidy up TS-72xx Watchdog resources
Can you please rebase this series against linux-next?
I'm reviewing the rest of the series now and will reply with any other issues.
Thanks,
Hartley
Powered by blists - more mailing lists