From: Anatolij Gustschin <agust@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Gerhard Sittig <gsi@denx.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [v1] powerpc/mpc512x: silence build warning upon disabled DIU
Date: Thu, 10 Oct 2013 21:37:47 +0200 [thread overview]
Message-ID: <20131010213747.4e56ca1f@crub> (raw)
In-Reply-To: <CAN8TOE8o-34zFP=0q3NjondqpA6UA1szitN+kgKcbaNOWhrscg@mail.gmail.com>
Hello,
On Thu, 10 Oct 2013 11:23:55 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
...
> > making mpc512x_setup_diu(), mpc512x_release_bootmem(),
> > mpc512x_valid_monitor_port() and void mpc512x_set_pixel_clock()
> > should be okay.
>
> And mpc512x_init_diu()?
yes, it can be static, too.
>
> >> Then, you can get the real benefit of IS_ENABLED() by removing the
> >>
> >> #if IS_ENABLED(CONFIG_FB_FSL_DIU)
> >>
> >> from around all the DIU code, and it will automatically be removed by
> >> the compiler when it is not used.
> >>
> >> I think the current patch is necessary for immediate use, and it can be
> >> sent to stable. But I might suggest a follow-up patch or 2 that makes
> >> the functions static and kills the #ifdef entirely.
> >
> > Yes, we also have to remove CONFIG_FB_FSL_DIU ifdef in
> > arch/powerpc/sysdev/fsl_soc.h and building should work then.
>
> Still want it around this line, probably, so we'll get compiler errors
> and not linker errors if someone tries to use it?
>
> extern struct platform_diu_data_ops diu_ops;
>
> But otherwise that looks OK to me. Shall I send a patch?
yes, please.
Thanks,
Anatolij
next prev parent reply other threads:[~2013-10-10 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 15:28 [PATCH v1] powerpc/mpc512x: silence build warning upon disabled DIU Gerhard Sittig
2013-10-08 21:42 ` Anatolij Gustschin
2013-10-09 19:29 ` [v1] " Brian Norris
2013-10-10 16:09 ` Anatolij Gustschin
2013-10-10 18:23 ` Brian Norris
2013-10-10 19:37 ` Anatolij Gustschin [this message]
2013-10-11 17:33 ` Brian Norris
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=20131010213747.4e56ca1f@crub \
--to=agust@denx.de \
--cc=computersforpeace@gmail.com \
--cc=gsi@denx.de \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).