From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] usb: Fix switch statement in ohci-tmio.c
Date: Thu, 14 Aug 2014 18:12:18 -0400 [thread overview]
Message-ID: <CAPDOMVhp=EpFxH7=_-_S3KHx0gcQTbv1J54bW4dQSQagt92irQ@mail.gmail.com> (raw)
In-Reply-To: <19546.1408052311@turing-police.cc.vt.edu>
On Thu, Aug 14, 2014 at 5:38 PM, <Valdis.Kletnieks@vt.edu> wrote:
> On Thu, 14 Aug 2014 17:13:28 -0400, Nick Krause said:
>> I am learned C. Perhaps I am a little rusty and need to review.
>
> We've seen very little evidence that you *ever* really understood C
> at all, and you're *far* from "a little rusty". It's been some 23
> years since I've hacked any code in IBM's Pascal/VS, and 29 since I
> had to do maintenance work on PL/I code, and I *still* remember more
> of those than you remember of C. (I'll admit that my mad Snobol4 skilz
> have pretty much evaporated, though ;)
>
> http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
I learned C like two years ago and never really practiced it that
much to be honest.
In addition I will come back in the future about I have read The C Programming
Language.
Cheers Nick
next prev parent reply other threads:[~2014-08-14 22:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 18:05 [PATCH] usb: Fix switch statement in ohci-tmio.c Nicholas Krause
2014-08-14 18:06 ` Nick Krause
2014-08-14 18:13 ` Kristofer Hallin
2014-08-14 18:18 ` Nick Krause
2014-08-14 18:36 ` Lucas Tanure
2014-08-14 20:51 ` Valdis.Kletnieks at vt.edu
2014-08-14 21:00 ` Nick Krause
2014-08-14 21:03 ` Mandeep Sandhu
2014-08-14 21:13 ` Nick Krause
2014-08-14 21:38 ` Valdis.Kletnieks at vt.edu
2014-08-14 22:12 ` Nick Krause [this message]
2014-08-14 23:46 ` Nick Krause
2014-08-15 2:16 ` Greg Freemyer
2014-08-15 2:29 ` Nick Krause
2014-08-15 2:42 ` Nick Krause
2014-08-15 3:37 ` Nick Krause
2014-08-15 3:42 ` Jaret Flores
2014-08-15 3:43 ` Nick Krause
2014-08-15 4:21 ` Nick Krause
2014-08-14 19:04 ` Tobias Boege
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='CAPDOMVhp=EpFxH7=_-_S3KHx0gcQTbv1J54bW4dQSQagt92irQ@mail.gmail.com' \
--to=xerofoify@gmail.com \
--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).