From: Alex BASTOS <alebas@televes.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] AMD/Spansion write buffer support in cfi_flash.c
Date: Mon, 29 Aug 2005 14:53:20 +0200 [thread overview]
Message-ID: <1125320000.431305401eea2@webmail.televes.com:443> (raw)
In-Reply-To: <20050829122658.C080935258E@atlas.denx.de>
> > - Adds flash_write_cfibuffer support for AMD/Spansion Flashes.
> > - Additionally, adds 8BIT AMD/Spansion support
>
> Please split this into two separate patches.
OK, I will when corrected
>
> > This is a mix and resend, following the recent rules from
> > U-boot Developers Information, of two similar patches from
> > Thomas Sch?fer and me.
>
> This information read:
>
> (2) Make separate commits for logically separate changes.
Sorry. They were closely related for me.
Best regards,
Alex BASTOS
prev parent reply other threads:[~2005-08-29 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 10:40 [U-Boot-Users] [PATCH] AMD/Spansion write buffer support in cfi_flash.c Alex BASTOS
2005-08-29 12:00 ` Yuli Barcohen
2005-08-29 12:51 ` Alex BASTOS
2005-08-29 13:03 ` Yuli Barcohen
2005-08-30 10:25 ` alebas at televes.com
2006-02-28 16:41 ` Wolfgang Denk
2005-08-29 12:26 ` Wolfgang Denk
2005-08-29 12:53 ` Alex BASTOS [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='1125320000.431305401eea2@webmail.televes.com:443' \
--to=alebas@televes.com \
--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