From: Ben Hutchings <bhutchings@solarflare.com>
To: Larry Baker <baker@usgs.gov>
Cc: <netdev@vger.kernel.org>
Subject: Re: decnet: /proc/sys/net/decnet sysctl entries disappear
Date: Tue, 12 Feb 2013 18:55:06 +0000 [thread overview]
Message-ID: <1360695306.3050.12.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <A16FE98D-5476-4AB2-855F-0CDA3944E7F5@usgs.gov>
On Tue, 2013-02-12 at 10:28 -0800, Larry Baker wrote:
> David,
>
> On 11 Feb 2013, at 8:53 PM, David Miller wrote:
>
> >
> > Never email developers privately, ever. It is both rude and
> > also a very poor use of global developer resources.
> >
> > Always ask on the appropriate, public, mailing list, so that
> > any developer, not just me, can answer you.
>
> I'm sorry you feel this way. Other developers have been very gracious
> in offering assistance and encouragement to solve this problem. I was
> following the instructions in Documentation/SubmittingPatches you
> guided me to. Specifically, the instructions to locate the assigned
> maintainer and "e-mail that person".
It should also say to mail the related list(s); that's apparently a
documentation error.
> > 5) Select e-mail destination.
> >
> > Look through the MAINTAINERS file and the source code, and determine
> > if your change applies to a specific subsystem of the kernel, with
> > an assigned maintainer. If so, e-mail that person. The script
> > scripts/get_maintainer.pl can be very useful at this step.
> >
> > If no maintainer is listed, or the maintainer does not respond, send
> > your patch to the primary Linux kernel developer's mailing list,
> > linux-kernel@vger.kernel.org. Most kernel developers monitor this
> > e-mail list, and can comment on your changes.
>
> scripts/get_maintainer.pl said that was you.
David Miller is in overall charge of networking, so for any code under
drivers/net/ or net/ that doesn't have its own maintainer, he'll show up
as the primary maintainer. But in reality I doubt he spends much time
thinking about relatively obscure areas that have lost their specialist
maintainer.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-02-12 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 0:26 decnet: /proc/sys/net/decnet sysctl entries disappear Larry Baker
2013-02-12 0:46 ` Ben Hutchings
2013-02-12 1:01 ` Ben Hutchings
2013-02-12 1:30 ` Larry Baker
2013-02-12 1:09 ` David Miller
2013-02-12 18:16 ` Larry Baker
[not found] ` <8EAAA907-914A-4670-BAAF-ABC95C0838CA@usgs.gov>
[not found] ` <20130211.235347.25383457019933412.davem@davemloft.net>
2013-02-12 18:28 ` Larry Baker
2013-02-12 18:43 ` Joe Perches
2013-02-12 18:58 ` Larry Baker
2013-02-12 19:15 ` Joe Perches
2013-02-12 18:55 ` Ben Hutchings [this message]
2013-02-12 22:13 ` PROBLEM: decnet: /proc/sys/net/decnet sysctl entries disappear (2.6.27 through 3.3.x) Larry Baker
[not found] ` <456F0392-03CE-4207-A092-F890D530B746@usgs.gov>
[not found] ` <877gmca8qb.fsf@xmission.com>
2013-02-14 0:50 ` decnet: /proc/sys/net/decnet sysctl entries disappear Larry Baker
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=1360695306.3050.12.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=baker@usgs.gov \
--cc=netdev@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