From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: [PATCH 0/2] riscv: add ARCH_HAS_SG_CHAIN to Kconfig
Date: Mon, 12 Nov 2018 17:52:25 -0800 (PST) [thread overview]
Message-ID: <mhng-8aec482b-66bf-4190-8d73-e8c06bcac316@palmer-si-x1c4> (raw)
In-Reply-To: <20181030100107.4590-1-david.abdurachmanov@gmail.com>
On Tue, 30 Oct 2018 03:01:05 PDT (-0700), david.abdurachmanov at gmail.com wrote:
> This should improve virtio-gpu support for riscv.
>
> David Abdurachmanov (2):
> riscv: add ARCH_HAS_SG_CHAIN
> doc: re-run features-refresh.sh
>
> Documentation/features/io/sg-chain/arch-support.txt | 4 ++--
> .../features/locking/queued-spinlocks/arch-support.txt | 2 +-
> Documentation/features/perf/kprobes-event/arch-support.txt | 2 +-
> Documentation/features/vm/pte_special/arch-support.txt | 2 +-
> arch/riscv/Kconfig | 1 +
> 5 files changed, 6 insertions(+), 5 deletions(-)
I'm not opposed to this, but I have no idea what it does or why it's in
arch/*/Kconfig. I've added the first patch to next-sg_chain, but I'm going to
re-do the second one as it looks like it batches up a bunch of updates.
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: david.abdurachmanov@gmail.com
Cc: aou@eecs.berkeley.edu, david.abdurachmanov@gmail.com,
linux-kernel@vger.kernel.org, green.hu@gmail.com,
linux-riscv@lists.infradead.org, deanbo422@gmail.com
Subject: Re: [PATCH 0/2] riscv: add ARCH_HAS_SG_CHAIN to Kconfig
Date: Mon, 12 Nov 2018 17:52:25 -0800 (PST) [thread overview]
Message-ID: <mhng-8aec482b-66bf-4190-8d73-e8c06bcac316@palmer-si-x1c4> (raw)
Message-ID: <20181113015225.NeWrT8cL7sL3vvR6avGc1ldG79sjmlmDv76b06edyO4@z> (raw)
In-Reply-To: <20181030100107.4590-1-david.abdurachmanov@gmail.com>
On Tue, 30 Oct 2018 03:01:05 PDT (-0700), david.abdurachmanov@gmail.com wrote:
> This should improve virtio-gpu support for riscv.
>
> David Abdurachmanov (2):
> riscv: add ARCH_HAS_SG_CHAIN
> doc: re-run features-refresh.sh
>
> Documentation/features/io/sg-chain/arch-support.txt | 4 ++--
> .../features/locking/queued-spinlocks/arch-support.txt | 2 +-
> Documentation/features/perf/kprobes-event/arch-support.txt | 2 +-
> Documentation/features/vm/pte_special/arch-support.txt | 2 +-
> arch/riscv/Kconfig | 1 +
> 5 files changed, 6 insertions(+), 5 deletions(-)
I'm not opposed to this, but I have no idea what it does or why it's in
arch/*/Kconfig. I've added the first patch to next-sg_chain, but I'm going to
re-do the second one as it looks like it batches up a bunch of updates.
Thanks!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-13 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 10:01 [PATCH 0/2] riscv: add ARCH_HAS_SG_CHAIN to Kconfig David Abdurachmanov
2018-10-30 10:01 ` David Abdurachmanov
2018-10-30 10:01 ` [PATCH 1/2] riscv: add ARCH_HAS_SG_CHAIN David Abdurachmanov
2018-10-30 10:01 ` David Abdurachmanov
2018-10-30 10:01 ` [PATCH 2/2] doc: re-run features-refresh.sh David Abdurachmanov
2018-10-30 10:01 ` David Abdurachmanov
2018-11-13 1:52 ` Palmer Dabbelt [this message]
2018-11-13 1:52 ` [PATCH 0/2] riscv: add ARCH_HAS_SG_CHAIN to Kconfig 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=mhng-8aec482b-66bf-4190-8d73-e8c06bcac316@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=linux-riscv@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).