From: Sam Ravnborg <sam@ravnborg.org>
To: devzero@web.de
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Should MODULE_DESCRIPTION be mandatory ?
Date: Thu, 16 Apr 2009 13:25:43 +0200 [thread overview]
Message-ID: <20090416112543.GA2672@uranus.ravnborg.org> (raw)
In-Reply-To: <672387486@web.de>
> >
>
> i can offer spending an afternoon (or more) on compiling a list of modulenames + missing description for review.
> if that list is complete and ack`ed, i could create a patch or patch series from that.
> (maybe the list could be split into logical parts, too)
If you do this then you should feed the patches via the maintainers.
I suggest to start out with the network stuff and see if netdev/David Miller
will take them.
Sam
next prev parent reply other threads:[~2009-04-16 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 21:59 Should MODULE_DESCRIPTION be mandatory ? devzero
2009-04-16 11:25 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 11:11 devzero
2009-04-15 19:42 ` Sam Ravnborg
2009-04-15 21:15 ` Randy Dunlap
2009-04-15 21:21 ` Sam Ravnborg
2009-04-15 21:26 ` Randy Dunlap
2009-04-16 12:27 ` Alan Cox
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=20090416112543.GA2672@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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