From: Mike Rapoport <mike@compulab.co.il>
To: David Woodhouse <dwmw2@infradead.org>
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 10:33:59 +0200 [thread overview]
Message-ID: <48FC4277.2000405@compulab.co.il> (raw)
In-Reply-To: <1224487490.6770.1509.camel@macbook.infradead.org>
David Woodhouse wrote:
> On Mon, 2008-10-20 at 16:35 +1100, Stephen Rothwell wrote:
>> Caused by commit aaf7ea20000436df3cbb397ccb734ad1e2e5164d ("[MTD]
>> [NAND] GPIO NAND flash driver"). I assume this needs to depend on
>> some architecture/platform so I reverted it for now.
>
> Hm, indeed. I thought it _did_ depend on ARM -- did I apply the wrong
> version of the patch?
>
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.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2008-10-20 10:13 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 [this message]
2008-10-20 8:48 ` David Woodhouse
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=48FC4277.2000405@compulab.co.il \
--to=mike@compulab.co.il \
--cc=dwmw2@infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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).