From: David Brownell <david-b@pacbell.net>
To: "Josh Boyer" <jwboyer@gmail.com>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: DataFlash & writesize
Date: Mon, 26 Jun 2006 15:27:25 -0700 [thread overview]
Message-ID: <200606261527.25777.david-b@pacbell.net> (raw)
In-Reply-To: <625fc13d0606261442p605d2291q5ec4b0ad4868e7b3@mail.gmail.com>
On Monday 26 June 2006 2:42 pm, Josh Boyer wrote:
> On 6/26/06, David Brownell <david-b@pacbell.net> wrote:
> > On Friday 23 June 2006 3:43 am, Artem B. Bityutskiy wrote:
> > > On Fri, 2006-06-23 at 12:27 +0200, Andrew Victor wrote:
> > > > Since the writesize change is now in mainline git, here is a trivial
> > > > patch to set mtd->writesize for DataFlash.
> > > > [writesize = erasesize = pagesize]
> > > >
> > >
> > > Andrew,
> > >
> > > I made the same yesterday and it is in GIT, but thank you anyway!
> >
> > What are the intended semantics for "writesize" by the way?
?
> > I noticed I was getting that first BUG_ON in mtdcore:add_mtd_device
> > since, with NOR CFI cmdset 1 flash, with current GIT. Seems like
> > writesie should have been set up already.
>
> Which git tree and when?
Kernel.org GIT tree, pulled yesterday.
> That was a bug that should have been fixed
> last week in the mtd-2.6.git tree. And it should also go to Linus
> ASAP.
>
> josh
>
next prev parent reply other threads:[~2006-06-26 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 7:49 DataFlash & writesize Artem B. Bityutskiy
2006-06-23 10:27 ` Andrew Victor
2006-06-23 10:43 ` Artem B. Bityutskiy
2006-06-26 20:33 ` David Brownell
2006-06-26 21:42 ` Josh Boyer
2006-06-26 22:27 ` David Brownell [this message]
2006-06-26 22:32 ` Thomas Gleixner
2006-06-27 7:02 ` Artem B. Bityutskiy
2006-06-27 7:05 ` Artem B. Bityutskiy
2006-06-27 8:10 ` David Brownell
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=200606261527.25777.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dedekind@yandex.ru \
--cc=jwboyer@gmail.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