From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question about kref API
Date: Wed, 23 Jul 2014 17:45:16 -0400 [thread overview]
Message-ID: <35480.1406151916@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 23 Jul 2014 17:55:50 -0000." <4E5779AD88B2F040B8A7E83ECF544D1A533A75@SJCPEX01CL02.citrite.net>
On Wed, 23 Jul 2014 17:55:50 -0000, Jeff Haran said:
> > From: 'Greg KH' [mailto:greg at kroah.com]
> > > If you could elaborate on where the race condition is here, I think
> > > you'd being doing both me and the community a great service.
> >
> > Nice try with the "Do it for the community because I don't understand this!"
> > appeal, that doesn't work for me, sorry...
>
> Boy, I try to be as deferential as possible here and you come back with this snarky response.
>
> My experience is when software developers can't or won't explain how their
> code works, it's because they don't understand it themselves.
On the other hand, the kernel community does expect you to do a large chunk of
the learning for yourself - first, because Greg KH isn't a scalable resource,
and second, because if you take the time to figure it out for yourself,
you'll understand it better than if Greg walked you through it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140723/a33f6360/attachment-0001.bin
prev parent reply other threads:[~2014-07-23 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 0:27 question about kref API Jeff Haran
2014-07-22 2:18 ` Greg KH
2014-07-22 17:25 ` Jeff Haran
2014-07-22 23:47 ` Greg KH
2014-07-23 17:33 ` Jeff Haran
2014-07-23 17:38 ` Jeff Haran
2014-07-23 17:48 ` 'Greg KH'
2014-07-23 17:55 ` Jeff Haran
2014-07-23 18:32 ` 'Greg KH'
2014-07-23 21:45 ` Valdis.Kletnieks at vt.edu [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=35480.1406151916@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).