From: Artem Bityutskiy <dedekind1@gmail.com>
To: Aaron Sierra <asierra@xes-inc.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: cfi: Allow per-mapping CFI device endianness
Date: Fri, 18 Nov 2011 00:01:27 +0200 [thread overview]
Message-ID: <1321567289.2272.20.camel@koala> (raw)
In-Reply-To: <43e9f17b-665e-489d-a987-495c847c44f1@zimbra>
On Mon, 2011-11-14 at 18:44 -0600, Aaron Sierra wrote:
> This patch allows each CFI device map to use its own endianness. The
> globally defined CFI endianness (CONFIG_MTD_CFI_NOSWAP,
> CONFIG_MTD_CFI_BE_BYTE_SWAP or CONFIG_MTD_CFI_LE_BYTE_SWAP) becomes the
> default value which can be overridden by a driver for a particular device.
>
> Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
Would be nice to get someone's tested-by from the list to make sure it
does not break existing setups. Anyone?
But anyway, looks sane, so I take it to my l2-mtd-2.6.git, thanks!
Artem.
prev parent reply other threads:[~2011-11-17 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32718f73-44ba-4dd0-90a7-8c15cc3ffc54@zimbra>
2011-11-15 0:44 ` [PATCH] mtd: cfi: Allow per-mapping CFI device endianness Aaron Sierra
2011-11-17 22:01 ` Artem Bityutskiy [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=1321567289.2272.20.camel@koala \
--to=dedekind1@gmail.com \
--cc=asierra@xes-inc.com \
--cc=linux-mtd@lists.infradead.org \
/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