From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH next] iommu: intel: don't dereference iommu_device if IOMMU_API is not built
Date: Wed, 14 Oct 2020 14:57:05 +0200 [thread overview]
Message-ID: <20201014125704.GB3635@8bytes.org> (raw)
In-Reply-To: <dc6f3226-c6e5-b361-601b-afa91540144e@linux.intel.com>
On Wed, Oct 14, 2020 at 03:25:08PM +0800, Lu Baolu wrote:
> I suppose Joerg will pick this up. I guess you don't need to resend it
> unless Joerg asks you to do.
Yes, will pick this up soon, no need to re-send.
Thanks,
Joerg
_______________________________________________
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: Bartosz Golaszewski <brgl@bgdev.pl>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH next] iommu: intel: don't dereference iommu_device if IOMMU_API is not built
Date: Wed, 14 Oct 2020 14:57:05 +0200 [thread overview]
Message-ID: <20201014125704.GB3635@8bytes.org> (raw)
In-Reply-To: <dc6f3226-c6e5-b361-601b-afa91540144e@linux.intel.com>
On Wed, Oct 14, 2020 at 03:25:08PM +0800, Lu Baolu wrote:
> I suppose Joerg will pick this up. I guess you don't need to resend it
> unless Joerg asks you to do.
Yes, will pick this up soon, no need to re-send.
Thanks,
Joerg
next prev parent reply other threads:[~2020-10-14 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 7:30 [PATCH next] iommu: intel: don't dereference iommu_device if IOMMU_API is not built Bartosz Golaszewski
2020-10-13 7:30 ` Bartosz Golaszewski
2020-10-13 9:16 ` David Woodhouse
2020-10-13 9:16 ` David Woodhouse
2020-10-14 0:42 ` Lu Baolu
2020-10-14 0:42 ` Lu Baolu
2020-10-14 7:18 ` Bartosz Golaszewski
2020-10-14 7:18 ` Bartosz Golaszewski
2020-10-14 7:25 ` Lu Baolu
2020-10-14 7:25 ` Lu Baolu
2020-10-14 12:57 ` Joerg Roedel [this message]
2020-10-14 12:57 ` Joerg Roedel
2020-10-17 10:27 ` David Woodhouse
2020-10-17 10:27 ` David Woodhouse
2020-10-19 12:07 ` Joerg Roedel
2020-10-19 12:07 ` 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=20201014125704.GB3635@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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.