From: Ralf Baechle <ralf@linux-mips.org>
To: "Steven J. Hill" <sjhill@mips.com>
Cc: linux-mips@linux-mips.org, Chris Dearman <chris@mips.com>,
John Crispin <blogic@openwrt.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] MIPS: kspd: Remove kspd support.
Date: Wed, 10 Oct 2012 09:38:26 +0200 [thread overview]
Message-ID: <20121010073826.GB6740@linux-mips.org> (raw)
In-Reply-To: <1349821203-23083-1-git-send-email-sjhill@mips.com>
On Tue, Oct 09, 2012 at 05:20:03PM -0500, Steven J. Hill wrote:
> From: "Steven J. Hill" <sjhill@mips.com>
>
> There are no users of the kspd functionality anymore.
Thanks. I've already applied a probably identical patch.
With kspd gone, the question is if there is still any point in keeping
CONFIG_MIPS_VPE_APSP_API and MIPS_VPE_LOADER? I've nuked those also but
I'm holding back for others to get a fair chance to speak up against.
But the fuse is now lit.
Ralf
next prev parent reply other threads:[~2012-10-10 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 22:20 [PATCH] MIPS: kspd: Remove kspd support Steven J. Hill
2012-10-10 7:38 ` Ralf Baechle [this message]
2012-10-10 8:24 ` Hempel Ralph (LQDE RD ST PON SW)
2012-10-10 9:06 ` Suprasad Mutalik Desai
2012-10-10 14:36 ` Hill, Steven
2012-10-11 6:45 ` Suprasad Mutalik Desai
2012-10-11 15:20 ` Hill, Steven
2012-10-15 17:45 ` Ralf Baechle
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=20121010073826.GB6740@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=blogic@openwrt.org \
--cc=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@mips.com \
--cc=viro@zeniv.linux.org.uk \
/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