Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: linux-mips@linux-mips.org
Subject: Re: reference to non-existent CONFIG_HAVE_GPIO_LIB variable?
Date: Mon, 16 May 2011 10:23:33 +0200	[thread overview]
Message-ID: <201105161023.33072.florian@openwrt.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1105141904410.13343@localhost6.localdomain6>

Hello,

On Sunday 15 May 2011 01:05:58 Robert P. J. Day wrote:
>   the current kernel source contains a Makefile reference to the above
> Kconfig variable that does not appear to be defined anywhere.

It would help if you mention which Makefile references this Kconfig variable 
along with the changeset which introduced it.
--
Florian

  reply	other threads:[~2011-05-16  8:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14 23:05 reference to non-existent CONFIG_HAVE_GPIO_LIB variable? Robert P. J. Day
2011-05-16  8:23 ` Florian Fainelli [this message]
2011-05-16  9:36   ` Robert P. J. Day
2011-05-16 11:33     ` Florian Fainelli
2011-05-16 12:14       ` Manuel Lauss
2011-05-16 15:57 ` Ralf Baechle
2011-05-16 19:40   ` Robert P. J. Day

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=201105161023.33072.florian@openwrt.org \
    --to=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=rpjday@crashcourse.ca \
    /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