From: Uday Shankar <ushankar@purestorage.com>
To: Breno Leitao <leitao@debian.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] netconsole: allow selection of egress interface via MAC address
Date: Mon, 3 Feb 2025 13:29:22 -0700 [thread overview]
Message-ID: <Z6EnIv6M9ujal6Ty@dev-ushankar.dev.purestorage.com> (raw)
In-Reply-To: <20250203-capable-manipulative-angelfish-bebe71@leitao>
On Mon, Feb 03, 2025 at 05:12:37AM -0800, Breno Leitao wrote:
> I wanted to check in on the status of this patchset, as I haven't
> received any updates in the past two weeks. I remain enthusiastic about
> this feature and believe it would be a valuable addition to the next
> major merge window.
>
> If you need any assistance or support, please don't hesitate to reach
> out. I'm more than happy to help.
Hey Breno, thanks for checking in. I've had the functional revisions
(removal of configfs interface) done for some time now, but haven't had
the time to figure out testing - last I checked, it would require a fair
bit of refactoring in libnetcons.sh since we'd have to use the module
parameter interface instead of configfs.
Perhaps it would be okay to merge the functional change first, then
follow up with test later? I'll try to clean up what I have, get a round
of manual testing in, and post it soon.
prev parent reply other threads:[~2025-02-03 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 2:18 [PATCH] netconsole: allow selection of egress interface via MAC address Uday Shankar
2024-12-12 10:11 ` Simon Horman
2024-12-12 22:31 ` Uday Shankar
2024-12-13 10:34 ` Simon Horman
2024-12-12 12:34 ` Paolo Abeni
2024-12-12 21:59 ` Uday Shankar
2025-01-03 11:41 ` Breno Leitao
2025-01-08 15:02 ` Uday Shankar
2025-01-09 15:43 ` Breno Leitao
2025-02-03 13:12 ` Breno Leitao
2025-02-03 20:29 ` Uday Shankar [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=Z6EnIv6M9ujal6Ty@dev-ushankar.dev.purestorage.com \
--to=ushankar@purestorage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.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).