linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: jirislaby@kernel.org, amit@kernel.org, arnd@arndb.de,
	osandov@fb.com, shile.zhang@linux.alibaba.com,
	linuxppc-dev@lists.ozlabs.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 0/3] make hvc pass dma capable memory to its backend
Date: Thu, 21 Oct 2021 10:35:39 +0200	[thread overview]
Message-ID: <YXEmW071C+GlmXqw@kroah.com> (raw)
In-Reply-To: <20211015024658.1353987-1-xianting.tian@linux.alibaba.com>

On Fri, Oct 15, 2021 at 10:46:55AM +0800, Xianting Tian wrote:
> Dear all,
> 
> This patch series make hvc framework pass DMA capable memory to
> put_chars() of hvc backend(eg, virtio-console), and revert commit
> c4baad5029 ("virtio-console: avoid DMA from stack”)

Thanks for sticking with this, looks much better now, all now queued up.

greg k-h

  parent reply	other threads:[~2021-10-21  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  2:46 [PATCH v11 0/3] make hvc pass dma capable memory to its backend Xianting Tian
2021-10-15  2:46 ` [PATCH v11 1/3] tty: hvc: use correct dma alignment size Xianting Tian
2021-10-15  2:46 ` [PATCH v11 2/3] tty: hvc: pass DMA capable memory to put_chars() Xianting Tian
2021-10-15 12:59   ` Xianting Tian
2021-10-20  8:47   ` Xianting Tian
2021-10-20  8:56     ` Greg KH
2021-10-26  5:10   ` Jiri Slaby
2021-10-26  6:02     ` Xianting Tian
2021-10-26  6:10       ` Greg KH
2021-10-26  6:11         ` Xianting Tian
2021-10-26  6:49           ` Greg KH
2021-10-15  2:46 ` [PATCH v11 3/3] virtio-console: remove unnecessary kmemdup() Xianting Tian
2021-10-21  8:35 ` Greg KH [this message]
2021-10-21  8:56   ` [PATCH v11 0/3] make hvc pass dma capable memory to its backend Xianting Tian

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=YXEmW071C+GlmXqw@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=amit@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=osandov@fb.com \
    --cc=shile.zhang@linux.alibaba.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xianting.tian@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).