From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Work
Date: Fri, 25 Jul 2014 13:42:12 -0400 [thread overview]
Message-ID: <9933.1406310132@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 24 Jul 2014 22:23:00 -0400." <CAPDOMVi3EGL8YP9-tdbWH8Bn+PbLfYXCq-MP72oQb=8ivagLSw@mail.gmail.com>
On Thu, 24 Jul 2014 22:23:00 -0400, Nick Krause said:
> I having been doing build tests and checkpatch in staging for the last month.
> It doesn't seem like it's worth my time as so my other people are doing it. I
> want an interesting project one that is challenging and rewarding :).
OK. I'm gonna be blunt. That's about as dumb as people who post "What should
my next blog post be about?", and for exactly the same reasons.
If you aren't *internally* motivated by a specific goal/interest, we're
not going to be able to help. Personally, I'm motivated to do testing and
debugging because I have a quarter acre of Linux boxes across the hall that
need stable kernels, and more users over on campus. And every single bug
I catch in linux-next or Fedora Rawhide and file a *good* bug report on
is one less bug that one of my users can trip over and file a poor bug
report about. ;)
Other people are motivated by the fact their employer is paying them
to write a Foobar 2890 driver. Some people find filesystems intellectually
interesting, and others worry far too much about security. And so on.
But if nothing like that is jumping out at you, maybe you should go look
around and see if there's something in userspace that *does* jump out at you.
-------------- 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/20140725/47ef1790/attachment.bin
next prev parent reply other threads:[~2014-07-25 17:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 16:38 Work Nick Krause
2014-07-24 16:43 ` Work Kristofer Hallin
2014-07-24 16:44 ` Work Lucas Tanure
2014-07-24 16:47 ` Work Nick Krause
2014-07-26 21:13 ` Work Yi Li
2014-07-26 21:55 ` Work Lucas Tanure
2014-07-24 16:51 ` Work Andev
2014-07-24 17:10 ` Work Nick Krause
2014-07-25 2:23 ` Work Nick Krause
2014-07-25 5:33 ` Work ravi ranjan Mishra
2014-07-25 11:44 ` Work Lucas Tanure
2014-07-25 12:17 ` Work Robert P. J. Day
2014-07-25 15:19 ` Work Nick Krause
2014-07-25 17:18 ` Work Robert P. J. Day
2014-07-25 17:28 ` Work Valdis.Kletnieks at vt.edu
2014-07-25 17:42 ` Valdis.Kletnieks at vt.edu [this message]
2014-07-25 21:54 ` Work Nick Krause
2014-07-25 22:23 ` Work Arlie Stephens
2014-07-25 23:02 ` Work Nick Krause
2014-07-25 23:35 ` Work Valdis.Kletnieks at vt.edu
2014-07-25 23:44 ` Work Nick Krause
2014-07-26 1:08 ` Work (really slow directory access on ext4) Arlie Stephens
2014-07-26 1:22 ` Nick Krause
2014-07-30 2:34 ` Nick Krause
2014-07-30 17:38 ` Arlie Stephens
2014-07-30 19:48 ` Valdis.Kletnieks at vt.edu
2014-07-30 20:45 ` Nick Krause
2014-07-31 23:36 ` Arlie Stephens
2014-07-31 23:41 ` Henry Hallam
2014-08-01 1:47 ` Nick Krause
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=9933.1406310132@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).