[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpUPYpYVaZhCk-bfMe9ZvttQYaSYM_xfKJYX=Z494PWv+A@mail.gmail.com>
Date: Sat, 16 Jun 2012 15:50:36 +0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Fengguang Wu <wfg@...ux.intel.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
Julia Lawall <julia.lawall@...6.fr>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Pekka Enberg <penberg@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Christopher Li <sparse@...isli.org>,
Josh Triplett <josh@...edesktop.org>,
Linus Torvalds <torvalds@...970.osdl.org>
Subject: Re: automated warning notifications
On Fri, Jun 15, 2012 at 10:34 PM, Fengguang Wu <wfg@...ux.intel.com> wrote:
> On Fri, Jun 15, 2012 at 02:19:14PM +0300, Dan Carpenter wrote:
>>
>> Probably we could use something like the attached script to print
>> out the line of code which causes the bug and some other script to
>> querry git blame and attach the offending commit?
>
> cat -n $code_file | tail -n +$(($lineno - (($context + 1) / 2))) | head -n $(($context + 1))
>
> That's handy, I'll use it to show the source file context for the
> first error/warning :-)
Well, you can use sed/awk, it will be much shorter:
cat -n drivers/leds/led-triggers.c | sed -ne '224,230p'
224 struct led_classdev *led_cdev;
225
226 led_cdev = list_entry(entry, struct led_classdev, trig_list);
227 led_set_brightness(led_cdev, brightness);
228 }
229 read_unlock(&trigger->leddev_list_lock);
230 }
(replace the hard-coded "224,230" with a shell variable)
And if you want to find the offending commit:
git show `git blame drivers/leds/led-triggers.c | awk 'NR==227{print $1}'`
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists