From: Stefan Roese <sr@denx.de>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: David Brownell <david-b@pacbell.net>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [Question] m25p80 driver versus spi clock rate
Date: Wed, 24 Jun 2009 16:50:25 +0200 [thread overview]
Message-ID: <200906241650.26057.sr@denx.de> (raw)
In-Reply-To: <4A423A0A.2010004@harris.com>
On Wednesday 24 June 2009 16:36:58 Steven A. Falco wrote:
> > I have to admit that I didn't find the time to rework the driver after
> > David's latest review. Frankly, this could take some time since I'm
> > currently busy with other tasks. So it would be great if someone else
> > (Steven?) might pick up here and resubmit this driver so that we can get
> > it finally included.
> >
> > Thanks.
> >
> > Best regards,
> > Stefan
>
> Ok - I'll take that on.
Great, thanks.
> Please, both David and Stefan send me the latest versions
> and/or patches you have, and I'll integrate them and post
> to the PPC list.
I just sent you my latest driver version (v6). Here a link to David's latest
review:
http://article.gmane.org/gmane.linux.ports.ppc64.devel/55229
Best regards,
Stefan
next prev parent reply other threads:[~2009-06-24 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 20:50 [Question] m25p80 driver versus spi clock rate Steven A. Falco
2009-06-22 21:04 ` Mike Frysinger
2009-06-23 18:41 ` Steven A. Falco
2009-06-23 18:46 ` Mike Frysinger
2009-06-23 19:56 ` David Brownell
2009-06-23 20:31 ` Steven A. Falco
2009-06-23 21:08 ` David Brownell
2009-06-23 21:49 ` Steven A. Falco
2009-06-23 22:38 ` David Brownell
2009-06-24 14:25 ` Steven A. Falco
2009-06-24 14:33 ` Stefan Roese
2009-06-24 14:36 ` Steven A. Falco
2009-06-24 14:50 ` Stefan Roese [this message]
2009-06-24 15:13 ` David Brownell
2009-06-24 16:14 ` Steven A. Falco
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=200906241650.26057.sr@denx.de \
--to=sr@denx.de \
--cc=david-b@pacbell.net \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfalco@harris.com \
--cc=vapier.adi@gmail.com \
/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.