From: Fabian Frederick <fabf@skynet.be>
To: linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, Fabian Frederick <fabf@skynet.be>,
Vince Bridgers <vbridger@opensource.altera.com>,
netdev@vger.kernel.org, nios2-dev@lists.rocketboards.org
Subject: [PATCH 02/16 linux-next] Altera TSE: constify of_device_id array
Date: Tue, 17 Mar 2015 19:37:33 +0100 [thread overview]
Message-ID: <1426617469-781-3-git-send-email-fabf@skynet.be> (raw)
In-Reply-To: <1426617469-781-1-git-send-email-fabf@skynet.be>
of_device_id is always used as const.
(See driver.of_match_table and open firmware functions)
Signed-off-by: Fabian Frederick <fabf@skynet.be>
---
drivers/net/ethernet/altera/altera_tse_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/altera/altera_tse_main.c b/drivers/net/ethernet/altera/altera_tse_main.c
index fd9296a..79ea358 100644
--- a/drivers/net/ethernet/altera/altera_tse_main.c
+++ b/drivers/net/ethernet/altera/altera_tse_main.c
@@ -89,7 +89,7 @@ MODULE_PARM_DESC(dma_tx_num, "Number of descriptors in the TX list");
#define TXQUEUESTOP_THRESHHOLD 2
-static struct of_device_id altera_tse_ids[];
+static const struct of_device_id altera_tse_ids[];
static inline u32 tse_tx_avail(struct altera_tse_private *priv)
{
@@ -1576,7 +1576,7 @@ static const struct altera_dmaops altera_dtype_msgdma = {
.start_rxdma = msgdma_start_rxdma,
};
-static struct of_device_id altera_tse_ids[] = {
+static const struct of_device_id altera_tse_ids[] = {
{ .compatible = "altr,tse-msgdma-1.0", .data = &altera_dtype_msgdma, },
{ .compatible = "altr,tse-1.0", .data = &altera_dtype_sgdma, },
{ .compatible = "ALTR,tse-1.0", .data = &altera_dtype_sgdma, },
--
2.1.0
next prev parent reply other threads:[~2015-03-17 18:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 18:37 [PATCH 00/16 linux-next] drivers/net: constify of_device_id array Fabian Frederick
2015-03-17 18:37 ` [PATCH 01/16 linux-next] net: netcp: " Fabian Frederick
2015-03-17 18:37 ` Fabian Frederick [this message]
2015-03-17 18:37 ` [PATCH 03/16 linux-next] net/fsl: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 04/16 linux-next] net: ethoc: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 05/16 linux-next] drivers: net: xgene: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 06/16 linux-next] net: ethernet: apple: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 07/16 linux-next] netdev: octeon_mgmt: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 08/16 linux-next] net: greth: " Fabian Frederick
2015-03-17 18:37 ` [PATCH 09/16 linux-next] net: xilinx: " Fabian Frederick
2015-03-18 6:50 ` Michal Simek
2015-03-17 18:40 ` [PATCH 10/16 linux-next] orinoco: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 11/16 linux-next] net: phy: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 12/16 linux-next] can: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 13/16 linux-next] IBM-EMAC: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 14/16 linux-next] ehea: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 15/16 linux-next] net: via-rhine: " Fabian Frederick
2015-03-17 18:40 ` [PATCH 16/16 linux-next] via-velocity: " Fabian Frederick
2015-03-17 19:00 ` [PATCH 00/16 linux-next] drivers/net: " David Miller
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=1426617469-781-3-git-send-email-fabf@skynet.be \
--to=fabf@skynet.be \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nios2-dev@lists.rocketboards.org \
--cc=vbridger@opensource.altera.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).