public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "bwidawsk@kernel.org" <bwidawsk@kernel.org>,
	"Jiang, Dave" <dave.jiang@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	"raghuhack78@gmail.com" <raghuhack78@gmail.com>,
	"Weiny, Ira" <ira.weiny@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] cxl/region: Remove else after return statement
Date: Wed, 3 May 2023 17:58:31 +0000	[thread overview]
Message-ID: <b4cd9ff666fdbb2d0ff31736ad61b3475d6f4b26.camel@intel.com> (raw)
In-Reply-To: <da1dad4b-cdee-76e3-a3eb-cb39b6ee1423@intel.com>

On Mon, 2023-05-01 at 07:53 -0700, Dave Jiang wrote:
> 
> 
> On 4/27/23 6:22 PM, Raghu H 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 H <raghuhack78@gmail.com>
> 
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> 
> > ---
> >   drivers/cxl/core/region.c | 8 ++++----
> >   1 file changed, 4 insertions(+), 4 deletions(-)

Looks good,
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>

> > 
> > diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> > index f29028148806..a46d6ad9ef0a 100644
> > --- a/drivers/cxl/core/region.c
> > +++ b/drivers/cxl/core/region.c
> > @@ -2666,11 +2666,11 @@ static int cxl_region_invalidate_memregion(struct cxl_region *cxlr)
> >                                 "Bypassing cpu_cache_invalidate_memregion() for testing!\n");
> >                         clear_bit(CXL_REGION_F_INCOHERENT, &cxlr->flags);
> >                         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);


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  1:22 [PATCH v2 0/2] Fixing check patch styling issues Raghu H
2023-04-28  1:22 ` [PATCH v2 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc Raghu H
2023-05-01 14:52   ` Dave Jiang
2023-05-03 17:57   ` Verma, Vishal L
2023-05-03 18:32   ` Fabio M. De Francesco
2023-05-03 22:03     ` Alison Schofield
2023-05-04 10:46       ` Fabio M. De Francesco
2023-05-04 15:23         ` Alison Schofield
2023-05-08  4:12           ` RAGHU H
2023-05-03 22:36   ` Davidlohr Bueso
2023-05-04  2:26     ` Alison Schofield
2023-04-28  1:22 ` [PATCH v2 2/2] cxl/region: Remove else after return statement Raghu H
2023-05-01 14:53   ` Dave Jiang
2023-05-03 17:58     ` Verma, Vishal L [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=b4cd9ff666fdbb2d0ff31736ad61b3475d6f4b26.camel@intel.com \
    --to=vishal.l.verma@intel.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 \
    /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