public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] move omap gpmc to drivers finally
Date: Fri, 28 Nov 2014 23:41:40 +0100	[thread overview]
Message-ID: <4073059.QNMRS4hN3Z@wuerfel> (raw)
In-Reply-To: <20141128213915.GV2817@atomide.com>

On Friday 28 November 2014 13:39:16 Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [141128 03:31]:
> > On Wednesday 26 November 2014, Tony Lindgren wrote:
> > >
> > > We can finally move the GPMC code to live in drivers/memory
> > > for further clean up work. This series does the move with
> > > minimal changes to the code.
> > 
> > I just looked at this branch. It's definitely nice to move the code
> > to drivers/memory, but I don't like the idea of having lots of function
> > declarations and internal data structures in a linux/platform_data/*.h
> > file. We can still merge this for 3.19, but I want to make sure you have
> > a plan for getting rid of this (and put that into the tag description).
> > 
> > Does this header file get removed once all non-DT board files are gone?
> 
> Yes that will become driver internal data at that point.

Ok, cool.

> > How about moving the declarations into include/linux/omap-gpmc.h instead?
> 
> OK. Below is an updated pull request with the platform_data/omap-gpmc.h
> dropped.

Pulled into next/omap-gpmc, thanks!

I guess we'll end up merging this branch into next/drivers before submitting,
but I have to see the relative sizes first. If it's a significant chunk of
the drivers changes, we might submit it as one branch to Linus.

	Arnd

      reply	other threads:[~2014-11-28 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:43 [GIT PULL] move omap gpmc to drivers finally Tony Lindgren
2014-11-28 11:28 ` Arnd Bergmann
2014-11-28 21:39   ` Tony Lindgren
2014-11-28 22:41     ` Arnd Bergmann [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=4073059.QNMRS4hN3Z@wuerfel \
    --to=arnd@arndb.de \
    --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