From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/14/] Doc. sources: expose watchdog
Date: Tue, 20 Jun 2006 12:13:42 -0700 [thread overview]
Message-ID: <20060620121342.61976088.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060620184847.GA4607@infomag.infomag.iguana.be>
On Tue, 20 Jun 2006 20:48:47 +0200 Wim Van Sebroeck wrote:
> Randy, Andrew,
>
> > > > > Documentation/watchdog/pcwd-watchdog.txt | 73 -------------------------------
> > > > > Documentation/watchdog/watchdog-api.txt | 17 -------
> > > > > Documentation/watchdog/watchdog-simple.c | 15 ++++++
> > > > > Documentation/watchdog/watchdog-test.c | 68 ++++++++++++++++++++++++++++
> > > > > Documentation/watchdog/watchdog.txt | 23 ---------
> > > >
> > > > Wouldn't it be better to move all the .c files into a new directory?
> > > > Documentation/src or something?
> > >
> > > I dunno. I like using multiple subdirectories (like watchdog/,
> > > laptop/, block/, etc.) and not cluttering up Documentation/
> > > with them.
> >
> > I think a "user" that wants to know something specific about watchdog drivers
> > will look in Documentation/watchdog and try to find what he need as fast as
> > he can. I would say Documentation/watchdog/src/ then...
>
> I'm going to change this patch so that we put the .c files in
> Documentation/watchdog/src/ . I presume this is ok for both of you?
Sure, OK for me. Thanks.
---
~Randy
prev parent reply other threads:[~2006-06-20 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 3:58 Randy.Dunlap
2006-05-22 20:05 ` Wim Van Sebroeck
2006-05-22 21:43 ` Andrew Morton
2006-05-22 21:58 ` Randy.Dunlap
2006-05-23 20:37 ` Wim Van Sebroeck
2006-06-20 18:48 ` Wim Van Sebroeck
2006-06-20 19:13 ` Randy.Dunlap [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=20060620121342.61976088.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®