lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 25 Jun 2018 16:33:00 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Dan Carpenter <dan.carpenter@...cle.com>,
        David Lechner <david@...hnology.com>
Cc:     Sekhar Nori <nsekhar@...com>,
        Michael Turquette <mturquette@...libre.com>,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] clk: davinci: cfgchip: testing the wrong variable

Quoting David Lechner (2018-06-25 16:17:55)
> On 06/02/2018 02:52 AM, Dan Carpenter wrote:
> > There is a copy and paste bug here.  We should be testing "usb1" instead
> > of "usb0".
> > 
> > Fixes: 58e1e2d2cd89 ("clk: davinci: cfgchip: Add TI DA8XX USB PHY clocks")
> > Signed-off-by: Dan Carpenter <dan.carpenter@...cle.com>
> > 
> > diff --git a/drivers/clk/davinci/da8xx-cfgchip.c b/drivers/clk/davinci/da8xx-cfgchip.c
> > index c971111d2601..20a120aa147e 100644
> > --- a/drivers/clk/davinci/da8xx-cfgchip.c
> > +++ b/drivers/clk/davinci/da8xx-cfgchip.c
> > @@ -672,7 +672,7 @@ static int of_da8xx_usb_phy_clk_init(struct device *dev, struct regmap *regmap)
> >   
> >       usb1 = da8xx_cfgchip_register_usb1_clk48(dev, regmap);
> >       if (IS_ERR(usb1)) {
> > -             if (PTR_ERR(usb0) == -EPROBE_DEFER)
> > +             if (PTR_ERR(usb1) == -EPROBE_DEFER)
> >                       return -EPROBE_DEFER;
> >   
> >               dev_warn(dev, "Failed to register usb1_clk48 (%ld)\n",
> > 
> 
> Applied to https://github.com/dlech/linux/tree/clk-davinci-fixes
> 

Ok. I expect this will be coming in a PR soon? Usually I can pick up
fixes just fine from the list and merge them on up to Linus, unless you
feel the need to pick it into your development tree to base future
development on.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ