From: Nicolin Chen <nicolinc@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: kernel test robot <lkp@intel.com>, <jgg@nvidia.com>,
<kevin.tian@intel.com>, <joro@8bytes.org>, <will@kernel.org>,
<oe-kbuild-all@lists.linux.dev>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] iommu: Sort out domain user data
Date: Wed, 5 Mar 2025 09:48:08 -0800 [thread overview]
Message-ID: <Z8iOWB1vH+bBMPWo@Asurada-Nvidia> (raw)
In-Reply-To: <3699641b-c7bc-4fec-b8e2-828f5b1f2d70@arm.com>
On Wed, Mar 05, 2025 at 03:45:21PM +0000, Robin Murphy wrote:
> > All errors (new ones prefixed by >>):
> >
> > > > drivers/iommu/iommu.c:2039:10: error: label at end of compound statement: expected statement
> > default:
> > ^
> > ;
> > 1 error generated.
>
> Oops, my bad... omitting an extra break here was a semi-conscious brainfart.
> Weird that my AArch64 GCC doesn't complain about this construct though, even
> with "-ansi -Wall" - I have to go all the way to -Wpedantic before it
> notices :/
Mine doesn't complain about this either.
I will add a break and respin.
Thanks
Nicolin
next prev parent reply other threads:[~2025-03-05 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 20:52 [PATCH v3 0/3] iommu: Clean up cookie and sw_msi in struct iommu_domain Nicolin Chen
2025-03-03 20:52 ` [PATCH v3 1/3] iommu: Sort out domain user data Nicolin Chen
2025-03-05 15:08 ` kernel test robot
2025-03-05 15:18 ` kernel test robot
2025-03-05 15:45 ` Robin Murphy
2025-03-05 17:48 ` Nicolin Chen [this message]
2025-03-05 16:51 ` kernel test robot
2025-03-05 17:44 ` kernel test robot
2025-03-06 5:59 ` Tian, Kevin
2025-03-06 20:10 ` Nicolin Chen
2025-03-03 20:52 ` [PATCH v3 2/3] iommufd: Move iommufd_sw_msi and related functions to driver.c Nicolin Chen
2025-03-05 17:53 ` Jason Gunthorpe
2025-03-05 18:53 ` Nicolin Chen
2025-03-03 20:52 ` [PATCH v3 3/3] iommu: Drop sw_msi from iommu_domain Nicolin Chen
2025-03-04 14:50 ` Robin Murphy
2025-03-06 6:01 ` Tian, Kevin
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=Z8iOWB1vH+bBMPWo@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=will@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.