linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Kees Cook <keescook@chromium.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Laura Abbott <labbott@redhat.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Allison Randal <allison@lohutok.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <swboyd@chromium.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Semmle Security Reports <security-reports@semmle.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dma-mapping: Add vmap checks to dma_map_single()
Date: Wed, 30 Oct 2019 20:45:32 +0100	[thread overview]
Message-ID: <20191030194532.GA21020@lst.de> (raw)
In-Reply-To: <20191030192640.GC709410@kroah.com>

On Wed, Oct 30, 2019 at 08:26:40PM +0100, Greg Kroah-Hartman wrote:
> Looks good!  You can apply patch 2/2 as well if you want to take that
> through your tree too.

I can do that, I'll just need a formal ACK from you.

  reply	other threads:[~2019-10-30 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 21:34 [PATCH v4 0/2] dma-mapping: Add vmap checks to dma_map_single() Kees Cook
2019-10-29 21:34 ` [PATCH v4 1/2] " Kees Cook
2019-10-30  9:18   ` Greg Kroah-Hartman
2019-10-30 18:09     ` Christoph Hellwig
2019-10-30 18:26       ` Kees Cook
2019-10-30 19:26       ` Greg Kroah-Hartman
2019-10-30 19:45         ` Christoph Hellwig [this message]
2019-10-31  6:51           ` Greg Kroah-Hartman
2019-10-29 21:34 ` [PATCH v4 2/2] usb: core: Remove redundant vmap checks Kees Cook
2019-10-31  6:50   ` Greg Kroah-Hartman
2019-10-31 17:13   ` Christoph Hellwig

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=20191030194532.GA21020@lst.de \
    --to=hch@lst.de \
    --cc=allison@lohutok.net \
    --cc=brouer@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=security-reports@semmle.com \
    --cc=swboyd@chromium.org \
    --cc=tglx@linutronix.de \
    /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).