mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Li Zhijian <lizhijian@fujitsu.com>, linux-cxl@vger.kernel.org
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
	alison.schofield@intel.com, vishal.l.verma@intel.com,
	ira.weiny@intel.com, dan.j.williams@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next] cxl: Fix -Werror=return-type in cxl_decoder_detach()
Date: Thu, 17 Jul 2025 16:21:04 -0700	[thread overview]
Message-ID: <848e0e2f-c2cf-4c07-ae48-b12cf1d0b332@intel.com> (raw)
In-Reply-To: <20250717031251.1043825-1-lizhijian@fujitsu.com>



On 7/16/25 8:12 PM, Li Zhijian wrote:
> Fix following compiling errors:
> In file included from ../drivers/cxl/core/pmu.c:10:
> ../drivers/cxl/core/core.h: In function ‘cxl_decoder_detach’:
> ../drivers/cxl/core/core.h:65:1: error: no return statement in function returning non-void [-Werror=return-type]
>  }
>  ^
> cc1: some warnings being treated as errors
>   CC [M]  drivers/nvdimm/claim.o
> make[6]: *** [../scripts/Makefile.build:287: drivers/cxl/core/pmu.o] Error 1
> make[6]: *** Waiting for unfinished jobs....
>   CC [M]  drivers/infiniband/core/verbs.o
> 
> Fixes: b3a88225519c ("cxl/region: Consolidate cxl_decoder_kill_region() and cxl_region_detach()")
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>

Thanks! I applied to cxl/next

1d0d1bc44e98dc90d478badb40de5e3adb747c2e


> ---
> I'm curious why the LKP robot didn't report this.

Yes. Odd. I guess randconf has not turned off CONFIG_CXL_REGION

DJ 

> ---
>  drivers/cxl/core/core.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cxl/core/core.h b/drivers/cxl/core/core.h
> index 705a5f09aa78..2669f251d677 100644
> --- a/drivers/cxl/core/core.h
> +++ b/drivers/cxl/core/core.h
> @@ -62,6 +62,7 @@ static inline int cxl_decoder_detach(struct cxl_region *cxlr,
>  				     struct cxl_endpoint_decoder *cxled,
>  				     int pos, enum cxl_detach_mode mode)
>  {
> +	return 0;
>  }
>  static inline int cxl_region_init(void)
>  {


      reply	other threads:[~2025-07-17 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17  3:12 Li Zhijian
2025-07-17 23:21 ` Dave Jiang [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=848e0e2f-c2cf-4c07-ae48-b12cf1d0b332@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhijian@fujitsu.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®