From: Marcel Holtmann <marcel@holtmann.org>
To: James Prestwood <prestwoj@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: [RFC] udev: Add module for checking interface renaming actions
Date: Tue, 30 Jan 2024 15:54:42 +0100 [thread overview]
Message-ID: <CE05B63F-A9DD-4CF9-A680-198D7329EBE1@holtmann.org> (raw)
In-Reply-To: <a6385e0a-6bd4-4152-930f-a995c0435179@gmail.com>
Hi James,
>> ---
>> Makefile.am | 1 +
>> src/udev.c | 285 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 286 insertions(+)
>> create mode 100644 src/udev.c
>>
> Just curious what this is for. Are we trying to avoid needing to install the link file to disable udev renaming? And instead allow renaming but pick up the changes internally?
this is meant as sample what it takes to wait for udev renaming. When you receive that event above, then you know for sure that udev is done with renaming and we can IFF_UP the hardware.
I do need to check this on big endian and if we have to adjust the hash value for “net”.
Regards
Marcel
prev parent reply other threads:[~2024-01-30 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 23:13 [RFC] udev: Add module for checking interface renaming actions Marcel Holtmann
2024-01-30 12:38 ` James Prestwood
2024-01-30 14:54 ` Marcel Holtmann [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=CE05B63F-A9DD-4CF9-A680-198D7329EBE1@holtmann.org \
--to=marcel@holtmann.org \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).