From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: julia.lawall@lip6.fr, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH] video: fbdev: make fb_var_screeninfo static, const and __initconst
Date: Thu, 12 Oct 2017 16:06:46 +0000 [thread overview]
Message-ID: <4996127.oJ8tDUhiv1@amdc3058> (raw)
In-Reply-To: <1505392334-8001-1-git-send-email-bhumirks@gmail.com>
[ added dri-devel & sparclinux MLs to cc: ]
On Thursday, September 14, 2017 06:02:14 PM Bhumika Goyal wrote:
> Make these structures static as they are not referenced in any other
> file. Make them const as they are used only during a copy operation.
> Replace __initdata with __initconst in file igafb.c to avoid section
> conflict error.
>
> Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
> ---
> The changes are not compile tested as I could not find the right
> architecture to cross compile the files.
>
> drivers/video/fbdev/dnfb.c | 2 +-
> drivers/video/fbdev/igafb.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
You can deduce such things by looking into Makefile-s and KConfig-s:
- dnfb is used by apollo platform of m68k arch
- igafb can be used on sparc32 arch
I took care of compile testing these changes and discovered that
in the current vanilla kernel (v4.14-rc4) igafb fails to build.
Thus I've only queued dnfb changes for v4.15 kernel for now.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2017-10-12 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170830114048epcas1p48ae21ff4b434a6cda51f6637ad555db8@epcas1p4.samsung.com>
2017-08-30 11:52 ` [PATCH] video: fbdev: make fb_var_screeninfo const Bhumika Goyal
2017-09-04 13:48 ` Bartlomiej Zolnierkiewicz
2017-09-14 12:44 ` [PATCH] video: fbdev: make fb_var_screeninfo static, const and __initconst Bhumika Goyal
2017-10-12 16:06 ` Bartlomiej Zolnierkiewicz [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=4996127.oJ8tDUhiv1@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=bhumirks@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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