From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Safonov <dima@arista.com>
Cc: stable@vger.kernel.org, 0x7f454c46@gmail.com,
Joerg Roedel <jroedel@suse.de>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH-4.19-stable 2/2] iommu/iova: Fix compilation error with !CONFIG_IOMMU_IOVA
Date: Wed, 31 Jul 2019 19:04:11 +0200 [thread overview]
Message-ID: <20190731170411.GA22660@kroah.com> (raw)
In-Reply-To: <20190731162220.24364-3-dima@arista.com>
On Wed, Jul 31, 2019 at 05:22:20PM +0100, Dmitry Safonov wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> [ Upstream commit 201c1db90cd643282185a00770f12f95da330eca ]
>
> The stub function for !CONFIG_IOMMU_IOVA needs to be
> 'static inline'.
>
> Fixes: effa467870c76 ('iommu/vt-d: Don't queue_iova() if there is no flush queue')
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Dmitry Safonov <dima@arista.com>
> [v4.14 backport]
4.19? :)
next prev parent reply other threads:[~2019-07-31 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:22 [PATCH-4.19-stable 0/2] iommu/vt-d: queue_iova() boot crash backport Dmitry Safonov
2019-07-31 16:22 ` Dmitry Safonov via iommu
2019-07-31 16:22 ` [PATCH-4.19-stable 1/2] iommu/vt-d: Don't queue_iova() if there is no flush queue Dmitry Safonov
2019-07-31 16:22 ` Dmitry Safonov via iommu
2019-07-31 16:22 ` [PATCH-4.19-stable 2/2] iommu/iova: Fix compilation error with !CONFIG_IOMMU_IOVA Dmitry Safonov
2019-07-31 17:04 ` Greg Kroah-Hartman [this message]
2019-07-31 17:06 ` Dmitry Safonov
2019-07-31 17:05 ` [PATCH-4.19-stable 0/2] iommu/vt-d: queue_iova() boot crash backport Greg Kroah-Hartman
2019-07-31 17:05 ` Greg Kroah-Hartman
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=20190731170411.GA22660@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=0x7f454c46@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=dima@arista.com \
--cc=dwmw2@infradead.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=stable@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.