From: Michal Marek <mmarek@suse.cz>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Hemminger <shemminger@vyatta.com>,
Andrew Morton <akpm@linux-foundation.org>,
WANG Cong <amwang@redhat.com>
Subject: Re: [PATCH] headers_check: better search for functions in headers
Date: Tue, 14 Dec 2010 17:07:37 +0100 [thread overview]
Message-ID: <4D079649.6030303@suse.cz> (raw)
In-Reply-To: <1291134119-12903-1-git-send-email-virtuoso@slind.org>
On 30.11.2010 17:21, Alexander Shishkin wrote:
> Some headers don't bother with "extern" in function prototypes,
> which results in said prototypes being unnoticed and exported
> to userland.
>
> This patch slightly improves detection of such cases by checking
> for C type names as well in the beginning of a line.
Applied to kbuild-2.6.git#misc, thanks.
Michal
prev parent reply other threads:[~2010-12-14 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 16:21 [PATCH] headers_check: better search for functions in headers Alexander Shishkin
2010-11-30 16:36 ` Randy Dunlap
2010-11-30 16:42 ` Alexander Shishkin
2010-12-14 16:07 ` Michal Marek [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=4D079649.6030303@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=virtuoso@slind.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