[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXPbozFVw25gVGvW@rocinante>
Date: Sat, 23 Oct 2021 11:53:39 +0200
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Richard Zhu <hongxing.zhu@....com>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
"l.stach@...gutronix.de" <l.stach@...gutronix.de>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"lorenzo.pieralisi@....com" <lorenzo.pieralisi@....com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: Re: [RESEND v2 4/5] PCI: imx6: Fix the clock reference handling
unbalance when link never came up
Hi,
[...]
> > > > > - default:
> > > > > - break;
> > >
> > > While you're at it, this "default: break;" thing is pointless.
> > > Normally it's better to just *move* something without changing it at
> > > all, but this is such a simple thing I think you could drop this at
> > > the same time as the move.
> > >
> > [Richard Zhu] Okay, got that. Would remove the "default:break" later. Thanks.
> [Richard Zhu] I figure out that the default:break is required by IMX6Q/IMX6QP.
> So I just don't drop them in v3 patch-set.
I hope you don't mind me asking, but how is an empty default case in the
switch statement helping IMX6Q and IMX6QP? What does it achieve for these
two controllers specifically?
Krzysztof
Powered by blists - more mailing lists