public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] clockevents: asm9260: Fix compilation error with sparc/sparc64 allyesconfig
Date: Mon, 23 Feb 2015 12:49:24 -0800	[thread overview]
Message-ID: <20150223204924.GA5669@roeck-us.net> (raw)
In-Reply-To: <54EB91BB.9020800@rempel-privat.de>

On Mon, Feb 23, 2015 at 09:46:51PM +0100, Oleksij Rempel wrote:
> Am 23.02.2015 um 21:34 schrieb Guenter Roeck:
> > On Mon, Feb 23, 2015 at 09:27:01PM +0100, Oleksij Rempel wrote:
> >> Am 23.02.2015 um 20:10 schrieb Guenter Roeck:
> >>> On Mon, Feb 23, 2015 at 08:00:51PM +0100, Daniel Lezcano wrote:
> >>>> The Kconfig options for the asm9260 timer is wrong as it can be selected by
> >>>> another platform with allyes config and thus leading to a compilation failure
> >>>> as some non arch related code is pulled by the compilation.
> >>>>
> >>>> Fix this by having the platform Kconfig to select the timer as it is done for
> >>>> the others drivers.
> >>>>
> >>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> >>>
> >>> Acked-by: Guenter Roeck <linux@roeck-us.net>
> >>>
> >>
> >> the thing is, this SoC or this company has no own IP cores. All of them
> >> are from other companies and providers, including this timer. This is
> >> why all modules for this SoC are selectable.
> >>
> > Maybe the modules should be selected by the architectures using the IP cores ?
> 
> At the moment of pushing patches to arch/arm, maintainers preferred to
> have minimalistic Kconfig.
> 
> > Either case, we'll need _some_ fix upstream, whatever is acceptable for the
> > maintainer.
> 
> What is with initial white list patch?
> 
I don't know. All I know is that the upstream kernel still has the problem,
and that it affects both sparc64-allmodconfig and sparc-allmodconfig.

Guenter

  reply	other threads:[~2015-02-23 20:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 10:18 linux-next: Tree for Feb 9 Stephen Rothwell
2015-02-09 17:20 ` linux-next: Tree for Feb 9 (build failures) Guenter Roeck
2015-02-10  7:07   ` Oleksij Rempel
2015-02-10 12:14     ` Guenter Roeck
2015-02-10 15:57       ` [PATCH] clocksource: whitelist asm9260_timer driver for ARM Oleksij Rempel
2015-02-18  7:17         ` Guenter Roeck
2015-02-18  8:47           ` Daniel Lezcano
2015-02-23 17:48           ` Daniel Lezcano
2015-02-23 17:57             ` Guenter Roeck
2015-02-23 18:57               ` Daniel Lezcano
2015-02-23 19:00               ` [PATCH] clockevents: asm9260: Fix compilation error with sparc/sparc64 allyesconfig Daniel Lezcano
2015-02-23 19:10                 ` Guenter Roeck
2015-02-23 20:27                   ` Oleksij Rempel
2015-02-23 20:34                     ` Guenter Roeck
2015-02-23 20:46                       ` Oleksij Rempel
2015-02-23 20:49                         ` Guenter Roeck [this message]
2015-02-23 21:21                         ` Daniel Lezcano
2015-02-24  5:16                           ` Oleksij Rempel

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=20150223204924.GA5669@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=tglx@linutronix.de \
    /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