From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Dmitri Vorobiev <dmitri.vorobiev@movial.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] A few cleanups for tip-latest
Date: Sun, 22 Mar 2009 19:32:04 +0100 [thread overview]
Message-ID: <49C68424.9080204@s5r6.in-berlin.de> (raw)
In-Reply-To: <1237741871-5827-1-git-send-email-dmitri.vorobiev@movial.com>
Dmitri Vorobiev wrote:
> Hi Ingo,
>
> The following three patches are against the latest tip. Please consider.
You called the patches
Fix a couple of sparse warnings in arch/x86/kernel/apic/io_apic.c
Fix one sparse warning in kernel/extable.c
trace: fix four sparse warnings
Better would have been to tell in the headline what the patches fix in
particular. The fact that the issues were found using the static
checker sparse is of lesser interest and is documented in the changelog
anyway. For example:
x86: io_apic: make a needlessly global symbol static; clean up 0/NULL
initialization
kernel: exceptions: add missing include
kernel: trace: make a needlessly global symbol static; add missing include
--
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/
prev parent reply other threads:[~2009-03-22 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 17:11 Dmitri Vorobiev
2009-03-22 17:11 ` [PATCH 1/3] Fix a couple of sparse warnings in arch/x86/kernel/apic/io_apic.c Dmitri Vorobiev
2009-03-22 17:11 ` [PATCH 2/3] Fix one sparse warning in kernel/extable.c Dmitri Vorobiev
2009-03-22 17:11 ` [PATCH 3/3] trace: fix four sparse warnings Dmitri Vorobiev
2009-03-22 19:39 ` [tip:tracing/ftrace] tracing: " Dmitri Vorobiev
2009-03-25 9:45 ` [tip:tracing/core] tracing, Text Edit Lock: Fix one sparse warning in kernel/extable.c Dmitri Vorobiev
2009-03-22 19:39 ` [tip:x86/cleanups] x86: Fix a couple of sparse warnings in arch/x86/kernel/apic/io_apic.c Dmitri Vorobiev
2009-03-22 17:17 ` [PATCH 0/3] A few cleanups for tip-latest Ingo Molnar
2009-03-22 18:32 ` Stefan Richter [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=49C68424.9080204@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=dmitri.vorobiev@movial.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®