From: danilokrummrich@dk-develop.de
To: Stefan Wahren <stefan.wahren@i2se.com>, Eric Anholt <eric@anholt.net>
Cc: rjui@broadcom.com, linux-clk@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com, sboyd@codeaurora.org,
linux-clk-owner@vger.kernel.org
Subject: Re: [PATCH v2] clk: bcm2835: remove remains from stub clk driver
Date: Wed, 07 Jun 2017 10:21:10 +0200 [thread overview]
Message-ID: <2bf353039cd7ccdac7ae4d415e75a569@dk-develop.de> (raw)
In-Reply-To: <978283989.189470.1496796963906@email.1und1.de>
On 2017-06-07 02:56, Stefan Wahren wrote:
>> Danilo Krummrich <danilokrummrich@dk-develop.de> hat am 6. Juni 2017
>> um 20:23 geschrieben:
>>
>>
>> This commit removes the fixed clocks introduced as a stub clock driver
>> added with commit 75fabc3f6448 ("ARM: bcm2835: add stub clock
>> driver").
>> Originally they were used to drive the AMBA bus and PL011 uart driver.
>> Now these clocks are derived by the CPRMAN clock driver and configured
>> in DT.
>>
>> Additionally, get rid of init_machine function in bcm2835 board file
>> as there's nothing to do any longer.
>>
>> Acked-by: Eric Anholt <eric@anholt.net>
>> Signed-off-by: Danilo Krummrich <danilokrummrich@dk-develop.de>
>> ---
>
> @Eric: How do we want to handle the potential conflict with this patch?
>
> [PATCH] irqchip/bcm2836: Move SMP startup code to arch/arm
> --
> To unsubscribe from this list: send the line "unsubscribe linux-clk" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Stefan, Eric,
If you like I can upload the patch rebased onto the mentioned one.
prev parent reply other threads:[~2017-06-07 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 18:23 [PATCH v2] clk: bcm2835: remove remains from stub clk driver Danilo Krummrich
2017-06-07 0:56 ` Stefan Wahren
2017-06-07 8:21 ` danilokrummrich [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=2bf353039cd7ccdac7ae4d415e75a569@dk-develop.de \
--to=danilokrummrich@dk-develop.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=linux-clk-owner@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sboyd@codeaurora.org \
--cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.