All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Ribeiro <drwyrm@gmail.com>
To: dedekind@infradead.org
Cc: Nicolas Pitre <nico@cam.org>,
	openezx-devel <openezx-devel@lists.openezx.org>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] cfi_cmdset_0001.c: quirk for PF38F4476.
Date: Tue, 19 May 2009 07:12:08 -0300	[thread overview]
Message-ID: <1242727928.6142.30.camel@brutus> (raw)
In-Reply-To: <1242713035.15206.2.camel@localhost.localdomain>

Em Ter, 2009-05-19 às 09:03 +0300, Artem Bityutskiy escreveu:
> On Sun, 2009-05-17 at 08:02 -0300, Daniel Ribeiro wrote:
> > This chip reports CFI 1.3, but the CFI PRI is like CFI 1.1. Add a quirk
> > to pass probe on this chip.
> > (This patch depends on "cfi_cmdset_0001.c: CFI 1.0 and CFI 1.1")
> > (sent again with CC to Nicolas Pitre)
> > 
> > Signed-off-by: Daniel Ribeiro <drwyrm@gmail.com>
> 
> I've pushed both to l2-mtd-2.6.git. The patches did not cleanly apply,
> probably because they were against an older linux code-base. Please,
> verify:
> 
> http://git.infradead.org/users/dedekind/l2-mtd-2.6.git
> 

Thanks Artem.

Patches were based on 2.6.30-rc4, last commit was "cfi_cmdset_0001.c:
Fix a bug in inval_cache_and_wait_for_operation()." (6ac15e), my guess
is that you had problems applying because you applied the "CFI: quirk
for PF38F4476." first. Next time I will send the patches as a series.

I verified the patches on your gitweb and they look ok.

-- 
Daniel Ribeiro

  reply	other threads:[~2009-05-19 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17 11:02 [PATCH] cfi_cmdset_0001.c: quirk for PF38F4476 Daniel Ribeiro
2009-05-18 23:29 ` Nicolas Pitre
2009-05-19  6:03 ` Artem Bityutskiy
2009-05-19 10:12   ` Daniel Ribeiro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-16 11:41 Daniel Ribeiro
2009-05-17  7:32 ` Artem Bityutskiy

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=1242727928.6142.30.camel@brutus \
    --to=drwyrm@gmail.com \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nico@cam.org \
    --cc=openezx-devel@lists.openezx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.