From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: "Michael König" <Michael.Koenig@ipcas.de>
Cc: linux-mtd@lists.infradead.org,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: Problems with cfi_cmdset_0002 and Atmel AT49BV642D
Date: Thu, 10 May 2007 12:24:15 +0200 [thread overview]
Message-ID: <1178792655.11554.62.camel@localhost.localdomain> (raw)
In-Reply-To: <EA3F0F32C26AA132D54202A0@franken3>
On Thu, 2007-05-10 at 12:13 +0200, Michael König wrote:
> > So if you have the patch available, now would probably be a good time
> > to post it ;-)
>
> Unfortunately I don't have any experience with GIT and also don't have the
> time to set it up right now, but I'm attaching a "diff -p" for the changes
> to the latest cfi_cmdset_0002.c in the repository.
Ah, very similar to the patch I posted against 2.6.20. The email is held
for approval for some reason, but this patch will do the same. Only
difference is that I put fixup_convert_atmel_pri on the top, since none
of the other fixups should read anything from an Atmel device CFI
information before it has been corrected.
--
With kind regards,
Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway
next prev parent reply other threads:[~2007-05-10 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:44 Problems with cfi_cmdset_0002 and Atmel AT49BV642D Michael König
2007-05-08 11:49 ` Vitaly Wool
2007-05-08 13:04 ` Michael König
2007-05-09 13:34 ` Michael König
2007-05-09 13:46 ` Hans-Christian Egtvedt
2007-05-10 6:53 ` Michael König
2007-05-10 7:15 ` Hans-Christian Egtvedt
2007-05-10 7:41 ` Michael König
2007-05-10 8:27 ` Haavard Skinnemoen
2007-05-10 10:13 ` Michael König
2007-05-10 10:24 ` Hans-Christian Egtvedt [this message]
2007-05-10 10:41 ` Haavard Skinnemoen
2007-08-06 13:41 ` Ricard Wanderlof
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=1178792655.11554.62.camel@localhost.localdomain \
--to=hcegtvedt@atmel.com \
--cc=Michael.Koenig@ipcas.de \
--cc=hskinnemoen@atmel.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