From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: linux-next: origin tree build warning
Date: Thu, 31 Dec 2009 16:34:37 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912311634110.3630@localhost.localdomain> (raw)
In-Reply-To: <20100101112914.41bc5f77.sfr@canb.auug.org.au>
On Fri, 1 Jan 2010, Stephen Rothwell wrote:
>
> Today's linux-next build (powerpc allnoconfig) produced this warning:
>
> drivers/pci/quirks.c: In function 'pci_dev_specific_reset':
> drivers/pci/quirks.c:2699: warning: assignment discards qualifiers from pointer target type
>
> Introduced by commit 5b889bf237fca383b5807ad69fde3ad1e2287e42 ("PCI: Fix
> build if quirks are not enabled").
Does this trivial patch get rid of it?
Linus
---
drivers/pci/quirks.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 5c449fc..c746943 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -2694,7 +2694,7 @@ static const struct pci_dev_reset_methods pci_dev_reset_methods[] = {
int pci_dev_specific_reset(struct pci_dev *dev, int probe)
{
- struct pci_dev_reset_methods *i;
+ const struct pci_dev_reset_methods *i;
for (i = pci_dev_reset_methods; i->reset; i++) {
if ((i->vendor == dev->vendor ||
next parent reply other threads:[~2010-01-01 0:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100101112914.41bc5f77.sfr@canb.auug.org.au>
2010-01-01 0:34 ` Linus Torvalds [this message]
2010-01-01 1:02 ` linux-next: origin tree build warning Stephen Rothwell
2010-01-01 1:16 ` Rafael J. Wysocki
2010-01-27 0:09 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 4:05 Stephen Rothwell
2010-01-18 4:14 ` Stephen Rothwell
2010-01-18 4:29 ` Wu, Fengguang
2010-01-18 5:40 ` Stephen Rothwell
2010-01-19 0:12 ` Stephen Rothwell
2010-01-19 21:05 ` Greg KH
2010-01-19 21:11 ` Greg KH
2010-01-19 23:47 ` Stephen Rothwell
2009-12-17 0:10 Stephen Rothwell
2009-12-16 3:52 Stephen Rothwell
2009-12-13 23:24 Stephen Rothwell
2009-12-14 7:24 ` Joe Perches
2009-11-29 23:01 Stephen Rothwell
2009-10-30 3:30 Stephen Rothwell
2009-10-11 23:56 Stephen Rothwell
2009-08-25 0:11 Stephen Rothwell
2009-08-25 2:37 ` David Miller
2009-06-23 0:36 Stephen Rothwell
2009-06-22 1:01 Stephen Rothwell
2009-06-22 3:11 ` FUJITA Tomonori
2009-06-19 1:13 Stephen Rothwell
2009-06-19 8:45 ` Kristoffer Ericson
2009-06-19 0:27 Stephen Rothwell
2009-06-19 0:28 ` Stephen Rothwell
2009-06-11 1:27 Stephen Rothwell
2009-04-29 4:49 Stephen Rothwell
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=alpine.LFD.2.00.0912311634110.3630@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
/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