mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: a.zummo@towertech.it, linux-kernel@vger.kernel.org,
	linux-rtc@vger.kernel.org
Subject: Re: [PATCH 0/4] constify rtc i2c_device_id
Date: Thu, 24 Aug 2017 11:01:55 +0200	[thread overview]
Message-ID: <20170824090155.vka35qu6jv3aw63h@piout.net> (raw)
In-Reply-To: <1503169678-18078-1-git-send-email-arvind.yadav.cs@gmail.com>

On 20/08/2017 at 00:37:54 +0530, Arvind Yadav wrote:
> i2c_device_id are not supposed to change at runtime. All functions
> working with i2c_device_id provided by <linux/i2c.h> work with
> const i2c_device_id. So mark the non-const structs as const.
> 
> Arvind Yadav (4):
>   [PATCH 1/4] rtc: ds1672: constify i2c_device_id
>   [PATCH 2/4] rtc: em3027: constify i2c_device_id
>   [PATCH 3/4] rtc: max6900: constify i2c_device_id
>   [PATCH 4/4] rtc: rv3029c2: constify i2c_device_id
> 
>  drivers/rtc/rtc-ds1672.c   | 2 +-
>  drivers/rtc/rtc-em3027.c   | 2 +-
>  drivers/rtc/rtc-max6900.c  | 2 +-
>  drivers/rtc/rtc-rv3029c2.c | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 

All applied.

> -- 
> 2.7.4
> 

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2017-08-24  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 19:07 Arvind Yadav
2017-08-19 19:07 ` [PATCH 1/4] rtc: ds1672: constify i2c_device_id Arvind Yadav
2017-08-19 19:07 ` [PATCH 2/4] rtc: em3027: " Arvind Yadav
2017-08-19 19:07 ` [PATCH 3/4] rtc: max6900: " Arvind Yadav
2017-08-19 19:07 ` [PATCH 4/4] rtc: rv3029c2: " Arvind Yadav
2017-08-24  9:01 ` Alexandre Belloni [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=20170824090155.vka35qu6jv3aw63h@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=a.zummo@towertech.it \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@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

all inboxes | Powered by JetHome®