From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Andy Shevchenko <andy@infradead.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/2] ACPI / PMIC: constify platform_device_id
Date: Wed, 29 Nov 2017 10:02:57 +0530 [thread overview]
Message-ID: <06603cb3-8645-c1a2-d222-f8b012a71a46@gmail.com> (raw)
In-Reply-To: <CAJZ5v0hnPzt8adPOWik9YYFtdkjqzZSuBgQh4QCm1KzhKJn-vA@mail.gmail.com>
Hi Rafael,
On Wednesday 29 November 2017 02:28 AM, Rafael J. Wysocki wrote:
> On Tue, Nov 28, 2017 at 11:01 AM, Arvind Yadav
> <arvind.yadav.cs@gmail.com> wrote:
>> platform_device_id are not supposed to change at runtime. All functions
>> working with platform_device_id provided by <linux/platform_device.h>
>> work with const platform_device_id. So mark the non-const structs as
>> const.
>>
>> Arvind Yadav (2):
>> [PATCH 1/2] ACPI / PMIC: constify platform_device_id
>> [PATCH 2/2] ACPI / PMIC: Constify platform_device_id
> Can you please resend the two changes in this series as one patch?
Yes, I will resend as single patch.
> Thanks,
> Rafael
Thanks,
~arvind
prev parent reply other threads:[~2017-11-29 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 10:01 Arvind Yadav
2017-11-28 10:01 ` [PATCH 1/2] " Arvind Yadav
2017-11-28 10:20 ` Mika Westerberg
2017-11-28 10:01 ` [PATCH 2/2] ACPI / PMIC: Constify platform_device_id Arvind Yadav
2017-11-28 10:22 ` Mika Westerberg
2017-11-28 20:58 ` [PATCH 0/2] ACPI / PMIC: constify platform_device_id Rafael J. Wysocki
2017-11-29 4:32 ` 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=06603cb3-8645-c1a2-d222-f8b012a71a46@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=andy@infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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®