public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: John Crispin <blogic@openwrt.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: MIPS: ralink: CONFIG_RALINK_ILL_ACC?
Date: Mon, 27 Oct 2014 10:54:41 +0100	[thread overview]
Message-ID: <1414403681.28499.4.camel@x220> (raw)

John,

Your commit 78865eacb4aa ("MIPS: ralink: add illegal access driver")
landed in today's linux-next (ie, next-20141027). That commit dates back
to May 16, 2013! It adds a driver that is built if CONFIG_RALINK_ILL_ACC
is set. But there's no Kconfig symbol RALINK_ILL_ACC.

I assume that patch that adds this symbol is queued somewhere. Is that
correct?


Paul Bolle


             reply	other threads:[~2014-10-27  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:54 Paul Bolle [this message]
     [not found] ` <544E188B.9000707@openwrt.org>
2014-11-10 12:32   ` MIPS: ralink: CONFIG_RALINK_ILL_ACC? Paul Bolle
2015-01-12 12:26     ` Paul Bolle

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=1414403681.28499.4.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=blogic@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --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