From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, backports@vger.kernel.org
Subject: Re: [PATCH] compat: drop const to fix compiler warnings
Date: Fri, 07 Sep 2012 11:12:57 +0200 [thread overview]
Message-ID: <5049BA99.1060707@openwrt.org> (raw)
In-Reply-To: <CAB=NE6V6vAdsVQyjKyaMYnPRQdJLc+Gt=nqiS5cN9mWU3vz7aQ@mail.gmail.com>
On 2012-09-07 11:04 AM, Luis R. Rodriguez wrote:
> On Fri, Sep 7, 2012 at 12:56 AM, Felix Fietkau <nbd@openwrt.org> wrote:
>> When calling pci_find_capability and pci_read_config_word, struct pci_dev
>> needs to be passed without const.
>
> Thanks! I guess because at certain kernel version pci_dev was const ?
Probably, I didn't really check. Either way, this patch should be safe
for all kernel versions.
- Felix
next prev parent reply other threads:[~2012-09-07 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 7:56 [PATCH] compat: drop const to fix compiler warnings Felix Fietkau
2012-09-07 9:04 ` Luis R. Rodriguez
2012-09-07 9:12 ` Felix Fietkau [this message]
2012-09-07 12:59 ` Andy Gospodarek
2012-09-11 23:36 ` Luis R. Rodriguez
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=5049BA99.1060707@openwrt.org \
--to=nbd@openwrt.org \
--cc=backports@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).