public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Lee Jones <lee.jones@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] mfd: db8500 stop passing around platform data
Date: Wed, 08 Jun 2016 17:51:58 +0200	[thread overview]
Message-ID: <3648943.90TpD9e9VC@wuerfel> (raw)
In-Reply-To: <CACRpkdZdR1rESjgD-p=79Jk3sp+Xi4ER1vYOsKcr6aAfHztpiw@mail.gmail.com>

On Wednesday, June 8, 2016 1:37:12 PM CEST Linus Walleij wrote:
> On Tue, May 10, 2016 at 4:02 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> 
> > Except for the constant DB8500_PRCMU_FW_VERSION_OFFSET number, nothing
> > is ever passed through the platform data and used in a driver, so we
> > can simply stop passing it around.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> 
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Do you think it's relevant for Lee to take this or do you want to
> have it in ARM SoC together with the other cleanups (that I
> haven't had time to look at...)?
> 
> In the latter case I need an ACK from Lee to apply it for a pull
> request to ARM SoC.
> 
> The functionality it pertains to is out-of-tree but if we want to
> reintroduce it, it should happen through DT anyway.

I think most of the changes are in mfd, so it would be appropriate
for Lee to take them all, but I could also put them into arm-soc
if he prefers.

	Arnd

  reply	other threads:[~2016-06-08 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 14:02 [PATCH 4/4] mfd: db8500 stop passing around platform data Arnd Bergmann
2016-06-08 10:49 ` Lee Jones
2016-06-08 11:37 ` Linus Walleij
2016-06-08 15:51   ` Arnd Bergmann [this message]
2016-06-09 14:50     ` Lee Jones

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=3648943.90TpD9e9VC@wuerfel \
    --to=arnd@arndb.de \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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