From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: tj@kernel.org, b.zolnierkie@samsung.com, linus.walleij@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: [PATCH 1/3] ata: ftide010: constify ata_port_info
Date: Thu, 24 Aug 2017 15:19:59 +0530 [thread overview]
Message-ID: <1503568201-9991-2-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1503568201-9991-1-git-send-email-arvind.yadav.cs@gmail.com>
ata_port_info are not supposed to change at runtime. All functions
working with ata_port_info provided by <linux/libata.h> work with
const ata_port_info. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/ata/pata_ftide010.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ata/pata_ftide010.c b/drivers/ata/pata_ftide010.c
index 5d4b72e..6c04495 100644
--- a/drivers/ata/pata_ftide010.c
+++ b/drivers/ata/pata_ftide010.c
@@ -256,7 +256,7 @@ static unsigned int ftide010_qc_issue(struct ata_queued_cmd *qc)
.qc_issue = ftide010_qc_issue,
};
-static struct ata_port_info ftide010_port_info[] = {
+static const struct ata_port_info ftide010_port_info[] = {
{
.flags = ATA_FLAG_SLAVE_POSS,
.mwdma_mask = ATA_MWDMA2,
--
1.9.1
next prev parent reply other threads:[~2017-08-24 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 9:49 [PATCH 0/3] " Arvind Yadav
2017-08-24 9:49 ` Arvind Yadav [this message]
2017-08-24 19:46 ` [PATCH 1/3] ata: ftide010: " Linus Walleij
2017-08-24 9:50 ` [PATCH 2/3] ata: pdc2027x: " Arvind Yadav
2017-08-24 9:50 ` [PATCH 3/3] ata: " Arvind Yadav
2017-08-24 14:23 ` [PATCH 0/3] " Tejun Heo
2017-08-24 17:26 ` Tejun Heo
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=1503568201-9991-2-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®