[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <500ce9e7-9a0f-b632-1731-f15a5ba872fd@embeddedor.com>
Date: Wed, 20 Mar 2019 14:41:35 -0500
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Juergen Gross <jgross@...e.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Kees Cook <keescook@...omium.org>,
xen-devel@...ts.xenproject.org
Subject: Re: [Xen-devel] [PATCH] PCI: Mark expected switch fall-throughs
On 3/20/19 2:27 PM, Andrew Cooper wrote:
> On 20/03/2019 18:27, Gustavo A. R. Silva wrote:
>> diff --git a/drivers/pci/proc.c b/drivers/pci/proc.c
>> index 6fa1627ce08d..445b51db75b0 100644
>> --- a/drivers/pci/proc.c
>> +++ b/drivers/pci/proc.c
>> @@ -222,6 +222,7 @@ static long proc_bus_pci_ioctl(struct file *file, unsigned int cmd,
>> }
>> /* If arch decided it can't, fall through... */
>> #endif /* HAVE_PCI_MMAP */
>> + /* fall through */
>
> Surely it would be better to transpose the #endif and its previous line,
> than to add a second fallthrough ?
>
I agree. The thing is that, currently, GCC is expecting to find the
fall-through "annotations" at the very bottom of the case statement,
as I mentioned it in the changelog text.
That's the reason why I decided to left in place the original comment.
Thanks
--
Gustavo
Powered by blists - more mailing lists