From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: fix locking violation in page fault handler
Date: Thu, 16 May 2019 09:42:01 +0200 [thread overview]
Message-ID: <mvmy336luba.fsf@suse.de> (raw)
In-Reply-To: <mhng-56794b7f-6cd4-4eb9-a962-83ad256ed3cd@palmer-si-x1e> (Palmer Dabbelt's message of "Tue, 07 May 2019 16:48:03 -0700 (PDT)")
On Mai 07 2019, Palmer Dabbelt <palmer@sifive.com> wrote:
> LMK if you, or anyone else, has a preference. I'm assuming this will go in
> through my tree, so I've picked up my version for now :)
You did?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: fix locking violation in page fault handler
Date: Thu, 16 May 2019 09:42:01 +0200 [thread overview]
Message-ID: <mvmy336luba.fsf@suse.de> (raw)
In-Reply-To: <mhng-56794b7f-6cd4-4eb9-a962-83ad256ed3cd@palmer-si-x1e> (Palmer Dabbelt's message of "Tue, 07 May 2019 16:48:03 -0700 (PDT)")
On Mai 07 2019, Palmer Dabbelt <palmer@sifive.com> wrote:
> LMK if you, or anyone else, has a preference. I'm assuming this will go in
> through my tree, so I've picked up my version for now :)
You did?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-05-16 7:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 7:36 [PATCH] riscv: fix locking violation in page fault handler Andreas Schwab
2019-05-07 7:36 ` Andreas Schwab
2019-05-07 8:04 ` Nikolay Borisov
2019-05-07 8:04 ` Nikolay Borisov
2019-05-07 14:12 ` Andreas Schwab
2019-05-07 14:12 ` Andreas Schwab
2019-05-07 14:22 ` Nikolay Borisov
2019-05-07 14:22 ` Nikolay Borisov
2019-05-07 14:36 ` Andreas Schwab
2019-05-07 14:36 ` Andreas Schwab
2019-05-07 23:48 ` Palmer Dabbelt
2019-05-07 23:48 ` Palmer Dabbelt
2019-05-16 7:42 ` Andreas Schwab [this message]
2019-05-16 7:42 ` Andreas Schwab
2019-05-29 16:41 ` Palmer Dabbelt
2019-05-29 16:41 ` Palmer Dabbelt
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=mvmy336luba.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.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.