From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Gote, Nitin R" <nitin.r.gote@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/pcode: Fix the coding style
Date: Wed, 12 Feb 2025 11:53:27 +0200 [thread overview]
Message-ID: <87pljnzdyg.fsf@intel.com> (raw)
In-Reply-To: <SJ0PR11MB58672CCB29FDDEF79D897C5BD0FC2@SJ0PR11MB5867.namprd11.prod.outlook.com>
On Wed, 12 Feb 2025, "Gote, Nitin R" <nitin.r.gote@intel.com> wrote:
> Hi,
>
>> -----Original Message-----
>> From: Jani Nikula <jani.nikula@linux.intel.com>
>> Sent: Tuesday, February 11, 2025 6:56 PM
>> To: Andi Shyti <andi.shyti@linux.intel.com>; Gote, Nitin R
>> <nitin.r.gote@intel.com>
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: Re: [PATCH] drm/i915/pcode: Fix the coding style
>>
>> On Mon, 10 Feb 2025, Andi Shyti <andi.shyti@linux.intel.com> wrote:
>> > Hi Nitin,
>> >
>> > On Mon, Feb 10, 2025 at 07:39:24PM +0530, Nitin Gote wrote:
>> >> Prefer binary operator at the end of the previous line instead of
>> >> putting operator at the start of the next line as per coding style.
>> >
>> > I'm not finding any documentation for this change, where did you take
>> > it?
>>
>> If not documented, it's the prevalent style, anyway.
>
> Yeah, My bad I thought it is a standard coding style but it is not so.
> But still, I feel the more correct way is to use binary "|" operator in continuation of first line
> instead of second line.
Yes, that's what I said, that's the prevalent style.
>
> Thanks,
> Nitin
>>
>> BR,
>> Jani.
>>
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-12 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 14:09 [PATCH] drm/i915/pcode: Fix the coding style Nitin Gote
2025-02-10 14:22 ` Andi Shyti
2025-02-11 13:25 ` Jani Nikula
2025-02-12 9:46 ` Gote, Nitin R
2025-02-12 9:53 ` Jani Nikula [this message]
2025-02-10 18:05 ` ✗ i915.CI.BAT: failure for " Patchwork
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=87pljnzdyg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nitin.r.gote@intel.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