linux-kernel - const struct pci_driver [Was: [RFC 2/2] Input: phantom, add a new driver]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Apr 2007 10:28:46 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>
Subject: const struct pci_driver [Was: [RFC 2/2] Input: phantom, add a new
 driver]

Andrew Morton napsal(a):
> On Tue, 17 Apr 2007 22:02:10 +0200 (CEST) Jiri Slaby <jirislaby@...il.com> wrote:
> 
>> phantom, add a new driver
[...]
>> +static struct pci_driver phantom_pci_driver = {
>> +	.name = "phantom",
>> +	.id_table = phantom_pci_tbl,
>> +	.probe = phantom_probe,
>> +	.remove = __devexit_p(phantom_remove),
>> +	.suspend = phantom_suspend,
>> +	.resume = phantom_resume
>> +};
> 
> This goes into the read/write section.  Make it const?

Hmm, good question, I don't know the answer. Why are not pci_driver structs
const, Greg?

thanks,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/