From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Frank Pavlic <fpavlic@de.ibm.com>
Subject: Re: [patch 4/4] lock validator: fix qeth compile warning
Date: Fri, 23 Jun 2006 15:40:34 +0200 [thread overview]
Message-ID: <20060623134034.GD15113@elte.hu> (raw)
In-Reply-To: <20060623132811.GH9446@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> +#ifdef CONFIG_LOCKDEP
> static struct lockdep_type_key qdio_out_skb_queue_key;
> +#endif
ok, that's fine for now. I'm cleaning this up via introducing
per-lock-variant keys. But maybe the best would be to offer the lock
validator in a binary way only - either for all lock variants at once,
or for none at all?
Ingo
prev parent reply other threads:[~2006-06-23 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 13:28 [patch 4/4] lock validator: fix qeth compile warning Heiko Carstens
2006-06-23 13:40 ` Ingo Molnar [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=20060623134034.GD15113@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=fpavlic@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--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