From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] sf: Macronix additional chips supported
Date: Mon, 6 Jul 2009 04:28:28 -0400 [thread overview]
Message-ID: <200907060428.30655.vapier@gentoo.org> (raw)
In-Reply-To: <1246882876-17543-1-git-send-email-prafulla@marvell.com>
On Monday 06 July 2009 08:21:16 Prafulla Wadaskar wrote:
> new chips supported:-
> MX25L1605D, MX25L3205D, MX25L6405D, MX25L12855E
> out of which MX25L6405D and MX25L12855E tested on Kirkwood platforms
>
> Modified the Macronix flash support to use 2 bytes of device id instead of
> 1 This was required to support MX25L12855E
>
> Done some indentation fixes
>
> Signed-off-by: Piyush Shah <spiyush@marvell.com>
> Signed-off-by: Prafulla Wadaskar <prafulla@marvell.com>
> ---
> Change log:-
> v2: leading spaces removed for clean patch apply
> build error fixed
> tested for new added chip MX25L6405D
>
> v3: updated contributors info
> ids combined to u16
> ids list of defines removed, used values in the struct
>
> v4: indentation fixes,
> line lengths brought below 78 chars
> alligned access fixed for idcode
blah, this just got much worse. code style cleanups should be kept separate.
i.e. the v3 patch without whitespace damage should be one commit and then if
you still want to do style changes, that needs to be on top of that.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090706/5d59b0f0/attachment.pgp
next prev parent reply other threads:[~2009-07-06 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 12:21 [U-Boot] [PATCH v4] sf: Macronix additional chips supported Prafulla Wadaskar
2009-07-06 7:34 ` Prafulla Wadaskar
2009-07-06 8:28 ` Mike Frysinger [this message]
2009-07-06 9:37 ` Prafulla Wadaskar
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=200907060428.30655.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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