From: Johan Hovold <johan@kernel.org>
To: Jonathan Marek <jonathan@marek.ca>
Cc: linux-arm-msm@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm
Date: Wed, 16 Oct 2024 15:21:16 +0200 [thread overview]
Message-ID: <Zw-9zFwwJfV4yPvO@hovoldconsulting.com> (raw)
In-Reply-To: <8c8df288-cb8c-2e59-a570-e8dcf39a367f@marek.ca>
On Wed, Oct 16, 2024 at 09:12:08AM -0400, Jonathan Marek wrote:
> On 10/16/24 9:02 AM, Johan Hovold wrote:
> >>>> int alarm_irq;
> >>>> const struct pm8xxx_rtc_regs *regs;
> >>>> struct device *dev;
> >>>> @@ -473,9 +474,14 @@ static int pm8xxx_rtc_probe(struct platform_device *pdev)
> >>>> if (!rtc_dd->regmap)
> >>>> return -ENXIO;
> >>>>
> >>>> - rtc_dd->alarm_irq = platform_get_irq(pdev, 0);
> >>>> - if (rtc_dd->alarm_irq < 0)
> >>>> - return -ENXIO;
> >>>> + rtc_dd->no_alarm = of_property_read_bool(pdev->dev.of_node,
> >>>> + "qcom,no-alarm");
> >>>> +
> >>>
> >>> Stray newline.
> >>
> >> That's not a stray newline?
> >
> > There was no empty line between the assignment and check before this
> > change, but now there is even though there should not be.
>
> There was no empty line between the "alarm_irq" assignment and check,
> and there still isn't. That empty line separating the new
> of_property_read_bool() line.
Ah, sorry, my bad.
> I could move both of_property_read_bool() lines together to make it look
> better.
Yeah, that sounds like a good idea.
Johan
next prev parent reply other threads:[~2024-10-16 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 0:47 [PATCH v3 0/5] x1e80100 RTC support Jonathan Marek
2024-10-15 0:47 ` [PATCH v3 1/5] rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm Jonathan Marek
2024-10-15 19:24 ` Bjorn Andersson
2024-10-16 6:42 ` Johan Hovold
2024-10-16 12:26 ` Alexandre Belloni
2024-10-16 12:44 ` Jonathan Marek
2024-10-16 13:02 ` Johan Hovold
2024-10-16 13:12 ` Jonathan Marek
2024-10-16 13:21 ` Johan Hovold [this message]
2024-10-15 0:47 ` [PATCH v3 2/5] dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag Jonathan Marek
2024-10-15 5:33 ` Krzysztof Kozlowski
2024-10-16 6:46 ` Johan Hovold
2025-01-12 23:35 ` [PATCH v3 0/5] x1e80100 RTC support Alexandre Belloni
2025-01-20 14:51 ` Johan Hovold
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=Zw-9zFwwJfV4yPvO@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.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).