All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: jean-philippe.brucker@arm.com, robin.murphy@arm.com,
	joro@8bytes.org, linux-arm-kernel@lists.infradead.org,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	liubo95@huawei.com, chenjiankang1@huawei.com
Subject: Re: [PATCH v2] iommu/arm-smmu-v3: Avoid ILLEGAL setting of STE.S1STALLD and CD.S
Date: Fri, 20 Oct 2017 09:36:54 +0100	[thread overview]
Message-ID: <20171020083653.GA17938@arm.com> (raw)
In-Reply-To: <7eb1db90-9a30-b70c-c3d1-71bbca41502d@huawei.com>

On Fri, Oct 20, 2017 at 03:00:01PM +0800, Yisheng Xie wrote:
> Any comment about this version?

I have it queued up and plan to send a pull request to Joerg today for 4.15.

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] iommu/arm-smmu-v3: Avoid ILLEGAL setting of STE.S1STALLD and CD.S
Date: Fri, 20 Oct 2017 09:36:54 +0100	[thread overview]
Message-ID: <20171020083653.GA17938@arm.com> (raw)
In-Reply-To: <7eb1db90-9a30-b70c-c3d1-71bbca41502d@huawei.com>

On Fri, Oct 20, 2017 at 03:00:01PM +0800, Yisheng Xie wrote:
> Any comment about this version?

I have it queued up and plan to send a pull request to Joerg today for 4.15.

Will

  reply	other threads:[~2017-10-20  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 12:36 [PATCH v2] iommu/arm-smmu-v3: Avoid ILLEGAL setting of STE.S1STALLD and CD.S Yisheng Xie
2017-09-21 12:36 ` Yisheng Xie
2017-09-21 12:36 ` Yisheng Xie
2017-10-20  7:00 ` Yisheng Xie
2017-10-20  7:00   ` Yisheng Xie
2017-10-20  7:00   ` Yisheng Xie
2017-10-20  8:36   ` Will Deacon [this message]
2017-10-20  8:36     ` Will Deacon
2017-10-20  9:14     ` Yisheng Xie
2017-10-20  9:14       ` Yisheng Xie
2017-10-20  9:14       ` Yisheng Xie

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=20171020083653.GA17938@arm.com \
    --to=will.deacon@arm.com \
    --cc=chenjiankang1@huawei.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo95@huawei.com \
    --cc=robin.murphy@arm.com \
    --cc=xieyisheng1@huawei.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.