mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>, <alex.smith@imgtec.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, <tony@atomide.com>,
	<scottwood@freescale.com>, <bharat.bhushan@freescale.com>,
	<linux-kernel@vger.kernel.org>, Paul Bolle <pebolle@tiscali.nl>,
	"Andreas Ruprecht" <rupran@einserver.de>,
	hengelein Stefan <stefan.hengelein@fau.de>, <jroedel@suse.de>
Subject: Re: memory: jz4780-nemc: Dependency on undefined Kconfig option
Date: Thu, 2 Apr 2015 10:19:04 +0100	[thread overview]
Message-ID: <551D0988.5020905@imgtec.com> (raw)
In-Reply-To: <CAD3Xx4KvYPx-d2OzJSRAeZAJA+MDwX9Vd9iBx8fCLV60JT_L3A@mail.gmail.com>

Hi Valentin,

MACH_JZ4780 will definitely be added via arch/mips

But the patch series for core jz4780 SOC support still needs a bit of refresh/refining.

For reference, see

http://www.spinics.net/lists/mips/msg55258.html
https://github.com/torvalds/linux/compare/master...paulburton:wip-ci20-v4.0

I have a feeling this will come up with the dma/i2c drivers as well.

Hope that clears the confusion.

Regards,
ZubairLK

On 02/04/15 10:09, Valentin Rothberg wrote:
> Hi Alex,
> 
> your commit ("memory: jz4780-nemc: driver for the NEMC on JZ4780
> SoCs") sets MACH_JZ4780 as Kconfig dependency for the JZ4780_NEMC
> driver.
> 
> +config JZ4780_NEMC
> [...]
> +       depends on MACH_JZ4780
> 
> MACH_JZ4780 is not defined in Kconfig, so that JZ4780_NEMC is always
> false and the driver cannot be compiled.
> 
> Is there a patch queued somewhere that adds the missing Kconfig option?
> 
> I detected this issue with scripts/checkkconfigsymbols.py by diffing
> yesterday's and today's linux-next tree.
> 
> Kind regards,
>  Valentin
> 

  reply	other threads:[~2015-04-02  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  9:09 Valentin Rothberg
2015-04-02  9:19 ` Zubair Lutfullah Kakakhel [this message]
2015-04-02  9:21   ` Valentin Rothberg

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=551D0988.5020905@imgtec.com \
    --to=zubair.kakakhel@imgtec.com \
    --cc=alex.smith@imgtec.com \
    --cc=bharat.bhushan@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rupran@einserver.de \
    --cc=scottwood@freescale.com \
    --cc=stefan.hengelein@fau.de \
    --cc=tony@atomide.com \
    --cc=valentinrothberg@gmail.com \
    /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
all inboxes | Powered by JetHome®