From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] iommu/arm-smmu-v3: Miscellaneous clean up
Date: Wed, 10 Oct 2018 15:49:48 +0100 [thread overview]
Message-ID: <20181010144948.GA17340@arm.com> (raw)
In-Reply-To: <1539167367-20471-1-git-send-email-andrew.murray@arm.com>
On Wed, Oct 10, 2018 at 11:29:25AM +0100, Andrew Murray wrote:
> Remove unnecessary code and license text.
These two look fine to me.
Joerg -- you can pick them up if you're still queueing patches, otherwise
I'll include them for 4.21.
Cheers,
Will
next prev parent reply other threads:[~2018-10-10 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 10:29 [PATCH 0/2] iommu/arm-smmu-v3: Miscellaneous clean up Andrew Murray
2018-10-10 10:29 ` [PATCH 1/2] iommu/arm-smmu-v3: Add SPDX header Andrew Murray
2018-10-10 10:37 ` Robin Murphy
2018-10-10 10:29 ` [PATCH 2/2] iommu/arm-smmu-v3: Remove unnecessary wrapper function Andrew Murray
2018-10-10 10:42 ` Robin Murphy
2018-10-10 14:49 ` Will Deacon [this message]
2018-10-10 16:10 ` [PATCH 0/2] iommu/arm-smmu-v3: Miscellaneous clean up Joerg Roedel
2018-10-10 16:28 ` Will Deacon
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=20181010144948.GA17340@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@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).