public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Teshan Kannangara <tpk.teshan@gmail.com>, <dave@stgolabs.net>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
	<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl/acpi: Fix coding style issues in acpi.c
Date: Tue, 17 Mar 2026 17:59:09 +0000	[thread overview]
Message-ID: <20260317175909.00006cee@huawei.com> (raw)
In-Reply-To: <2aa6594d-3277-4637-af6a-9be11400d05d@intel.com>

On Tue, 17 Mar 2026 07:48:17 -0700
Dave Jiang <dave.jiang@intel.com> wrote:

> On 3/17/26 5:13 AM, Teshan Kannangara wrote:
> > Fix various coding style issues in drivers/cxl/acpi.c, including
> > indentation, line wrapping, macro alignment, cast formatting,
> > and conditional braces.  
> 
> Hi Teshan,
> Thank you for the code changes. While we appreciate it, I'm going to NAK the changes. For this sub-system, we are not going to make style changes or fixes unless it's part of functional code changes or refactor. The reason is to not introduce unnecessary churns to the code that can make fix backports difficult later on. Thanks.
> 
> DJ

I'm going to give it a quick review on the first item at least.

> 
> > 
> > No functional changes.
> > 
> > Signed-off-by: Teshan Kannangara <tpk.teshan@gmail.com>
> > ---
> >  drivers/cxl/acpi.c | 26 +++++++++++++++++---------
> >  1 file changed, 17 insertions(+), 9 deletions(-)
> > 
> > diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> > index 127537628817..b54b962cf973 100644
> > --- a/drivers/cxl/acpi.c
> > +++ b/drivers/cxl/acpi.c
> > @@ -395,9 +395,16 @@ static void cxl_setup_extended_linear_cache(struct cxl_root_decoder *cxlrd)
> >  	cxlrd->cache_size = cache_size;
> >  }
> >  
> > -DEFINE_FREE(put_cxlrd, struct cxl_root_decoder *,
> > -	    if (!IS_ERR_OR_NULL(_T)) put_device(&_T->cxlsd.cxld.dev))
> > -DEFINE_FREE(del_cxl_resource, struct resource *, if (_T) del_cxl_resource(_T))
> > +DEFINE_FREE
> > +(put_cxlrd, struct cxl_root_decoder *,
> > +if (!IS_ERR_OR_NULL(_T))
> > +	put_device(&_T->cxlsd.cxld.dev))
> > +
> > +DEFINE_FREE
> > +(del_cxl_resource, struct resource *,
> > +if (_T)
> > +	del_cxl_resource(_T))
> > +
Why? the original code was the standard way to format these and
there is no explanation of the change in the commit message.
Is it because it's over 80 chars long?  That is guidance only and
if readability is hurt (like here) feel free to go up to 100 chars
before worrying about it.





      reply	other threads:[~2026-03-17 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 12:13 [PATCH] cxl/acpi: Fix coding style issues in acpi.c Teshan Kannangara
2026-03-17 14:48 ` Dave Jiang
2026-03-17 17:59   ` Jonathan Cameron [this message]

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=20260317175909.00006cee@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpk.teshan@gmail.com \
    --cc=vishal.l.verma@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