From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux-foundation.org,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix compile error [-Werror=implicit-function-declaration]
Date: Tue, 2 Feb 2021 14:44:19 +0100 [thread overview]
Message-ID: <20210202134419.GU32671@8bytes.org> (raw)
In-Reply-To: <20210130151907.3929148-1-baolu.lu@linux.intel.com>
On Sat, Jan 30, 2021 at 11:19:07PM +0800, Lu Baolu wrote:
> drivers/iommu/intel/Makefile | 2 +-
> drivers/iommu/intel/iommu.c | 1 -
> include/trace/events/intel_iommu.h | 2 --
> 3 files changed, 1 insertion(+), 4 deletions(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix compile error [-Werror=implicit-function-declaration]
Date: Tue, 2 Feb 2021 14:44:19 +0100 [thread overview]
Message-ID: <20210202134419.GU32671@8bytes.org> (raw)
In-Reply-To: <20210130151907.3929148-1-baolu.lu@linux.intel.com>
On Sat, Jan 30, 2021 at 11:19:07PM +0800, Lu Baolu wrote:
> drivers/iommu/intel/Makefile | 2 +-
> drivers/iommu/intel/iommu.c | 1 -
> include/trace/events/intel_iommu.h | 2 --
> 3 files changed, 1 insertion(+), 4 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2021-02-02 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 15:19 [PATCH 1/1] iommu/vt-d: Fix compile error [-Werror=implicit-function-declaration] Lu Baolu
2021-01-30 15:19 ` Lu Baolu
2021-01-30 17:42 ` Randy Dunlap
2021-01-30 17:42 ` Randy Dunlap
2021-02-02 13:44 ` Joerg Roedel [this message]
2021-02-02 13:44 ` Joerg Roedel
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=20210202134419.GU32671@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@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 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.