From: Guenter Roeck <linux@roeck-us.net>
To: Waldemar Brodkorb <mail@waldemar-brodkorb.de>
Cc: Mikael Starvik <mikael.starvik@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jesper Nilsson <jespern@axis.com>,
Mikael Starvik <starvik@axis.com>,
linux-cris-kernel <linux-cris-kernel@axis.com>
Subject: Re: [RFC PATCH 8/8] Revert "percpu: free percpu allocation info for uniprocessor system"
Date: Sun, 21 Sep 2014 13:08:53 -0700 [thread overview]
Message-ID: <541F3055.4060706@roeck-us.net> (raw)
In-Reply-To: <20140921191919.GS14691@waldemar-brodkorb.de>
On 09/21/2014 12:19 PM, Waldemar Brodkorb wrote:
> Hi Guenter,
> Guenter Roeck wrote,
>
>> On 09/21/2014 10:23 AM, Mikael Starvik wrote:
>>> Thanks for all your work with CRIS! CRISv10 is alive but is currently used as small helper CPUs close to hardware blocks.
>>>
>>
>> You are welcome. Now it would be even better if we could get the upstream code to work
>> with qemu. Which leads to the questions - is CRISv32 alive, and is there a chance
>> to get there ? Also, if CRISv10 is alive, is there any interest or even benefit to
>> maintain it in the latest kernel ? Because if not, we might as well drop v10 support
>> to simplify kernel maintenance.
>
> Please do not drop crisv10 support.
> Don't kill my foxboard lx cluster ;)
>
> http://www.openadk.org/cris/cris1.jpg
> http://www.openadk.org/cris/cris2.jpg
>
No problem as long as it's working and someone keeps it maintained.
Guenter
next prev parent reply other threads:[~2014-09-21 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 16:27 [RFC PATCH 0/8] cris: Patches needed on top of v3.17-rc5 Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 1/8] cris: Add support for early console Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 2/8] cris: Add serial driver for Cris v32 Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 3/8] cris: Add dummy free_initrd_mem Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 4/8] cris: time.c: Add missing include file to fix compile error Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 5/8] cris: Add basic qemu_defconfig Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 6/8] tty: crisv32: Coding style cleanup, delete dead code Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 7/8] resource: Add NULL check in next_resource Guenter Roeck
2014-09-21 16:27 ` [RFC PATCH 8/8] Revert "percpu: free percpu allocation info for uniprocessor system" Guenter Roeck
2014-09-21 17:23 ` Mikael Starvik
2014-09-21 18:37 ` Guenter Roeck
2014-09-21 19:19 ` Waldemar Brodkorb
2014-09-21 20:08 ` Guenter Roeck [this message]
2014-09-21 21:12 ` Tejun Heo
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=541F3055.4060706@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@waldemar-brodkorb.de \
--cc=mikael.starvik@axis.com \
--cc=starvik@axis.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®