From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v3 20/22] clk: renesas: r8a7778: Remove obsolete r8a7778_clocks_init()
Date: Thu, 2 Jun 2016 09:13:36 +0200 [thread overview]
Message-ID: <CAMuHMdWNZ8tV1Tc6HGL4qqs-hg6G5f1M5AYuB05Mb-JQPrPf4A@mail.gmail.com> (raw)
In-Reply-To: <9f19c6e5-54d1-abd8-b666-bdf1a502d9c4@de.bosch.com>
Hi Dirk,
On Thu, Jun 2, 2016 at 7:54 AM, Dirk Behme <dirk.behme@de.bosch.com> wrote:
> On 01.06.2016 21:21, Geert Uytterhoeven wrote:
>> The R-Car M1A board code no longer calls r8a7778_clocks_init().
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>> v3:
>> - New.
>> ---
>> drivers/clk/renesas/clk-r8a7778.c | 13 -------------
>> include/linux/clk/renesas.h | 1 -
>> 2 files changed, 14 deletions(-)
>>
>> diff --git a/drivers/clk/renesas/clk-r8a7778.c
>> b/drivers/clk/renesas/clk-r8a7778.c
>> index 07ea411098a75ad1..886a8380e91247a1 100644
>> --- a/drivers/clk/renesas/clk-r8a7778.c
>> +++ b/drivers/clk/renesas/clk-r8a7778.c
>> @@ -143,16 +143,3 @@ static void __init r8a7778_cpg_clocks_init(struct
>> device_node *np)
>>
>> CLK_OF_DECLARE(r8a7778_cpg_clks, "renesas,r8a7778-cpg-clocks",
>> r8a7778_cpg_clocks_init);
>> -
>> -void __init r8a7778_clocks_init(u32 mode)
>> -{
>> - BUG_ON(!(mode & BIT(19)));
>> -
>> - cpg_mode_rates = (!!(mode & BIT(18)) << 2) |
>> - (!!(mode & BIT(12)) << 1) |
>> - (!!(mode & BIT(11)));
>> - cpg_mode_divs = (!!(mode & BIT(2)) << 1) |
>> - (!!(mode & BIT(1)));
>> -
>> - of_clk_init(NULL);
>> -}
>
> Just a question on how you structured the patches: Is there a special reason
> why you do the adding of new code and the removal of dead code in two
> patches?
>
> Having both in one patch normally makes it more obvious which old code is
> replaced by which new code.
>
> An example: In patch
>
> [PATCH/RFC v3 11/22] clk: renesas: r8a7778: Obtain mode pin values using
> R-Car RST driver
>
> I wondered where the section
>
> + BUG_ON(!(mode & BIT(19)));
> +
> + cpg_mode_rates = (!!(mode & BIT(18)) << 2) |
> + (!!(mode & BIT(12)) << 1) |
> + (!!(mode & BIT(11)));
> + cpg_mode_divs = (!!(mode & BIT(2)) << 1) |
> + (!!(mode & BIT(1)));
>
> comes from. This becomes obvious with this patch 20/22. But it's 9 patches
> later ;) So why don't make the whole replacement visible in one patch?
Because that would break bisection.
Path 20 depends on patch 17, which depends on patch 11.
These three can't be a single patch because they touch multiple subsystems.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-06-02 7:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464808880-343-1-git-send-email-geert+renesas@glider.be>
[not found] ` <1464808880-343-2-git-send-email-geert+renesas@glider.be>
2016-06-02 5:40 ` [PATCH/RFC v3 01/22] reset: Add renesas,rst DT bindings Dirk Behme
2016-06-02 21:47 ` Laurent Pinchart
2016-06-10 7:52 ` Geert Uytterhoeven
[not found] ` <1464808880-343-21-git-send-email-geert+renesas@glider.be>
2016-06-02 5:54 ` [PATCH/RFC v3 20/22] clk: renesas: r8a7778: Remove obsolete r8a7778_clocks_init() Dirk Behme
2016-06-02 7:13 ` Geert Uytterhoeven [this message]
2016-06-02 5:57 ` [PATCH/RFC v3 00/22] soc: renesas: Add R-Car RST driver for obtaining mode pin state Dirk Behme
[not found] ` <1464808880-343-3-git-send-email-geert+renesas@glider.be>
2016-06-02 5:42 ` [PATCH/RFC v3 02/22] soc: renesas: Add R-Car RST driver Dirk Behme
2016-06-10 7:58 ` Geert Uytterhoeven
2016-06-10 8:38 ` Dirk Behme
2016-06-10 13:08 ` Laurent Pinchart
2016-06-02 21:58 ` Laurent Pinchart
2016-06-10 7:54 ` Geert Uytterhoeven
[not found] ` <1464808880-343-15-git-send-email-geert+renesas@glider.be>
2016-06-02 22:01 ` [PATCH/RFC v3 14/22] clk: renesas: r8a7795: Obtain mode pin values from " Laurent Pinchart
[not found] ` <1464808880-343-16-git-send-email-geert+renesas@glider.be>
2016-06-02 22:02 ` [PATCH/RFC v3 15/22] clk: renesas: r8a7796: " Laurent Pinchart
[not found] ` <1464808880-343-17-git-send-email-geert+renesas@glider.be>
2016-06-02 22:02 ` [PATCH/RFC v3 16/22] clk: renesas: rcar-gen3-cpg: Remove obsolete rcar_gen3_read_mode_pins() Laurent Pinchart
2016-06-30 20:14 ` [PATCH/RFC v3 00/22] soc: renesas: Add R-Car RST driver for obtaining mode pin state Stephen Boyd
2016-09-01 11:46 ` Geert Uytterhoeven
2016-09-12 22:16 ` Stephen Boyd
2016-09-13 6:48 ` Geert Uytterhoeven
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=CAMuHMdWNZ8tV1Tc6HGL4qqs-hg6G5f1M5AYuB05Mb-JQPrPf4A@mail.gmail.com \
--to=geert@linux-m68k.org \
--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).