From: Joerg Roedel <joro@8bytes.org>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/s390: fix sparse warnings
Date: Thu, 26 Nov 2015 14:41:54 +0100 [thread overview]
Message-ID: <20151126134154.GA17674@8bytes.org> (raw)
In-Reply-To: <alpine.LFD.2.11.1511061723260.2646@denkbrett>
On Fri, Nov 06, 2015 at 05:26:24PM +0100, Sebastian Ott wrote:
> Fix these warnings:
> CHECK drivers/iommu/s390-iommu.c
> drivers/iommu/s390-iommu.c:52:21: warning: symbol 's390_domain_alloc' was not declared. Should it be static?
> drivers/iommu/s390-iommu.c:76:6: warning: symbol 's390_domain_free' was not declared. Should it be static?
>
> Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Applied, thanks.
prev parent reply other threads:[~2015-11-26 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 16:26 [PATCH] iommu/s390: fix sparse warnings Sebastian Ott
2015-11-26 13:41 ` Joerg Roedel [this message]
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=20151126134154.GA17674@8bytes.org \
--to=joro@8bytes.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebott@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox