netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com
Subject: Re: [PATCH net-next 2/4] tools: ynl: user space helpers
Date: Sun, 4 Jun 2023 11:00:34 -0700	[thread overview]
Message-ID: <20230604110034.08015f1b@kernel.org> (raw)
In-Reply-To: <ZHtSbn1oHl4KcfUL@corigine.com>

On Sat, 3 Jun 2023 16:47:10 +0200 Simon Horman wrote:
> > +/**
> > + * struct ynl_error - error encountered by YNL
> > + * Users should interact with the err member of struct ynl_sock directly.
> > + * The main exception to that rule is ynl_sock_create().  
> 
> nit: As this is a kernel doc, maybe document the structure members here.
> 
> > + */
> > +struct ynl_error {
> > +	enum ynl_error_code code;
> > +	unsigned int attr_offs;
> > +	char msg[512];
> > +};
> > +
> > +/**
> > + * struct ynl_family - YNL family info
> > + * Family description generated by codegen.  
> 
> And here.
> 
> > + */
> > +struct ynl_family {
> > +	const char *name;
> > +	const struct ynl_ntf_info *ntf_info;
> > +	unsigned int ntf_info_size;
> > +};  
> 
> ...
> 
> > +/**
> > + * ynl_has_ntf() - check if socket has *parsed* notifications
> > + * Note that this does not take into account notifications sitting
> > + * in netlink socket, just the notifications which have already been
> > + * read and parsed (e.g. during a ynl_ntf_check() call).  
> 
> And the parameter of this function here.

Thanks, not sure why my brain considered this "not really kernel code
so I don't have to obey the rules" :S I marked the innards of the
family as private, and tossed in the other descriptions. v2 posted.

  reply	other threads:[~2023-06-04 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03  5:25 [PATCH net-next 0/4] tools: ynl: user space C Jakub Kicinski
2023-06-03  5:25 ` [PATCH net-next 1/4] tools: ynl-gen: clean up stray new lines at the end of reply-less requests Jakub Kicinski
2023-06-03  5:25 ` [PATCH net-next 2/4] tools: ynl: user space helpers Jakub Kicinski
2023-06-03 14:47   ` Simon Horman
2023-06-04 18:00     ` Jakub Kicinski [this message]
2023-06-05 11:51       ` Simon Horman
2023-06-03  5:25 ` [PATCH net-next 3/4] tools: ynl: support fou and netdev in C Jakub Kicinski
2023-06-03  5:25 ` [PATCH net-next 4/4] tools: ynl: add sample for netdev Jakub Kicinski

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=20230604110034.08015f1b@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.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).