From: "Steve Wise" <swise@opengridcomputing.com>
To: "'David Miller'" <davem@davemloft.net>
Cc: <rajur@chelsio.com>, <dledford@redhat.com>,
<linux-rdma@vger.kernel.org>, <jgg@ziepe.ca>,
<netdev@vger.kernel.org>, <bharat@chelsio.com>,
<ganeshgr@chelsio.com>, <rahul.lakkireddy@chelsio.com>
Subject: RE: interdependencies with cxgb4 and iw_cxgb4
Date: Tue, 20 Mar 2018 10:20:21 -0500 [thread overview]
Message-ID: <3d8001d3c05e$f63bf660$e2b3e320$@opengridcomputing.com> (raw)
In-Reply-To: <20180320.111824.2214262102648467414.davem@davemloft.net>
>
> From: "Steve Wise" <swise@opengridcomputing.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.
prev parent reply other threads:[~2018-03-20 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:31 interdependencies with cxgb4 and iw_cxgb4 Steve Wise
2018-03-16 16:21 ` David Miller
2018-03-19 19:50 ` Steve Wise
2018-03-19 23:34 ` David Miller
2018-03-20 13:47 ` Steve Wise
2018-03-20 14:03 ` Leon Romanovsky
2018-03-20 14:40 ` David Miller
2018-03-20 15:08 ` Steve Wise
2018-03-20 15:18 ` David Miller
2018-03-20 15:20 ` Steve Wise [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='3d8001d3c05e$f63bf660$e2b3e320$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=bharat@chelsio.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=ganeshgr@chelsio.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rajur@chelsio.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.