dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: airlied@linux.ie, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] constify drm i2c_device_id
Date: Tue, 22 Aug 2017 15:13:14 +0530	[thread overview]
Message-ID: <d0a27e63-d11e-29b8-40ce-bfb45c7c4fd7@gmail.com> (raw)
In-Reply-To: <20170822062900.vaclssbmt3tiemfl@phenom.ffwll.local>

Hi Daniel,


On Tuesday 22 August 2017 12:01 PM, Daniel Vetter wrote:
> On Sat, Aug 19, 2017 at 11:58:17PM +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.
> All applied.
>
> btw I think this isn't your first series, and we're trying to keep some of
> the trivial mistakes around in drm, as an easy way for newbies to get into
> the subsystem with their first patch.
>
> We'd like more regular contributors to tackle some of the more involved
> cleanup tasks, which should also be more valuable to the subsystem:
>
> file:///home/daniel/linux/src/Documentation/output/gpu/todo.html#todo
I want to contribute drm and others subsystem. If you can guide me.
It will helpful for me.
> Cheers, Daniel
>
>> Arvind Yadav (3):
>>    [PATCH 1/3] drm: i2c: ch7006: constify i2c_device_id
>>    [PATCH 2/3] drm: i2c: sil164: constify i2c_device_id
>>    [PATCH 3/3] drm: i2c: tda998x: constify i2c_device_id
>>
>>   drivers/gpu/drm/i2c/ch7006_drv.c  | 2 +-
>>   drivers/gpu/drm/i2c/sil164_drv.c  | 2 +-
>>   drivers/gpu/drm/i2c/tda998x_drv.c | 2 +-
>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> -- 
>> 2.7.4
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
~arvind

      reply	other threads:[~2017-08-22  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 18:28 [PATCH 0/3] constify drm i2c_device_id Arvind Yadav
2017-08-19 18:28 ` [PATCH 1/3] drm: i2c: ch7006: constify i2c_device_id Arvind Yadav
2017-08-19 18:28 ` [PATCH 2/3] drm: i2c: sil164: " Arvind Yadav
2017-08-19 18:28 ` [PATCH 3/3] drm: i2c: tda998x: " Arvind Yadav
2017-08-22  6:31 ` [PATCH 0/3] constify drm i2c_device_id Daniel Vetter
2017-08-22  9:43   ` Arvind Yadav [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=d0a27e63-d11e-29b8-40ce-bfb45c7c4fd7@gmail.com \
    --to=arvind.yadav.cs@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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