From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: Make the struct pci_dev * argument of pci_fixup_irqs const.
Date: Sat, 11 Jun 2011 16:01:19 -0700 (PDT) [thread overview]
Message-ID: <20110611.160119.176399204911265689.davem@davemloft.net> (raw)
In-Reply-To: <20110610143021.GA26043@linux-mips.org>
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 10 Jun 2011 15:30:21 +0100
> Aside of the usual motivation for constification, this function has a
> history of being abused a hook for interrupt and other fixups so I turned
> this function const ages ago in the MIPS code but it should be done
> treewide.
>
> Due to function pointer passing in varous places a few other functions
> had to be constified as well.
>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2011-06-11 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 14:30 [PATCH] PCI: Make the struct pci_dev * argument of pci_fixup_irqs const Ralf Baechle
2011-06-11 23:01 ` David Miller [this message]
2011-06-13 4:24 ` Paul Mundt
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=20110611.160119.176399204911265689.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).