Hi Miquel, On mar., janv. 08 2019, Miquel Raynal <[email protected]> wrote:
> The error message should state that the driver failed to get the > parent clock, not the opposite. > > Signed-off-by: Miquel Raynal <[email protected]> Reviewed-by: Gregory CLEMENT <[email protected]> Thanks, Gregory > --- > drivers/clk/mvebu/armada-37xx-tbg.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/clk/mvebu/armada-37xx-tbg.c > b/drivers/clk/mvebu/armada-37xx-tbg.c > index ee272d4d8c24..77b978c55ef6 100644 > --- a/drivers/clk/mvebu/armada-37xx-tbg.c > +++ b/drivers/clk/mvebu/armada-37xx-tbg.c > @@ -98,7 +98,7 @@ static int armada_3700_tbg_clock_probe(struct > platform_device *pdev) > > parent = clk_get(dev, NULL); > if (IS_ERR(parent)) { > - dev_err(dev, "Could get the clock parent\n"); > + dev_err(dev, "Could not get the clock parent\n"); > return -EINVAL; > } > parent_name = __clk_get_name(parent); > -- > 2.19.1 > -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com
