From: David Woodhouse <dwmw2@infradead.org>
To: "Cagle, John" <john.cagle@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mtd@lists.infradead.org,
Christian Borntraeger <linux-kernel@borntraeger.net>,
Torben Mathiasen <device@lanana.org>,
linux-kernel@vger.kernel.org
Subject: RE: [Patch][RFC] conflicting device major numbers in devices.txt
Date: Sun, 19 Sep 2004 08:50:54 +0100 [thread overview]
Message-ID: <1095580254.5065.172.camel@localhost.localdomain> (raw)
In-Reply-To: <C50AB9511EE59B49B2A503CB7AE1ABD108F82153@cceexc19.americas.cpqcorp.net>
On Sat, 2004-09-18 at 18:14 -0500, Cagle, John wrote:
> Torben -- please correct this in devices.txt and find a new block
> major for the Linux-MTD project (if they will accept it).
Seems reasonable.
--
dwmw2
next prev parent reply other threads:[~2004-09-19 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 23:14 [Patch][RFC] conflicting device major numbers in devices.txt Cagle, John
2004-09-19 7:50 ` David Woodhouse [this message]
[not found] ` <20040921092356.GD4055@linux>
2004-09-21 15:03 ` Arnd Bergmann
[not found] ` <20040921164938.GQ4055@linux>
2004-09-21 17:03 ` Arnd Bergmann
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=1095580254.5065.172.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=device@lanana.org \
--cc=john.cagle@hp.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--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