From: David Woodhouse <dwmw2@infradead•org>
To: Mike Rapoport <mike@compulab•co.il>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org,
Russell King <rmk+kernel@arm•linux.org.uk>
Subject: Re: linux-next: mtd tree build failure
Date: Mon, 20 Oct 2008 09:48:02 +0100 [thread overview]
Message-ID: <1224492482.6770.1531.camel@macbook.infradead.org> (raw)
In-Reply-To: <48FC4277.2000405@compulab.co.il>
On Mon, 2008-10-20 at 10:33 +0200, Mike Rapoport wrote:
> You applied the correct version of the patch. It did depend on ARM at the
> beginning, but after discussion it was decided to make it generic so that other
> architecture would be able to use it. I just haven't thought that readsw/writesw
> might be not available on all architectures.
I've made it depend on ARM again for now. For 2.6.29, let's look at
making use ioread8_rep().
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel•com Intel Corporation
next prev parent reply other threads:[~2008-10-20 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 5:35 linux-next: mtd tree build failure Stephen Rothwell
2008-10-20 7:24 ` David Woodhouse
2008-10-20 8:33 ` Mike Rapoport
2008-10-20 8:48 ` David Woodhouse [this message]
2008-11-16 7:39 ` [PATCH] MTD: NAND: make gpio_nand use io{read,write}{8,16}_rep (was: Re: linux-next: mtd tree build failure) Mike Rapoport
-- strict thread matches above, loose matches on Subject: below --
2009-05-27 3:40 linux-next: mtd tree build failure Stephen Rothwell
2008-08-07 3:30 Stephen Rothwell
2008-08-07 14:19 ` Stephen Rothwell
2008-08-09 20:41 ` Alexey Korolev
2008-08-09 21:33 ` David Woodhouse
2008-08-11 8:30 ` Alexey Korolev
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=1224492482.6770.1531.camel@macbook.infradead.org \
--to=dwmw2@infradead$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mike@compulab$(echo .)co.il \
--cc=rmk+kernel@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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