linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	robh@kernel.org, stephen@networkplumber.org,
	ecree.xilinx@gmail.com, sdf@google.com, f.fainelli@gmail.com,
	fw@strlen.de, linux-doc@vger.kernel.org, razor@blackwall.org,
	nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v3 7/8] net: fou: use policy and operation tables generated from the spec
Date: Thu, 19 Jan 2023 21:56:05 +0100	[thread overview]
Message-ID: <a340a5e2da55f352322c2aa902b592ece9bfbb5a.camel@sipsolutions.net> (raw)
In-Reply-To: <20230119003613.111778-8-kuba@kernel.org>

On Wed, 2023-01-18 at 16:36 -0800, Jakub Kicinski wrote:
> 
> +fou-y := fou_core.o fou-nl.o

I feel like you could've been consistent there and used "fou-core.o"
with a dash, but hey :-)

johannes

  reply	other threads:[~2023-01-19 20:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  0:36 [PATCH net-next v3 0/8] Netlink protocol specs Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 1/8] docs: add more netlink docs (incl. spec docs) Jakub Kicinski
2023-01-19 15:48   ` Vladimir Oltean
2023-01-19 20:29   ` Johannes Berg
2023-01-20  0:23     ` Jacob Keller
2023-01-20  9:10       ` Johannes Berg
2023-01-20 18:35         ` Keller, Jacob E
2023-01-20  2:13     ` Jakub Kicinski
2023-01-20  9:15       ` Johannes Berg
2023-01-20 17:23         ` Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 2/8] netlink: add schemas for YAML specs Jakub Kicinski
2023-01-19 14:07   ` Rob Herring
2023-01-19 21:49     ` Jakub Kicinski
2023-01-19 22:24       ` Jakub Kicinski
2023-01-19 23:02       ` Rob Herring
2023-01-20  0:08     ` Jakub Kicinski
2023-01-20 14:43       ` Rob Herring
2023-01-19  0:36 ` [PATCH net-next v3 3/8] net: add basic C code generators for Netlink Jakub Kicinski
2023-01-19 20:53   ` Johannes Berg
2023-01-20  1:53     ` Jakub Kicinski
2023-01-20  9:17       ` Johannes Berg
2023-01-19  0:36 ` [PATCH net-next v3 4/8] netlink: add a proto specification for FOU Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 5/8] net: fou: regenerate the uAPI from the spec Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 6/8] net: fou: rename the source for linking Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 7/8] net: fou: use policy and operation tables generated from the spec Jakub Kicinski
2023-01-19 20:56   ` Johannes Berg [this message]
2023-01-20  0:18     ` Jacob Keller
2023-01-20  1:04       ` Jakub Kicinski
2023-01-19  0:36 ` [PATCH net-next v3 8/8] tools: ynl: add a completely generic client Jakub Kicinski
2023-01-20  0:50   ` Jacob Keller
2023-01-19 17:07 ` [PATCH net-next v3 0/8] Netlink protocol specs Stanislav Fomichev

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=a340a5e2da55f352322c2aa902b592ece9bfbb5a.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=robh@kernel.org \
    --cc=sdf@google.com \
    --cc=stephen@networkplumber.org \
    /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).