public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Detlef Vollmann <dv@vollmann.ch>, Benjamin Cama <benoar@dolka.fr>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform
Date: Wed, 02 Dec 2015 20:51:04 +0100	[thread overview]
Message-ID: <4984219.tZoFdLBDNB@wuerfel> (raw)
In-Reply-To: <20151202192825.GF8644@n2100.arm.linux.org.uk>

On Wednesday 02 December 2015 19:28:25 Russell King - ARM Linux wrote:
> 
> As I said above, that's not the problem, the problem is merging it into
> the rest of my tree.
> 
> Having done most of that merge, I'm now tripping up on:
> 
> arch/arm/mach-dove/common.c: In function 'dove_wdt_init':
> arch/arm/mach-dove/common.c:538:2: error: implicit declaration of function 'orion_wdt_init' [-Werror=implicit-function-declaration]
> 
> which I guess is because you've deleted the legacy orion watchdog stuff.
> So I'm going to have to revert that.  That then gives me:
> 
> arch/arm/mach-dove/clock.c:19:21: fatal error: mach/pm.h: No such file or directory
> arch/arm/mach-dove/clock.c:20:27: fatal error: mach/hardware.h: No such file or directory
> 
> The first is easy to solve, and the second by replacing it with dove.h.
> The next problem is this:
> 
> arch/arm/plat-orion/common.c:25:30: fatal error: mach/bridge-regs.h: No such file or directory
> 
> which is impossible to solve, because plat-orion/common.c wants
> mach-dove/bridge-regs.h.

Ok, I can try to work around that, either by duplicating the device definition,
or passing the address into orion_wdt_init.

> I also have arch/arm/mach-dove/include/mach/sdhci.h to pass the GPIO
> for card detection to the SDHCI driver, which is going to break unless
> it's moved to include/linux/platform-data.

Right, a platform_data file seems the right approach there. Possibly just
passing the gpio number by casting it to a pointer, though that's a bit
ugly.

> Everything else seems mostly happy, but I've no way to tell whether
> what would be the resulting kernel would work as it's impossible to
> know without fixing the wreckage above.
> 
> I'm sure I don't have to repeat my position over what I'm going to do if
> these petty mainline changes which are totally unnecessary break the only
> setup I have which works.  Making mach-dove multi-platform is a "wouldn't
> it be nice if", it's not an absolute necessity.

I'm mostly interested in it because it's the only ARMv7 platform that is
left after my other patches, and I just want to be done with it after
spending 5 years on it ;-)

	Arnd

  parent reply	other threads:[~2015-12-02 19:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 15:49 [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Arnd Bergmann
2015-11-25 15:49 ` [PATCH 1/5] ARM: orion: move watchdog setup to mach-orion5x Arnd Bergmann
2015-11-25 15:49 ` [PATCH 2/5] ARM: orion: always use MULTI_IRQ_HANDLER Arnd Bergmann
2015-11-25 15:49 ` [PATCH 3/5] ARM: orion: use SPARSE_IRQ everywhere Arnd Bergmann
2015-11-25 15:49 ` [PATCH 4/5] ARM: orion: clean up mach/*.h headers Arnd Bergmann
2015-11-25 15:49 ` [PATCH 5/5] ARM: orion: multiplatform support Arnd Bergmann
2015-11-25 16:09 ` [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Andrew Lunn
2015-11-25 17:34   ` Gregory CLEMENT
2015-11-25 17:44     ` Andrew Lunn
2015-11-25 19:58       ` Arnd Bergmann
2015-11-26 14:50         ` Jason Cooper
2015-11-25 18:37   ` Russell King - ARM Linux
2015-11-25 19:16     ` Andrew Lunn
2015-11-25 19:29       ` Russell King - ARM Linux
2015-11-25 23:19       ` Russell King - ARM Linux
2015-11-25 20:05     ` Arnd Bergmann
2015-11-25 22:47       ` Russell King - ARM Linux
2015-11-25 20:14 ` Andrew Lunn
2015-11-30 13:37 ` Gregory CLEMENT
2015-12-01 22:51   ` Andrew Lunn
2015-12-01 22:55     ` Arnd Bergmann
2015-12-02 11:03     ` Gregory CLEMENT
2015-12-02 12:33   ` Russell King - ARM Linux
2015-12-02 15:49     ` Arnd Bergmann
2015-12-02 19:28       ` Russell King - ARM Linux
2015-12-02 19:37         ` Russell King - ARM Linux
2015-12-02 19:54           ` Arnd Bergmann
2015-12-02 19:51         ` Arnd Bergmann [this message]
2015-12-02 20:22           ` Russell King - ARM Linux
2015-12-02 20:38             ` Andrew Lunn
2015-12-02 21:03               ` Russell King - ARM Linux
2015-12-02 21:15               ` Arnd Bergmann
2015-12-02 23:59                 ` Andrew Lunn
     [not found]   ` <87wpsz61r7.fsf@free-electrons.com>
     [not found]     ` <20151201182226.ea7d860eb3a35086981cd18f@vollmann.ch>
     [not found]       ` <87fuzl2jm5.fsf@free-electrons.com>
2015-12-02 14:55         ` Andrew Lunn
     [not found]     ` <56697665.1070609@vollmann.ch>
2015-12-10 13:18       ` Arnd Bergmann
2015-12-10 13:43         ` Arnd Bergmann
     [not found]           ` <5669CC76.4030606@vollmann.ch>
2015-12-10 20:59             ` Arnd Bergmann
     [not found]               ` <5669EB31.4050700@vollmann.ch>
2015-12-10 21:29                 ` Arnd Bergmann
     [not found]                   ` <5669F5F8.5010005@vollmann.ch>
2015-12-10 23:10                     ` Arnd Bergmann
2015-12-11 13:36                       ` Jason Cooper
2015-12-11 14:46                         ` Arnd Bergmann
2015-12-11 14:55                           ` Jason Cooper
2015-12-11 18:27                         ` Josh Triplett
2015-12-11 18:46                           ` Jason Cooper
2015-12-11 19:08                             ` Josh Triplett
2015-12-11 19:14                               ` Jason Cooper
     [not found]         ` <5669808F.2050909@vollmann.ch>
2015-12-11 21:33           ` Arnd Bergmann

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=4984219.tZoFdLBDNB@wuerfel \
    --to=arnd@arndb.de \
    --cc=andrew@lunn.ch \
    --cc=benoar@dolka.fr \
    --cc=dv@vollmann.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sebastian.hesselbarth@gmail.com \
    /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