netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: nick <yocto6@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, mst@redhat.com,
	therbert@google.com, willemb@google.com, fw@strlen.de,
	Paul.Durrant@citrix.com, tgraf@suug.ch, vyasevic@redhat.com,
	herbert@gondor.apana.org.au, JBeulich@suse.com, mszeredi@suse.cz,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: SKB Documentation Ideas and How to Write Docs for Kernel
Date: Sun, 28 Sep 2014 08:29:20 +0200	[thread overview]
Message-ID: <1411885760.5137.58.camel@marge.simpson.net> (raw)
In-Reply-To: <542770B8.3000102@gmail.com>

On Sat, 2014-09-27 at 22:21 -0400, nick wrote: 
> Hello to the maintainers of the file,skb.c ,
> I am wondering about making it easier for new developers including myself by writing a file in the docs on networking
> related to skb_buff and it's various methods of use to developing in the kernel's various networking subsystems. If one of the maintainers would like to help give me feedback on my writing of these docs this would be helpful and make it 
> easier for everyone as from my experience skb_buff is one of the most asked about things in the networking lists and
> would allow people more thing for other work, including the maintainers of lots of the networking code. I understand
> you guys are very busy so feel free to respond whenever you get free time during the next few weeks.

Observation #2, this time public: despite having been told repeatedly
that this is not the way to help, step #1 in your work flow continues to
be to pester people to help YOU.  This repeated pattern of attempts by
you to TAP the community to help YOU really needs to stop.

If you want to work on the linux kernel, get off your butt and get to
work, but whatever you do, STOP trying to engage developers to become
your private tutors.  This list is NOT about developing Nick Krause.

-Mike

      reply	other threads:[~2014-09-28  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  2:21 SKB Documentation Ideas and How to Write Docs for Kernel nick
2014-09-28  6:29 ` Mike Galbraith [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=1411885760.5137.58.camel@marge.simpson.net \
    --to=umgwanakikbuti@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mszeredi@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    --cc=therbert@google.com \
    --cc=vyasevic@redhat.com \
    --cc=willemb@google.com \
    --cc=yocto6@gmail.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;
as well as URLs for NNTP newsgroup(s).