From: Joe Perches <joe@perches.com>
To: Alison Schofield <alison.schofield@intel.com>,
Raghu Halharvi <raghuhack78@gmail.com>
Cc: linux-cxl@vger.kernel.org, ira.weiny@intel.com,
bwidawsk@kernel.org, dan.j.williams@intel.com,
vishal.l.verma@intel.com, linux-kernel@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH v7 2/2] cxl/region: Remove else after return statement
Date: Sun, 30 Jul 2023 13:09:26 -0700 [thread overview]
Message-ID: <15913bee637e2cff63626dc64c0577abc1ad9c6c.camel@perches.com> (raw)
In-Reply-To: <ZMXIi+HC3uFQyvGK@aschofie-mobl2>
On Sat, 2023-07-29 at 19:18 -0700, Alison Schofield wrote:
> On Wed, Jul 26, 2023 at 07:34:21AM +0000, Raghu Halharvi wrote:
> > Issue found with checkpatch
> >
> > The else section here is redundant after return statement, removing it.
> > Sanity and correctness is not affected due to this fix.
> >
> > Signed-off-by: Raghu Halharvi <raghuhack78@gmail.com>
> > Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> > Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
> > Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
>
>
> > ---
> > drivers/cxl/core/region.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> > index e115ba382e04..bfd3b13dd2c1 100644
> > --- a/drivers/cxl/core/region.c
> > +++ b/drivers/cxl/core/region.c
> > @@ -133,11 +133,11 @@ static int cxl_region_invalidate_memregion(struct cxl_region *cxlr)
> > &cxlr->dev,
> > "Bypassing cpu_cache_invalidate_memregion() for testing!\n");
> > return 0;
> > - } else {
> > - dev_err(&cxlr->dev,
> > - "Failed to synchronize CPU cache state\n");
> > - return -ENXIO;
> > }
> > +
> > + dev_err(&cxlr->dev,
> > + "Failed to synchronize CPU cache state\n");
> > + return -ENXIO;
> > }
> >
> > cpu_cache_invalidate_memregion(IORES_DESC_CXL);
> > --
> > 2.39.2
> >
My preference would be for this function to be something like:
---
static int cxl_region_invalidate_memregion(struct cxl_region *cxlr)
{
if (cpu_cache_has_invalidate_memregion()) {
cpu_cache_invalidate_memregion(IORES_DESC_CXL);
return 0;
}
if (IS_ENABLED(CONFIG_CXL_REGION_INVALIDATION_TEST)) {
dev_warn_once(&cxlr->dev,
"Bypassing cpu_cache_invalidate_memregion() for testing!\n");
return 0;
}
dev_err(&cxlr->dev, "Failed to synchronize CPU cache state\n");
return -ENXIO;
}
prev parent reply other threads:[~2023-07-30 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 7:34 [PATCH v7 0/2] Fixing check patch styling issues Raghu Halharvi
2023-07-26 7:34 ` [PATCH v7 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc Raghu Halharvi
2023-07-30 2:17 ` Alison Schofield
2023-07-26 7:34 ` [PATCH v7 2/2] cxl/region: Remove else after return statement Raghu Halharvi
2023-07-30 2:18 ` Alison Schofield
2023-07-30 20:09 ` Joe Perches [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=15913bee637e2cff63626dc64c0577abc1ad9c6c.camel@perches.com \
--to=joe@perches.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@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
all inboxes | Powered by JetHome®