From: Kartik Rajput <kkartik@nvidia.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Bart Van Assche" <bvanassche@acm.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@sandisk.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Thierry Reding <treding@nvidia.com>,
linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] scsi: ufs: tegra: Add Tegra264 UFS host controller driver
Date: Tue, 22 Sep 2026 15:05:14 +0530 [thread overview]
Message-ID: <9145429d-95c7-415f-8e54-027818ef1251@nvidia.com> (raw)
In-Reply-To: <f6cd2cb7-48ef-4f0d-83d5-0c2beae5aab5@nvidia.com>
On 22/09/26 15:02, Kartik Rajput wrote:
> Hi Uwe, Bart,
>
> Thanks for reviewing the patch.
>
> On 10/09/26 19:22, Uwe Kleine-König wrote:
>> Hello Bart,
>>
>> On Thu, Sep 10, 2026 at 06:09:30AM -0700, Bart Van Assche wrote:
>>> On 9/10/26 4:21 AM, Uwe Kleine-König wrote:
>>>> What makes you claim that {} is preferred?
>>>
>>> There are many more occurrences of " = {};" (about 7000) in the Linux
>>> kernel than of " = { };" (about 1500). Additionally, clang-format
>>> changes any occurrence of " = { };" into " = {};".
>>
>> clang-format does this due to
>>
>> SpaceInEmptyParentheses: false
>>
>> in .clang-format which I claim we have due to prefering no space between
>> () for function calls. It seems only newer clang-format (starting with
>> version 22) can configure that individually using SpaceInEmptyBraces.
>>
>> And IMHO my statistic is more relevant because we're not talking about
>> `= {};` or `= { };`.
>>
>> But I guess this is all subjective. Having said that I feel offended
>> when seeing "= {};" and would ask to add a space there, too, when
>> spotting that during a review.
>>
>> Best regards
>> Uwe
>
> ACK, I will use `{}` instead of `{ }`. Or if you prefer, I can use `{ /* sentinel */ }`.
>
Apologies, `{ }` instead of `{}`
Thanks,
Kartik
next prev parent reply other threads:[~2026-09-22 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 10:41 [PATCH 0/4] Add UFS host controller support for NVIDIA Tegra264 Kartik Rajput
2026-09-09 10:41 ` [PATCH 1/4] dt-bindings: ufs: Add nvidia,tegra264-ufs Kartik Rajput
2026-09-13 8:40 ` Krzysztof Kozlowski
2026-09-22 9:22 ` Kartik Rajput
2026-09-09 10:41 ` [PATCH 2/4] scsi: ufs: Add UIC DEBUGSAVECONFIGTIME attribute and its field masks Kartik Rajput
2026-09-09 10:41 ` [PATCH 3/4] scsi: ufs: hisi: Use VS_DEBUGSAVECONFIGTIME instead of a literal address Kartik Rajput
2026-09-09 10:41 ` [PATCH 4/4] scsi: ufs: tegra: Add Tegra264 UFS host controller driver Kartik Rajput
2026-09-09 14:20 ` Uwe Kleine-König
2026-09-09 16:10 ` Bart Van Assche
2026-09-10 11:21 ` Uwe Kleine-König
2026-09-10 13:09 ` Bart Van Assche
2026-09-10 13:52 ` Uwe Kleine-König
2026-09-22 9:32 ` Kartik Rajput
2026-09-22 9:35 ` Kartik Rajput [this message]
2026-09-22 9:36 ` Kartik Rajput
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=9145429d-95c7-415f-8e54-027818ef1251@nvidia.com \
--to=kkartik@nvidia.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.com \
--cc=u.kleine-koenig@baylibre.com \
/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
all inboxes | Powered by JetHome®