From: Ralf Baechle <ralf@linux-mips.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
davem@redhat.com, jgarzik@pobox.com, linux-net@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] move dp83840.h to Documentation/
Date: Tue, 1 Feb 2005 00:02:48 +0000 [thread overview]
Message-ID: <20050201000248.GA13862@linux-mips.org> (raw)
In-Reply-To: <20050131234158.GI21437@stusta.de>
On Tue, Feb 01, 2005 at 12:41:58AM +0100, Adrian Bunk wrote:
>
> dp83840.h is included once but none of the definitions it contains is
> actually used.
>
> Ralf Baechle wants that it stays as documentation, so this patch moves
> it under Documentation/ .
Under Documentation is certainly not the right place for a piece of code,
so let's do it as David says.
Ralf
prev parent reply other threads:[~2005-02-01 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 23:41 [2.6 patch] move dp83840.h to Documentation/ Adrian Bunk
2005-01-31 23:46 ` David S. Miller
2005-01-31 23:57 ` Jeff Garzik
2005-02-01 0:29 ` [2.6 patch] remove dp83840.h Adrian Bunk
2005-02-02 5:34 ` Jeff Garzik
2005-02-01 0:02 ` Ralf Baechle [this message]
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=20050201000248.GA13862@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.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