From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] reset: Add a Gemini reset controller
Date: Mon, 08 May 2017 09:01:33 +0200 [thread overview]
Message-ID: <1494226893.3029.21.camel@pengutronix.de> (raw)
In-Reply-To: <CACRpkdaRkWY7qF43-XxOPu5h0cR3_w3ydHs3Ln-Oay+bzw4JWA@mail.gmail.com>
Hi Linus,
On Sun, 2017-05-07 at 21:23 +0200, Linus Walleij wrote:
> On Tue, Apr 25, 2017 at 10:43 AM, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> > [Me]
> >> +/*
> >> + * Cortina Gemini Reset controller driver
> >> + * Copyright (c) 2017 Linus Walleij <linus.walleij@linaro.org>
> >
> > No license statement, choice or oversight?
>
> Choice. I'm one of those guys who think that the top-level COPYING file
> in the kernel is by far enough of legalese. If you want, I can put in a license
> of course.
Yes, please do. The implicit statement made by the Signed-off-by tag
refers to the "license indicated in the file", unfortunately.
[...]
> >> + ret = devm_reset_controller_register(&pdev->dev, &gr->rcdev);
> >> + if (ret)
> >> + return ret;
> >> +
> >> + dev_info(dev, "registered Gemini reset controller\n");
> >
> > This is a bit verbose. I'd remove it and shorten the last part to:
> >
> > return devm_reset_controller_register(&pdev->dev, &gr->rcdev);
>
> It's always this thing whether to be in the camp that like drivers to announce
> themselves or not, but I can do as you suggest if it's a strong preference.
>
> The reason I want it is: deselect the driver from Kconfig, something stops
> working. Compare the dmesg: they both look the same. You don't immediately
> see that something is missing.
>
> So some people think that it is time to go around in /sys, and then what
> if it is a boot regression, like the system can't mount root without the
> reset controller. (Yeah I know, the thing mounting root should select the
> reset controller then, OK another bug we would have seen with this...)
>
> And then all of a sudden there is a lot of debug time spent looking for this
> fact that would be spotted in no time if the was a dev_info() about the
> driver being probed.
>
> But if you insist, I will remove it.
I don't insist.
I am in the camp of people who don't particularly like to see driver
announcements, but that preference only extends to machines I use.
regards
Philipp
next prev parent reply other threads:[~2017-05-08 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 19:28 [PATCH 2/2] reset: Add a Gemini reset controller Linus Walleij
2017-04-25 8:43 ` Philipp Zabel
2017-05-07 19:23 ` Linus Walleij
2017-05-08 7:01 ` Philipp Zabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-24 8:19 Linus Walleij
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=1494226893.3029.21.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).