From: Thomas Gleixner <tglx@linutronix.de>
To: David Brownell <david-b@pacbell.net>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>,
Josh Boyer <jwboyer@gmail.com>,
Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: DataFlash & writesize
Date: Tue, 27 Jun 2006 00:32:23 +0200 [thread overview]
Message-ID: <1151361143.25491.451.camel@localhost.localdomain> (raw)
In-Reply-To: <200606261527.25777.david-b@pacbell.net>
On Mon, 2006-06-26 at 15:27 -0700, David Brownell wrote:
> > Which git tree and when?
>
> Kernel.org GIT tree, pulled yesterday.
Does not have the latest fixups. MTD git has. Sorry for the
inconveniance.
tglx
next prev parent reply other threads:[~2006-06-26 22:30 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
2006-06-26 22:32 ` Thomas Gleixner [this message]
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=1151361143.25491.451.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=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