From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: allison.henderson@oracle.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF note
Date: Tue, 10 Jun 2025 16:54:13 -0400 [thread overview]
Message-ID: <aEibdVJDL7oolbc1@char.us.oracle.com> (raw)
In-Reply-To: <aaef74e8-5517-49ae-aaf5-2ca82ca4ee28@lunn.ch>
On Tue, Jun 10, 2025 at 10:50:06PM +0200, Andrew Lunn wrote:
> > Right..
> > > as /dev/null.
> >
> > Not sure I follow. Make them the same a /dev/null? Meaning link them to
> > /dev/null when the module is loaded?
>
> I mean the contents of the file does not matter. All that matters is
> if the file exists or not. The IOCTL etc should never change, and if
> they do, the patch which changes them will be reverted. So i would
> make them a 0 byte file. You can even make it have mode 0000.
Gotcha! That seems to run counter to what the sysfs expects?
It has to have _something_ in them. But let me play around and see.
Thanks for the feedback!
>
> However, i would first try to copy existing ideas...
Yup, lets see what the other folks have to say.
>
> Andrew
next prev parent reply other threads:[~2025-06-10 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:27 [PATCH RFC v1] Feature reporting of RDS driver Konrad Rzeszutek Wilk
2025-06-10 16:27 ` [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF note Konrad Rzeszutek Wilk
2025-06-10 20:30 ` Andrew Lunn
2025-06-10 20:41 ` Konrad Rzeszutek Wilk
2025-06-10 20:50 ` Andrew Lunn
2025-06-10 20:54 ` Konrad Rzeszutek Wilk [this message]
2025-06-10 20:51 ` Konrad Rzeszutek Wilk
2025-06-12 9:17 ` Leon Romanovsky
2025-06-10 20:47 ` [rds-devel] [PATCH RFC v1] Feature reporting of RDS driver Konrad Rzeszutek Wilk
2025-06-10 21:32 ` Tejun Heo
2025-06-10 23:15 ` Konrad Rzeszutek Wilk
2025-06-16 17:45 ` Tejun Heo
2025-06-10 21:09 ` Allison Henderson
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=aEibdVJDL7oolbc1@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=allison.henderson@oracle.com \
--cc=andrew@lunn.ch \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.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.