From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
Joerg Roedel <joro@8bytes.org>,
"David S. Miller" <davem@davemloft.net>,
sparclinux <sparclinux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Parisc List <linux-parisc@vger.kernel.org>,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu-common: fix return type of iommu_tbl_range_alloc()
Date: Wed, 21 Oct 2015 15:56:40 -0400 [thread overview]
Message-ID: <20151021195640.GC14667@oracle.com> (raw)
In-Reply-To: <CAMuHMdXGM0ynDSv-_MdZptXeqJ=sU7=LChmihSCoqanVTUpWXQ@mail.gmail.com>
On (10/21/15 21:12), Geert Uytterhoeven wrote:
>
> Does this function really need to return DMA_ERROR_CODE in case of
> failure?
fwiw, this came up very early in code review:
http://marc.info/?l=linux-sparc&m=142613044704833&w=2
--Sowmini
WARNING: multiple messages have this Message-ID (diff)
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu-common: fix return type of iommu_tbl_range_alloc()
Date: Wed, 21 Oct 2015 19:56:40 +0000 [thread overview]
Message-ID: <20151021195640.GC14667@oracle.com> (raw)
In-Reply-To: <CAMuHMdXGM0ynDSv-_MdZptXeqJ=sU7=LChmihSCoqanVTUpWXQ@mail.gmail.com>
On (10/21/15 21:12), Geert Uytterhoeven wrote:
>
> Does this function really need to return DMA_ERROR_CODE in case of
> failure?
fwiw, this came up very early in code review:
http://marc.info/?l=linux-sparc&m\x142613044704833&w=2
--Sowmini
WARNING: multiple messages have this Message-ID (diff)
From: sowmini.varadhan@oracle.com (Sowmini Varadhan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu-common: fix return type of iommu_tbl_range_alloc()
Date: Wed, 21 Oct 2015 15:56:40 -0400 [thread overview]
Message-ID: <20151021195640.GC14667@oracle.com> (raw)
In-Reply-To: <CAMuHMdXGM0ynDSv-_MdZptXeqJ=sU7=LChmihSCoqanVTUpWXQ@mail.gmail.com>
On (10/21/15 21:12), Geert Uytterhoeven wrote:
>
> Does this function really need to return DMA_ERROR_CODE in case of
> failure?
fwiw, this came up very early in code review:
http://marc.info/?l=linux-sparc&m=142613044704833&w=2
--Sowmini
next prev parent reply other threads:[~2015-10-21 19:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 8:40 [PATCH] iommu-common: only compile lib/iommu_common.c for Sparc64 Andre Przywara
2015-09-17 8:40 ` Andre Przywara
2015-09-17 8:40 ` Andre Przywara
2015-09-17 18:38 ` David Miller
2015-09-17 18:38 ` David Miller
2015-09-17 18:38 ` David Miller
2015-09-18 9:03 ` Andre Przywara
2015-09-18 9:03 ` Andre Przywara
2015-09-18 9:03 ` Andre Przywara
2015-09-18 9:09 ` [PATCH] iommu-common: fix return type of iommu_tbl_range_alloc() Andre Przywara
2015-09-18 9:09 ` Andre Przywara
2015-09-18 9:09 ` Andre Przywara
2015-10-21 19:12 ` Geert Uytterhoeven
2015-10-21 19:12 ` Geert Uytterhoeven
2015-10-21 19:12 ` Geert Uytterhoeven
2015-10-21 19:12 ` Geert Uytterhoeven
2015-10-21 19:12 ` Geert Uytterhoeven
2015-10-21 19:56 ` Sowmini Varadhan [this message]
2015-10-21 19:56 ` Sowmini Varadhan
2015-10-21 19:56 ` Sowmini Varadhan
2015-09-18 17:09 ` [PATCH] iommu-common: only compile lib/iommu_common.c for Sparc64 David Miller
2015-09-18 17:09 ` David Miller
2015-09-18 17:09 ` David Miller
2015-09-18 17:28 ` Andre Przywara
2015-09-18 17:28 ` Andre Przywara
2015-09-18 17:28 ` Andre Przywara
2015-09-21 17:17 ` [PATCH] sparc(64)/iommu: fixup iommu_tbl_range_alloc() types Andre Przywara
2015-09-21 17:17 ` Andre Przywara
2015-09-21 17:17 ` Andre Przywara
2015-10-05 9:54 ` Andre Przywara
2015-10-05 9:54 ` Andre Przywara
2015-10-05 9:54 ` Andre Przywara
2015-11-04 16:38 ` David Miller
2015-11-04 16:38 ` David Miller
2015-11-04 16:38 ` David Miller
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=20151021195640.GC14667@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=andre.przywara@arm.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=sparclinux@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.