netdev - RE: interdependencies with cxgb4 and iw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 20 Mar 2018 10:20:21 -0500
From:   "Steve Wise" <swise@...ngridcomputing.com>
To:     "'David Miller'" <davem@...emloft.net>
Cc:     <rajur@...lsio.com>, <dledford@...hat.com>,
        <linux-rdma@...r.kernel.org>, <jgg@...pe.ca>,
        <netdev@...r.kernel.org>, <bharat@...lsio.com>,
        <ganeshgr@...lsio.com>, <rahul.lakkireddy@...lsio.com>
Subject: RE: interdependencies with cxgb4 and iw_cxgb4

> 
> From: "Steve Wise" <swise@...ngridcomputing.com>
> Date: Tue, 20 Mar 2018 10:08:44 -0500
> 
> > For the maintainers, yes.  But it avoids setting up k.o accounts and
> > git repos for each device driver maintainer that has this issue.
> 
> I think this is quite a reasonable requirement for submitters wishing
> to make significant changes across two subsystems with complex
> interdependencies.
> 
> It is critical to get the changes tested in both the RDMA and net-next
> tree contexts as early as possible, and to shake out any intergration
> issues (which happens transparently via linux-next).
> 
> I know it's easy to see the personal "burdon" it causes you as an
> individual developer, but you really have to consider how much is
> in-flight and being dealt with by maintainers of very active
> subsystems like the networking.
> 
> Thank you.

Fair enough.  Thanks Dave.