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: Re: MIPS: ralink: CONFIG_RALINK_ILL_ACC?
Date: Mon, 12 Jan 2015 13:26:33 +0100 [thread overview]
Message-ID: <1421065593.22660.57.camel@x220> (raw)
In-Reply-To: <1415622769.21229.15.camel@x220>
John,
On Mon, 2014-11-10 at 13:32 +0100, Paul Bolle wrote:
> On Mon, 2014-10-27 at 11:03 +0100, John Crispin wrote:
> > On 27/10/2014 10:54, Paul Bolle wrote:
> > > 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?
> >
> > i'll look into it. the commit that move all dts files to a central
> > folder broke some of my patches so i had to rebase them. apparently
> > the bit that adds the symbol got lost.
>
> (CONFIG_RALINK_ILL_ACC was already gone in next-20141029. So that issue
> is resolved, as far as I care.)
It returned in next-20141114 and then made it into mainline (v3.19-rc1
and later). But there's still no Kconfig symbol RALINK_ILL_ACC. What's
the status of the patch to add it?
Paul Bolle
prev parent reply other threads:[~2015-01-12 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 9:54 MIPS: ralink: CONFIG_RALINK_ILL_ACC? Paul Bolle
2014-10-27 10:03 ` John Crispin
2014-11-10 12:32 ` Paul Bolle
2015-01-12 12:26 ` Paul Bolle [this message]
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=1421065593.22660.57.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.