From: "Jörn Engel" <joern@logfs.org>
To: Bryan Wu <cooloney@kernel.org>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH 1/1] mtd maps - Blackfin Async Flash Maps (try #4): Handle the case where flash memory and ethernet mac/phy are mapped onto the same async bank
Date: Mon, 19 May 2008 13:18:51 +0200 [thread overview]
Message-ID: <20080519111851.GA32679@logfs.org> (raw)
In-Reply-To: <1211193144-7731-1-git-send-email-cooloney@kernel.org>
On Mon, 19 May 2008 18:32:24 +0800, Bryan Wu wrote:
>
> [try #4]
> - drop superfluous casts
> - drop SSYNC() when reading from the flash and rewrite
> bfin_copy_from() to be like bfin_copy_to() so that
> we dont have to handle all the aligned/unaligned cases
>
> [try #3] rename bf5xx-flash to bfin-async-flash
> - move all kconfig board settings into board resources
> - fixup casting style according to lkml feedback
> - rewrite driver so that it can handle arbitrary of
> instances according to the declared platform resources
>
> [try #2]
> Remove useless SSYNC() as Will said
>
> [try #1]
> The BF533-STAMP does this for example.
> All board-specific configuration goes in your board resources file.
>
> Signed-off-by: Mike Frysinger <vapier.adi@gmail.com>
> Cc: Joern Engel <joern@logfs.org>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
Looks good to me. If dwmw2 doesn't mind adding another mapping driver,
this can go in. Not that I had any idea how physmap could sanely cover
this driver too.
Acked-By: Joern Engel <joern@logfs.org>
Jörn
--
Ninety percent of everything is crap.
-- Sturgeon's Law
prev parent reply other threads:[~2008-05-19 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 10:32 [PATCH 1/1] mtd maps - Blackfin Async Flash Maps (try #4): Handle the case where flash memory and ethernet mac/phy are mapped onto the same async bank Bryan Wu
2008-05-19 11:18 ` Jörn Engel [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=20080519111851.GA32679@logfs.org \
--to=joern@logfs.org \
--cc=cooloney@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@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