On Tue Sep 9, 2025 at 9:36 AM CEST, Alexandra Winter wrote: > > > On 09.09.25 03:54, Dust Li wrote: >> On 2025-09-05 16:54:16, Alexandra Winter wrote: >>> Create an 'DIBS' shim layer that will provide generic functionality and >>> declarations for dibs device drivers and dibs clients. >>> >>> Following patches will add functionality. >>> >>> Signed-off-by: Alexandra Winter <wintera@xxxxxxxxxxxxx> >>> --- >>> MAINTAINERS | 7 +++++++ >>> include/linux/dibs.h | 42 ++++++++++++++++++++++++++++++++++++++++++ >>> net/Kconfig | 1 + >>> net/Makefile | 1 + >>> net/dibs/Kconfig | 12 ++++++++++++ >>> net/dibs/Makefile | 7 +++++++ >>> net/dibs/dibs_main.c | 37 +++++++++++++++++++++++++++++++++++++ >>> 7 files changed, 107 insertions(+) >>> create mode 100644 include/linux/dibs.h >>> create mode 100644 net/dibs/Kconfig >>> create mode 100644 net/dibs/Makefile >>> create mode 100644 net/dibs/dibs_main.c >> >> I recall we previously discussed the issue of which directory to place >> it in, and I don't have any strong preference regarding this. However, >> I'm not sure whether we reached an agreement on this point. In my >> opinion, placing it under the drivers/ directory seems more reasonable. >> But if net/ is OK, that works for me too. >> >> Best regards, >> Dust >> >> > > You mean like drivers/infiniband that provides sys/class/infiniband? > I don't have any strong feelings about where to place the directory. > Are there any practical consequences? > Other opinions? I agree with Dust. Since we are planning to also have non-networking use-cases, it would be better to place it in drivers/.
