From: Nils Radtke <lkml@Think-Future.com>
To: Dan Carpenter <error27@gmail.com>,
gregkh@suse.de, kernel-janitors@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: p80211netdev.c cleanup
Date: Thu, 18 Nov 2010 10:31:17 +0000 [thread overview]
Message-ID: <20101118103117.GO8821@localhost> (raw)
In-Reply-To: <20101117213246.GJ31724@bicker>
Hi Dan,
Thank you for your reply.
# I don't want to be rude, but it's basically a kernel hacker rule that
# after you introduce a bug (and your last cleanup patch did) that you
# have to fix a bug to make up for it. One excellent source of easy bugs
No offense taken. There are already other mails in
the pipe to actually do that last "multi"-patch properly. Just felt
to finally give feedback at least.
# is using static checkers.
I just used smatch as you proposed. That's where I started to dive into
some code that I had to understand before continuing "fixing" something else.
And I still try to figure out some pieces (had a big break for the locality
change too).. More in the upcoming mails.
# I've found a static checker bug for you.
You've been invaluable already, thank you. I'll try myself one after another.
Maybe first the bug found by smatch (some offset prob), then this one. Hm, we'll see.
Some answer right away, the rest gets pushed on the todo stack.
# 4) Is it a special case where the caller handles it differently?
# Use cscope for this.
# ^] takes you back a step.
Good hint, thx. Hitting esc+alt+] is so "expensive" with this kb layout (you risk
breaking your hand doing that).. ;)
# cscope is an essential kernel hacking tool.
Thank you very much for your detailed explanation. I am already familiar
with cscope, in this case.
# !skb is better as Al Viro explains in this email:
# http://lwn.net/Articles/331593/
Great, thank you!
Cheers,
Nils
--
:x Think-Future.com :)
Yevtushenko has... an ego that can crack crystal at a distance of
twenty feet. -- John Cheever
next prev parent reply other threads:[~2010-11-18 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 18:30 [PATCH] Staging: wlan-ng: p80211netdev.c cleanup Nils Radtke
2010-09-18 20:41 ` Dan Carpenter
2010-11-17 14:55 ` Nils Radtke
2010-11-17 21:32 ` Dan Carpenter
2010-11-18 10:31 ` Nils Radtke [this message]
2010-09-19 12:40 ` walter harms
2010-09-21 0:07 ` Greg KH
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=20101118103117.GO8821@localhost \
--to=lkml@think-future.com \
--cc=devel@driverdev.osuosl.org \
--cc=error27@gmail.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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