Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rjw@rjwysocki.net (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Revert explicit support for Renesas R-Car Gen 3 r8a779[56] SoCs
Date: Thu, 10 May 2018 11:51:38 +0200	[thread overview]
Message-ID: <2473510.IAjYrYimeR@aspire.rjw.lan> (raw)
In-Reply-To: <20180502095806.30341-1-horms+renesas@verge.net.au>

On Wednesday, May 2, 2018 11:58:04 AM CEST Simon Horman wrote:
> Revert commits that added explicit support for Renesas R-Car Gen 3
> r8a779[56] SoCs to the generic cpufreq driver.
> 
> This is no longer needed since the flowing commit and to the best of my
> knowledge is not relied on by any upstream DTS: edeec420de24 ("cpufreq:
> dt-platdev: Automatically create cpufreq device with OPP v2")
> 
> Simon Horman (2):
>   Revert "cpufreq: dt: Add r8a7796 support to to use generic cpufreq
>     driver"
>   Revert "cpufreq: rcar: Add support for R8A7795 SoC"
> 
>  drivers/cpufreq/cpufreq-dt-platdev.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> 

Am I expected to pick up this series?

Thanks,
Rafael

  parent reply	other threads:[~2018-05-10  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  9:58 [PATCH 0/2] Revert explicit support for Renesas R-Car Gen 3 r8a779[56] SoCs Simon Horman
2018-05-02  9:58 ` [PATCH 1/2] Revert "cpufreq: dt: Add r8a7796 support to to use generic cpufreq driver" Simon Horman
2018-05-02  9:58 ` [PATCH 2/2] Revert "cpufreq: rcar: Add support for R8A7795 SoC" Simon Horman
2018-05-02 10:03 ` [PATCH 0/2] Revert explicit support for Renesas R-Car Gen 3 r8a779[56] SoCs Viresh Kumar
2018-05-10  9:51 ` Rafael J. Wysocki [this message]
2018-05-15  7:35   ` Simon Horman
2018-05-15  8:00     ` Rafael J. Wysocki

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=2473510.IAjYrYimeR@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --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