linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.7
Date: Wed, 13 Apr 2016 13:23:28 -0700	[thread overview]
Message-ID: <20160413202328.GS19945@localhost> (raw)
In-Reply-To: <CAMuHMdUbNcbLdQYG037MiDRAe1dr7ohRK625vb16oM8W19WEFw@mail.gmail.com>

On Wed, Apr 13, 2016 at 09:57:39PM +0200, Geert Uytterhoeven wrote:
> Hi Olof,
> 
> On Wed, Apr 13, 2016 at 9:43 PM, Olof Johansson <olof@lixom.net> wrote:
> > On Mon, Apr 04, 2016 at 10:22:56AM +0900, Simon Horman wrote:
> >> Please consider these Renesas ARM based SoC drivers updates for v4.7.
> >>
> >>
> >> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
> >>
> >>   Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
> >>
> >> are available in the git repository at:
> >>
> >>   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-drivers-for-v4.7
> >>
> >> for you to fetch changes up to cd89841fc6dbb6dc11aa113769f39dcd30be720f:
> >>
> >>   ARM: shmobile: timer: Drop support for Cortex A8 (2016-03-28 09:01:31 +0900)
> >>
> >> ----------------------------------------------------------------
> >> Renesas ARM Based SoC Drivers Updates for v4.7
> >>
> >> Loop delay calculation updates:
> >> * Remove check for no longer supported Cortex A8 cores
> >> * Correct short calculation of delay
> >>
> >> ----------------------------------------------------------------
> >> Geert Uytterhoeven (2):
> >>       ARM: shmobile: timer: Fix preset_lpj leading to too short delays
> >>       ARM: shmobile: timer: Drop support for Cortex A8
> >
> > I don't understand your naming. THis isn't driver code, this is SoC code.
> >
> > Anyway, I replied to the drop-A8 patch, the resulting function doesn't make
> > much sense once that code path is removed (div is always 1). Seems like this
> > should be cleaned up in other ways instead.
> >
> > So, not merging this branch for now since I think it should be revisited.
> 
> The reason these are small separate patches is because especially the
> first one may be backported to stable, as it's a real bug fix.

Ok, so then the second shouldn't just remove cortex-a8, but rework the function
(yet again).


-Olof

  reply	other threads:[~2016-04-13 20:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  1:22 [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.7 Simon Horman
2016-04-04  1:22 ` [PATCH 1/2] ARM: shmobile: timer: Fix preset_lpj leading to too short delays Simon Horman
2016-04-04  1:22 ` [PATCH 2/2] ARM: shmobile: timer: Drop support for Cortex A8 Simon Horman
2016-04-13 19:41   ` Olof Johansson
2016-04-13 19:50     ` Geert Uytterhoeven
2016-04-13 19:43 ` [GIT PULL] Renesas ARM Based SoC Drivers Updates for v4.7 Olof Johansson
2016-04-13 19:57   ` Geert Uytterhoeven
2016-04-13 20:23     ` Olof Johansson [this message]
2016-04-14  8:19       ` Geert Uytterhoeven
2016-04-15  0:33         ` Simon Horman
2016-04-15  6:35           ` Geert Uytterhoeven
2016-04-18  3:55             ` Simon Horman
2016-04-19  7:25               ` Geert Uytterhoeven
2016-04-19 22:48                 ` Simon Horman

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=20160413202328.GS19945@localhost \
    --to=olof@lixom.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;
as well as URLs for NNTP newsgroup(s).