Linux CXL
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Raghu H <raghuhack78@gmail.com>, <linux-cxl@vger.kernel.org>,
	"Alison Schofield" <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Ben Widawsky <bwidawsk@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [STYLE v1 2/3] cxl/core/port: Use tabs to fix styling errors
Date: Thu, 27 Apr 2023 12:06:27 -0700	[thread overview]
Message-ID: <644ac7b3e5354_182a929456@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230419111443.231151-3-raghuhack78@gmail.com>

Raghu H wrote:
> Styling errors due to linux of unwanted spaces in the definition,
> modified the definition to use tab to fix the styling issue.
> 
> Signed-off-by: Raghu H <raghuhack78@gmail.com>

NAK

This is unnecessary churn.  The formatting of the file is fine and very
readable.

Ira

> ---
>  drivers/cxl/core/port.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/cxl/core/port.c b/drivers/cxl/core/port.c
> index 8ee6b6e2e2a4..7c3aaed180ca 100644
> --- a/drivers/cxl/core/port.c
> +++ b/drivers/cxl/core/port.c
> @@ -95,15 +95,15 @@ static ssize_t size_show(struct device *dev, struct device_attribute *attr,
>  }
>  static DEVICE_ATTR_RO(size);
>  
> -#define CXL_DECODER_FLAG_ATTR(name, flag)                            \
> -static ssize_t name##_show(struct device *dev,                       \
> -			   struct device_attribute *attr, char *buf) \
> -{                                                                    \
> -	struct cxl_decoder *cxld = to_cxl_decoder(dev);              \
> -                                                                     \
> -	return sysfs_emit(buf, "%s\n",                               \
> -			  (cxld->flags & (flag)) ? "1" : "0");       \
> -}                                                                    \
> +#define CXL_DECODER_FLAG_ATTR(name, flag)				\
> +static ssize_t name##_show(struct device *dev,				\
> +			   struct device_attribute *attr, char *buf)	\
> +{									\
> +	struct cxl_decoder *cxld = to_cxl_decoder(dev);			\
> +									\
> +	return sysfs_emit(buf, "%s\n",					\
> +			  (cxld->flags & (flag)) ? "1" : "0");		\
> +}									\
>  static DEVICE_ATTR_RO(name)
>  
>  CXL_DECODER_FLAG_ATTR(cap_pmem, CXL_DECODER_F_PMEM);
> -- 
> 2.39.2
> 



  reply	other threads:[~2023-04-27 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 11:14 [STYLE v1 0/3] Fixing check patch styling issues Raghu H
2023-04-19 11:14 ` [STYLE v1 1/3] cxl/mbox: remove redundant debug msg Raghu H
2023-04-27 19:05   ` Ira Weiny
2023-04-27 19:32   ` Alison Schofield
2023-04-19 11:14 ` [STYLE v1 2/3] cxl/core/port: Use tabs to fix styling errors Raghu H
2023-04-27 19:06   ` Ira Weiny [this message]
2023-04-19 11:14 ` [STYLE v1 3/3] cxl/core/region:Remove else after return statement Raghu H
2023-04-27 19:13   ` Ira Weiny
2023-04-27 19:49     ` Alison Schofield
2023-04-28  0:00       ` RAGHU H
2023-04-27 19:46 ` [STYLE v1 0/3] Fixing check patch styling issues Alison Schofield

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=644ac7b3e5354_182a929456@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raghuhack78@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