netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] connector, linux++: fix <uapi/linux/cn_proc.h> header
Date: Wed, 24 Jan 2024 08:40:27 +0000	[thread overview]
Message-ID: <20240124084027.GR254773@kernel.org> (raw)
In-Reply-To: <3878dc5a-9046-4d7a-bf9e-70dcdc5d9265@p183>

On Tue, Jan 23, 2024 at 01:16:46PM +0300, Alexey Dobriyan wrote:
> Rules around enums are stricter in C++, they decay to ints just as
> easily but don't convert back to enums:
> 
> 	#define PROC_EVENT_ALL (PROC_EVENT_FORK|...)
> 	enum proc_cn_event ev_type;
> 	ev_type &= PROC_EVENT_ALL;
> 
> main.cc: In function ‘proc_cn_event valid_event(proc_cn_event)’:
> main.cc:91:17: error: invalid conversion from ‘unsigned int’ to ‘proc_cn_event’ [-fpermissive]
>    91 |         ev_type &= PROC_EVENT_ALL;
>       |                 ^
>       |                 |
>       |                 unsigned int
> 
> Use casts so that both C and C++ compilers are satisfied.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
> 
>  include/uapi/linux/cn_proc.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> --- a/include/uapi/linux/cn_proc.h
> +++ b/include/uapi/linux/cn_proc.h
> @@ -69,8 +69,7 @@ struct proc_input {
>  
>  static inline enum proc_cn_event valid_event(enum proc_cn_event ev_type)
>  {
> -	ev_type &= PROC_EVENT_ALL;
> -	return ev_type;
> +	return (enum proc_cn_event)(ev_type & PROC_EVENT_ALL)

Hi Alexey,

I think the line above needs a ; at the end of it.

>  }
>  
>  /*
> -- 
> 2.43.0
> 

      reply	other threads:[~2024-01-24  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 10:16 [PATCH 2/2] connector, linux++: fix <uapi/linux/cn_proc.h> header Alexey Dobriyan
2024-01-24  8:40 ` Simon Horman [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=20240124084027.GR254773@kernel.org \
    --to=horms@kernel.org \
    --cc=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).