All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC net-next] generate boilerplate impls such as devlink_resource_register()
Date: Wed, 3 Jul 2024 17:51:11 -0700	[thread overview]
Message-ID: <20240703175111.0832953e@kernel.org> (raw)
In-Reply-To: <4886830b-73fe-47f5-9635-0f3910c8e205@intel.com>

On Wed, 3 Jul 2024 12:13:58 +0200 Przemek Kitszel wrote:
> I have and idea that boilerplate devlink_ wrappers over devl_ functions
> could be generated via short script, with the handcrafted .c code as the
> only input. Take for example the following [one line] added to 
> devlink/resource.c would replace the whole definition and kdoc, which 
> would be placed in the generated file in about the same form as the
> current code. This will be applied to all suitable functions of course.

How?

> The script will be short, but not so trivial to write it without prior
> RFC. For those wondering if I don't have better things to do: yes, but
> I have also some awk-time that will not be otherwise spend on more 
> serious stuff anyway :)

What's the exchange rate from awk-time to other types of time?

  reply	other threads:[~2024-07-04  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 10:13 [RFC net-next] generate boilerplate impls such as devlink_resource_register() Przemek Kitszel
2024-07-04  0:51 ` Jakub Kicinski [this message]
2024-07-04  7:23   ` Przemek Kitszel

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=20240703175111.0832953e@kernel.org \
    --to=kuba@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.