From: Tony Lindgren <tony@atomide.com>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: julia.lawall@lip6.fr, aaro.koskinen@iki.fi,
linux@armlinux.org.uk, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: omap1: add const and initconst to omap_lcd_config
Date: Mon, 2 Oct 2017 12:39:26 -0700 [thread overview]
Message-ID: <20171002193926.GO4394@atomide.com> (raw)
In-Reply-To: <1503383150-2363-1-git-send-email-bhumirks@gmail.com>
* Bhumika Goyal <bhumirks@gmail.com> [170821 23:26]:
> Make these const as they are only passed to a const argument of the function
> omapfb_set_lcd_config.
> Also, replace __initdata with __initconst to avoid section conflict error.
> Done using Coccinelle.
Applying into omap-for-v4.15/omap1 thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap1: add const and initconst to omap_lcd_config
Date: Mon, 2 Oct 2017 12:39:26 -0700 [thread overview]
Message-ID: <20171002193926.GO4394@atomide.com> (raw)
In-Reply-To: <1503383150-2363-1-git-send-email-bhumirks@gmail.com>
* Bhumika Goyal <bhumirks@gmail.com> [170821 23:26]:
> Make these const as they are only passed to a const argument of the function
> omapfb_set_lcd_config.
> Also, replace __initdata with __initconst to avoid section conflict error.
> Done using Coccinelle.
Applying into omap-for-v4.15/omap1 thanks.
Tony
next prev parent reply other threads:[~2017-10-02 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 6:25 [PATCH] ARM: omap1: add const and initconst to omap_lcd_config Bhumika Goyal
2017-08-22 6:25 ` Bhumika Goyal
2017-10-02 19:39 ` Tony Lindgren [this message]
2017-10-02 19:39 ` Tony Lindgren
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=20171002193926.GO4394@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=bhumirks@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.