From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: linux-next: build warnings after merge of the driver-core.current tree
Date: Sun, 2 May 2010 19:59:28 -0700 [thread overview]
Message-ID: <20100503025928.GA28102@kroah.com> (raw)
In-Reply-To: <20100503100137.a05c9098.sfr@canb.auug.org.au>
On Mon, May 03, 2010 at 10:01:37AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the driver-core.current tree, today's linux-next build (powerpc
> ppc64_defconfig and x86_64 allmodconfig) produced these warning:
>
> drivers/pcmcia/ds.c: In function 'pcmcia_load_firmware':
> drivers/pcmcia/ds.c:761: warning: passing argument 1 of 'release_firmware' discards qualifiers from pointer target type
> include/linux/firmware.h:46: note: expected 'struct firmware *' but argument is of type 'const struct firmware *'
> drivers/net/cxgb3/cxgb3_main.c: In function 't3_get_edc_fw':
> drivers/net/cxgb3/cxgb3_main.c:1084: warning: passing argument 1 of 'release_firmware' discards qualifiers from pointer target type
> include/linux/firmware.h:46: note: expected 'struct firmware *' but argument is of type 'const struct firmware *'
>
> and *lots* more similar warnings ...
>
> Caused by commit d5ae47f7d90f94a15e668f389c12211a11798b6f
> ("firmware_class: fix memory leak - free allocated pages"). This patch
> was modified from an earlier version that produced different (though many
> fewer) warnings.
Yeah, the people responsible were been notified last Friday, and they
sent me a patch today, hopefully it fixes the issue. I'll test it out
tomorrow and merge it if it does.
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-03 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 0:01 linux-next: build warnings after merge of the driver-core.current tree Stephen Rothwell
2010-05-03 2:59 ` Greg KH [this message]
2010-05-03 11:19 ` Winkler, Tomas
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=20100503025928.GA28102@kroah.com \
--to=greg@kroah.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tomas.winkler@intel.com \
/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.