From: Tejun Heo <tj@kernel.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: b.zolnierkie@samsung.com, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/3] constify ata_port_info
Date: Thu, 24 Aug 2017 07:23:46 -0700 [thread overview]
Message-ID: <20170824142346.GN491396@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <1503568201-9991-1-git-send-email-arvind.yadav.cs@gmail.com>
On Thu, Aug 24, 2017 at 03:19:58PM +0530, Arvind Yadav wrote:
> 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.
Applied 1-3 to libata/for-4.14.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-08-24 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 9:49 [PATCH 0/3] constify ata_port_info Arvind Yadav
2017-08-24 9:49 ` [PATCH 1/3] ata: ftide010: " Arvind Yadav
2017-08-24 19:46 ` 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 ` Tejun Heo [this message]
2017-08-24 17:26 ` [PATCH 0/3] " 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=20170824142346.GN491396@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=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 \
/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