From: Guenter Roeck <linux@roeck-us.net>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Rabin Vincent <rabin@rab.in>,
jespern@axis.com, linux-cris-kernel@axis.com,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] CRISv32: handle multiple signals
Date: Mon, 9 Feb 2015 08:57:03 -0800 [thread overview]
Message-ID: <20150209165703.GA26547@roeck-us.net> (raw)
In-Reply-To: <20150209095727.GL11399@axis.com>
On Mon, Feb 09, 2015 at 10:57:27AM +0100, Jesper Nilsson wrote:
>
> Niclas Cassel has submitted a reworked driver for crisv32,
> which is in Gregs tree now, unfortunately it wasn't sent to LKML,
> only the linux-serial list, but it should be headed to Linus soon.
>
> http://www.spinics.net/lists/linux-serial/msg15619.html
>
I fetched it from Greg's tree and gave it a test. Works nicely
when combined with the other pending patches for crisv32.
Different question - do you by any chance have a working configuration
for crisv10 in combination with qemu ?
Thanks,
Guenter
next prev parent reply other threads:[~2015-02-09 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 20:45 [PATCH 1/3] CRISv32: don't attempt syscall restart on irq exit Rabin Vincent
2015-02-08 20:45 ` [PATCH 2/3] CRISv32: prevent bogus restarts on sigreturn Rabin Vincent
2015-02-09 9:51 ` Jesper Nilsson
2015-02-08 20:45 ` [PATCH 3/3] CRISv32: handle multiple signals Rabin Vincent
2015-02-09 2:03 ` Guenter Roeck
2015-02-09 9:57 ` Jesper Nilsson
2015-02-09 14:16 ` Guenter Roeck
2015-02-09 16:57 ` Guenter Roeck [this message]
2015-02-10 8:21 ` Jesper Nilsson
[not found] ` <CAJy5ezog4wmV13muOsVopwYhV7QYE6kwqFtJx0rsh+5Z4bf1tg@mail.gmail.com>
2015-02-10 12:26 ` Guenter Roeck
2015-02-09 9:52 ` Jesper Nilsson
2015-02-09 9:49 ` [PATCH 1/3] CRISv32: don't attempt syscall restart on irq exit Jesper Nilsson
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=20150209165703.GA26547@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
--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