From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: davinci: pdata-quirks: fix const warnings
Date: Fri, 09 Jun 2017 10:14:58 -0700 [thread overview]
Message-ID: <m2shj99j71.fsf@baylibre.com> (raw)
In-Reply-To: <5144c8fc-06a8-1d85-0bd3-2640d0903d5c@ti.com> (Sekhar Nori's message of "Thu, 8 Jun 2017 10:55:16 +0530")
Sekhar Nori <nsekhar@ti•com> writes:
> Hi Kevin,
>
> On Saturday 03 June 2017 04:42 AM, Kevin Hilman wrote:
>> After VPIF was converted to enable getting subdevs from DT, the
>> pdata is no longer const, so remove these to avoid compiler warnings.
>>
>> Signed-off-by: Kevin Hilman <khilman@baylibre•com>
>
> I think this should be squashed into patch 2/4 of "davinci:
> vpif_capture: raw camera support" series where the warning is
> introduced. That does mix the platform and driver parts in one patch,
> but I think its better that way so that no patch introduces a warning.
Well, media maintainers have already taken that patch, and probably
won't want to take this as a separate patch now. So, IMO, as long as
this goes in the same merge window, a couple warnings in -next while
things are settling will be OK.
> The patch does not clash with anything queued in davinci tree, so I
> think it should be fine.
>
> Also, there is a warning introduced in
> arch/arm/mach-davinci/board-dm646x-evm.c that should be fixed as well.
I'll fix that and resend the series (this time with DT maintainers in
copy for PATCH 2/2.
Kevin
next prev parent reply other threads:[~2017-06-09 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 23:12 [PATCH 0/2] ARM: davinci: misc. VPIF cleanups Kevin Hilman
2017-06-02 23:12 ` [PATCH 1/2] ARM: davinci: pdata-quirks: fix const warnings Kevin Hilman
2017-06-08 5:25 ` Sekhar Nori
2017-06-09 17:14 ` Kevin Hilman [this message]
2017-06-02 23:12 ` [PATCH 2/2] ARM: dts: da850-evm: drop VPIF endpoints Kevin Hilman
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=m2shj99j71.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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