From: vz@mleia•com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH for v4.7] arm: lpc32xx: remove leftovers of legacy clock source and provider drivers
Date: Mon, 4 Apr 2016 20:03:43 +0300 [thread overview]
Message-ID: <57029E6F.5050300@mleia.com> (raw)
In-Reply-To: <1459784558.25564.6.camel@localhost>
Hi Sylvain,
On 04.04.2016 18:42, Sylvain Lemieux wrote:
> Hi Vladimir,
>
> On Thu, 2016-03-03 at 04:46 +0200, Vladimir Zapolskiy wrote:
>> After switching the platform to common clock framework there is no
>> more need to keep dead code in arch/arm/mach-lpc32xx, which glued
>> legacy clock source and clock provider drivers, remove the leftovers.
>>
>> Signed-off-by: Vladimir Zapolskiy <vz@mleia•com>
>> ---
>> arch/arm/mach-lpc32xx/common.c | 95 ------------------------------------------
>> arch/arm/mach-lpc32xx/common.h | 23 +---------
>> 2 files changed, 1 insertion(+), 117 deletions(-)
>>
>> diff --git a/arch/arm/mach-lpc32xx/common.h b/arch/arm/mach-lpc32xx/common.h
>> index 1cd8853..f03683f 100644
>> --- a/arch/arm/mach-lpc32xx/common.h
>> +++ b/arch/arm/mach-lpc32xx/common.h
>> @@ -19,38 +19,17 @@
>>
>> #include <linux/reboot.h>
>>
> It is possible to remove "reboot.h";
> do you want me to send a separate patch for it?
I assume that removing of this #include entry is independent from my patch,
and related to gone lpc32xx_restart, please send a fixup on top of v4.6-r1.
>> extern void lpc23xx_restart(enum reboot_mode, const char *);
>>
> The patch does not apply on 4.6-rc1;
> can you send a version 2 of your patch based on the latest mainline?
>
Right, the change requires a rebase, I'll send v2 shortly.
Thanks!
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-04-04 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 2:46 [PATCH for v4.7] arm: lpc32xx: remove leftovers of legacy clock source and provider drivers Vladimir Zapolskiy
2016-04-04 15:42 ` Sylvain Lemieux
2016-04-04 17:03 ` Vladimir Zapolskiy [this message]
2016-04-04 17:10 ` Sylvain Lemieux
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=57029E6F.5050300@mleia.com \
--to=vz@mleia$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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