From: Andrew Lunn <andrew@lunn•ch>
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: Jakub Kicinski <kuba@kernel•org>,
Steve Williams <steve.williams@getcruise•com>,
netdev@vger•kernel.org, vinicius.gomes@intel•com,
xiaoliang.yang_1@nxp•com
Subject: Re: [PATCH net-next] net/hanic: Add the hanic network interface for high availability links
Date: Tue, 22 Nov 2022 20:54:55 +0100 [thread overview]
Message-ID: <Y30pD0B6t4MmUht9@lunn.ch> (raw)
In-Reply-To: <20221122113412.dg4diiu5ngmulih2@skbuf>
> ../drivers/net/hanic/hanic_sysfs.c:83:31: error: ‘struct hanic_netns’ has no member named ‘class_attr_sandlan_interfaces’; did you mean ‘class_attr_hanic_interfaces’?
> 83 | sysfs_attr_init(&xns->class_attr_sandlan_interfaces.attr);
There was another submission over the weekend adding a network
emulation system called sandlan. The cover latter for this patchset
should of at minimum said there was a dependency between the two. But
in practice, there should not be any dependency at all. It is unclear
if sandlan will get merged.
Andrew
next prev parent reply other threads:[~2022-11-22 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 23:26 [PATCH net-next] net/hanic: Add the hanic network interface for high availability links Steve Williams
2022-11-22 0:40 ` Andrew Lunn
2022-11-22 3:58 ` Jakub Kicinski
2022-11-22 11:34 ` Vladimir Oltean
2022-11-22 19:54 ` Andrew Lunn [this message]
2022-11-22 21:01 ` [EXT] " Steve Williams
2022-11-22 20:51 ` Steve Williams
2022-11-23 14:26 ` Vladimir Oltean
2022-11-23 14:52 ` Jiri Pirko
2022-11-23 15:12 ` Andrew Lunn
2023-02-21 11:03 ` Ferenc Fejes
2022-11-23 15:25 ` Vladimir Oltean
2022-11-23 16:36 ` Jiri Pirko
2022-11-29 22:38 ` Steve Williams
2022-11-22 12:49 ` Jiri Pirko
2022-11-22 13:55 ` Vladimir Oltean
2022-11-22 14:06 ` Jiri Pirko
2022-11-22 20:57 ` [EXT] " Steve Williams
2022-11-23 12:46 ` Jiri Pirko
2023-02-21 10:56 ` Ferenc Fejes
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=Y30pD0B6t4MmUht9@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=steve.williams@getcruise$(echo .)com \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
--cc=xiaoliang.yang_1@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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