From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: jejb@parisc-linux.org, deller@gmx.de,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc: parport_gsc: constify parisc_device_id
Date: Sat, 14 Oct 2017 22:27:37 +0100 [thread overview]
Message-ID: <20171014212737.GA4712@sudip-laptop> (raw)
In-Reply-To: <208280b55a359db78eecee720799955f2043fb49.1503162439.git.arvind.yadav.cs@gmail.com>
On Sat, Aug 19, 2017 at 10:38:41PM +0530, Arvind Yadav wrote:
> parisc_device_id are not supposed to change at runtime. All functions
> working with parisc_device_id provided by <asm/parisc-device.h> work
> with
> const parisc_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
> ---
> drivers/parport/parport_gsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This has already been done by f0973443bef7 ("parisc/parport_gsc: Fix section mismatches")
--
Regards
Sudip
prev parent reply other threads:[~2017-10-14 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 17:08 [PATCH] parisc: parport_gsc: constify parisc_device_id Arvind Yadav
2017-10-14 21:27 ` Sudip Mukherjee [this message]
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=20171014212737.GA4712@sudip-laptop \
--to=sudipm.mukherjee@gmail.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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