Messages in this thread | | | Date | Thu, 15 Feb 2024 13:08:42 +0100 | From | Jiri Pirko <> | Subject | Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver |
| |
Thu, Feb 15, 2024 at 08:00:40AM CET, hch@infradead.org wrote: >On Wed, Feb 14, 2024 at 07:48:32AM -0800, Jakub Kicinski wrote:
[...]
>> > I think all maintainers can and should voice the >> > opinions, be those technical or political, but trying to block a useful >> > feature without lots of precedence because it is vaguely related to the >> > subsystem is not helpful. >> >> Not sure what you mean by "without lots of precedence" but you can ask > >Should have been with. Just about every subsystem with complex devices >has this kind of direct interface for observability and co in at least >some drivers.
What about configuration? How do you ensure the direct FW/HW access is used only for observability/debug purposes. I mean, if you can't, I think it is incorrect to name it that way, isn't it?
| |