From: David Brownell <david-b@pacbell.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: trimarchimichael@yahoo.it, jwboyer@gmail.com,
linux-mtd@lists.infradead.org, akpm@linux-foundation.org,
rmk@arm.linux.org.uk
Subject: Re: [patch 02/13] jffs2 summary allocation: don't use vmalloc()
Date: Thu, 31 Jul 2008 01:21:22 -0700 [thread overview]
Message-ID: <200807310121.22219.david-b@pacbell.net> (raw)
In-Reply-To: <1217489583.3454.36.camel@pmac.infradead.org>
On Thursday 31 July 2008, David Woodhouse wrote:
> Yes. We're planning to change the API so it looks a lot more like the
> block layer, and a lot less like the one we inherited from PCMCIA in the
> 1990s.
Yeah, there are still a few "old" driver structures lingering. And
I expect the Linux community understands a LOT more about MTD than
it did way back in the day ... :)
> One of the design considerations we've spoken about has been the
> fact that we want to make DMA work properly.
Glad to hear that. But am I right in reading between the lines that
this isn't "soon"? So that the issue addressed by $SUBJECT won't be
able to rely on that as its fix.
- Dave
prev parent reply other threads:[~2008-07-31 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:34 [patch 02/13] jffs2 summary allocation: don't use vmalloc() akpm
2008-07-30 22:39 ` David Brownell
2008-07-30 22:46 ` Andrew Morton
2008-07-31 5:10 ` David Brownell
2008-07-31 5:37 ` Artem Bityutskiy
2008-07-31 6:57 ` David Brownell
2008-07-31 8:03 ` Artem Bityutskiy
2008-07-31 5:15 ` Artem Bityutskiy
2008-07-31 6:56 ` David Brownell
2008-07-31 8:00 ` Artem Bityutskiy
2008-07-31 8:48 ` David Woodhouse
2008-07-31 9:09 ` David Woodhouse
2008-07-31 7:33 ` David Woodhouse
2008-07-31 8:21 ` David Brownell [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=200807310121.22219.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rmk@arm.linux.org.uk \
--cc=trimarchimichael@yahoo.it \
/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