From: Jiri Slaby <jirislaby@gmail.com>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Karsten Keil <kkeil@suse.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 4/9] mISDN: fix sparse warnings
Date: Wed, 10 Dec 2008 22:01:10 +0000 [thread overview]
Message-ID: <49403C26.5050402@gmail.com> (raw)
In-Reply-To: <493feab4.0aaa660a.7938.3213@mx.google.com>
On 12/10/2008 04:13 PM, Hannes Eder wrote:
> Should 'plx_lock' be declared in a header file? Or is it really
> neccessart to export it?
As there is no other user, I vote for unexporting it.
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Karsten Keil <kkeil@suse.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 4/9] mISDN: fix sparse warnings
Date: Wed, 10 Dec 2008 23:01:10 +0100 [thread overview]
Message-ID: <49403C26.5050402@gmail.com> (raw)
In-Reply-To: <493feab4.0aaa660a.7938.3213@mx.google.com>
On 12/10/2008 04:13 PM, Hannes Eder wrote:
> Should 'plx_lock' be declared in a header file? Or is it really
> neccessart to export it?
As there is no other user, I vote for unexporting it.
next prev parent reply other threads:[~2008-12-10 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 15:13 [PATCH 4/9] mISDN: fix sparse warnings Hannes Eder
2008-12-10 15:13 ` Hannes Eder
2008-12-10 22:01 ` Jiri Slaby [this message]
2008-12-10 22:01 ` Jiri Slaby
2008-12-10 19:41 ` [PATCHv2 4/9] mISDN: fix sparse warning Hannes Eder
2008-12-10 19:41 ` Hannes Eder
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=49403C26.5050402@gmail.com \
--to=jirislaby@gmail.com \
--cc=hannes@hanneseder.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kkeil@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.