All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
	<wim@linux-watchdog.org>, <linux@roeck-us.net>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: timer: atmel,at91sam9260-pit: convert to yaml
Date: Fri, 9 Jun 2023 12:21:41 +0000	[thread overview]
Message-ID: <897b1a45-dadc-eaa8-eb7d-c604ff723c2c@microchip.com> (raw)
In-Reply-To: <5fc609e0-a70f-03e6-6ac2-db96a2ff7747@linaro.org>

On 09.06.2023 15:18, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 09/06/2023 14:09, Claudiu.Beznea@microchip.com wrote:
>>>>>
>>>>> interrupts? They are still required, so why no description here?
>>>>
>>>> It was here in the previous versions but Conor suggested to remove it as it
>>>> was nothing specific about this description. For the if-then branch I kept
>>>> it to specify that the interrupt is share with other devices. In this
>>>> branch the interrupt is only for the timer itself. With this, would you
>>>> still prefer to add it back?
>>>
>>> I just don't understand why interrupts are in one arm of the if: and not
>>> in the other.
>>>
>>
>> As previously mentioned, Conor suggested to have it like this.
>>
> 
> ok

Would you still prefer to add back interrupt description on both branches
of if?

> 
> Best regards,
> Krzysztof
> 


WARNING: multiple messages have this Message-ID (diff)
From: <Claudiu.Beznea@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
	<wim@linux-watchdog.org>, <linux@roeck-us.net>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: timer: atmel,at91sam9260-pit: convert to yaml
Date: Fri, 9 Jun 2023 12:21:41 +0000	[thread overview]
Message-ID: <897b1a45-dadc-eaa8-eb7d-c604ff723c2c@microchip.com> (raw)
In-Reply-To: <5fc609e0-a70f-03e6-6ac2-db96a2ff7747@linaro.org>

On 09.06.2023 15:18, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 09/06/2023 14:09, Claudiu.Beznea@microchip.com wrote:
>>>>>
>>>>> interrupts? They are still required, so why no description here?
>>>>
>>>> It was here in the previous versions but Conor suggested to remove it as it
>>>> was nothing specific about this description. For the if-then branch I kept
>>>> it to specify that the interrupt is share with other devices. In this
>>>> branch the interrupt is only for the timer itself. With this, would you
>>>> still prefer to add it back?
>>>
>>> I just don't understand why interrupts are in one arm of the if: and not
>>> in the other.
>>>
>>
>> As previously mentioned, Conor suggested to have it like this.
>>
> 
> ok

Would you still prefer to add back interrupt description on both branches
of if?

> 
> Best regards,
> Krzysztof
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-06-09 12:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  9:07 [PATCH v3 0/3] dt-bindings: timer: Microchip AT91 convert to YAML Claudiu Beznea
2023-05-30  9:07 ` Claudiu Beznea
2023-05-30  9:07 ` [PATCH v3 1/3] dt-bindings: timer: atmel,at91sam9260-pit: convert to yaml Claudiu Beznea
2023-05-30  9:07   ` Claudiu Beznea
2023-05-31  8:55   ` Krzysztof Kozlowski
2023-05-31  8:55     ` Krzysztof Kozlowski
2023-06-09 10:22     ` Claudiu.Beznea
2023-06-09 10:22       ` Claudiu.Beznea
2023-06-09 10:48       ` Krzysztof Kozlowski
2023-06-09 10:48         ` Krzysztof Kozlowski
2023-06-09 12:09         ` Claudiu.Beznea
2023-06-09 12:09           ` Claudiu.Beznea
2023-06-09 12:18           ` Krzysztof Kozlowski
2023-06-09 12:18             ` Krzysztof Kozlowski
2023-06-09 12:21             ` Claudiu.Beznea [this message]
2023-06-09 12:21               ` Claudiu.Beznea
2023-05-30  9:07 ` [PATCH v3 2/3] dt-bindings: watchdog: atmel,at91rm9200-wdt: " Claudiu Beznea
2023-05-30  9:07   ` Claudiu Beznea
2023-05-31  8:56   ` Krzysztof Kozlowski
2023-05-31  8:56     ` Krzysztof Kozlowski
2023-05-30  9:07 ` [PATCH v3 3/3] dt-bindings: timer: atmel,at91rm9200-st: " Claudiu Beznea
2023-05-30  9:07   ` Claudiu Beznea
2023-05-31  8:58   ` Krzysztof Kozlowski
2023-05-31  8:58     ` Krzysztof Kozlowski
2023-05-30 12:29 ` [PATCH v3 0/3] dt-bindings: timer: Microchip AT91 convert to YAML Nicolas Ferre
2023-05-30 12:29   ` Nicolas Ferre

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=897b1a45-dadc-eaa8-eb7d-c604ff723c2c@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.