From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Brownell <david-b@pacbell.net>
Cc: Michael Buesch <mb@bu3sch.de>, gregkh <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
Piot Skamruk <piotr.skamruk@gmail.com>,
Pierre Ossman <drzeus-mmc@drzeus.cx>,
openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH v2] Add GPIO-based MMC/SD driver
Date: Mon, 21 Jul 2008 13:53:32 -0700 [thread overview]
Message-ID: <20080721135332.4ce02e0c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200807211341.35766.david-b@pacbell.net>
On Mon, 21 Jul 2008 13:41:35 -0700 David Brownell wrote:
> [ I see "v3" switches to configfs ... same comments apply. ]
> > > Index: linux-next/Documentation/gpiommc.txt
> > > ===================================================================
> > > --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> > > +++ linux-next/Documentation/gpiommc.txt 2008-07-18 21:54:05.000000000 +0200
>
> Should there be a Documentation/mmc/... for such stuff, instead?
What other files could be moved into that subdir?
> The toplevel Documentation directory is getting unmanageable.
Yes, it is.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
next prev parent reply other threads:[~2008-07-21 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 20:01 Michael Buesch
2008-07-18 22:10 ` Randy Dunlap
2008-07-18 22:38 ` Michael Buesch
2008-07-18 22:59 ` Greg KH
2008-07-18 23:19 ` Michael Buesch
2008-07-21 20:41 ` David Brownell
2008-07-21 20:53 ` Randy Dunlap [this message]
2008-07-27 23:30 ` David Brownell
2008-07-27 23:34 ` David Brownell
2008-07-28 13:11 ` Michael Buesch
2008-07-28 20:03 ` Piotr Skamruk
2008-07-21 21:21 ` Michael Buesch
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=20080721135332.4ce02e0c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=drzeus-mmc@drzeus.cx \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=openwrt-devel@lists.openwrt.org \
--cc=piotr.skamruk@gmail.com \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome