From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] Add forward declaration of struct device
Date: Wed, 19 Jan 2011 17:01:21 +0100 [thread overview]
Message-ID: <201101191701.29931.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1101191556190.26685@pobox.suse.cz>
[-- Attachment #1: Type: Text/Plain, Size: 511 bytes --]
Am Mittwoch 19 Januar 2011, 15:56:47 schrieb Jiri Kosina:
> On Mon, 20 Dec 2010, Rolf Eike Beer wrote:
> > This fixes this warning when including linux/dmapool.h first:
> >
> > warning: ‘struct device’ declared inside parameter list
> > warning: its scope is only this definition or declaration, which is
> > probably not what you want
>
> In what situation do you see this warning? (the one you have posted
> doesn't show the filename that is being compiled).
Nothing (yet) in tree.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-01-19 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 16:23 [PATCH] Add forward declaration of struct device Rolf Eike Beer
2011-01-19 14:56 ` Jiri Kosina
2011-01-19 16:01 ` Rolf Eike Beer [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=201101191701.29931.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=dan.j.williams@intel.com \
--cc=jkosina@suse.cz \
--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