From: Leon Romanovsky <leon@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Doug Ledford <dledford@redhat.com>
Subject: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Wed, 7 Sep 2016 08:03:02 +0300 [thread overview]
Message-ID: <CALq1K=L7MWcQVCbQE+QzjMxuUbhwXk=65_T30UThuvaKDo2V-A@mail.gmail.com> (raw)
Hi,
Sorry for my late reply to this thread and I hope that it is not too
late to join this topic.
We are in RDMA subsystem in the process of unifying our user-space
parts of RDMA stack to be similar in structure and schedules to
kernel. There is over all consensus that current kernel maintainer
(Doug Ledford) will take responsibility of this meta-bundle [1]
(initial stage, WIP).
However, in the last year, we saw increasing interest in RDMA
technology and steady stream of new drivers and features, including
ABI redesign. The next year is expecting to be more challenging, so it
is vital to us to rethink our maintainership model, before everything
collapse :).
We (me and Doug, if he didn't register to this yet) would be very
interesting to join and discuss different models to manage RDMA stack.
Thanks
[1] https://github.com/jgunthorpe/rdma-plumbing/
next reply other threads:[~2016-09-07 5:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 5:03 Leon Romanovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-20 12:11 Daniel Vetter
2016-07-22 20:02 ` Darren Hart
2016-07-25 5:57 ` Daniel Vetter
2016-07-26 16:22 ` Darren Hart
2016-07-28 22:13 ` Bjorn Helgaas
2016-07-26 16:45 ` Olof Johansson
2016-07-27 3:04 ` Vinod Koul
2016-07-27 5:34 ` Wolfram Sang
2016-07-27 7:53 ` Arnd Bergmann
2016-07-27 12:57 ` Vinod Koul
2016-07-27 14:22 ` Mark Brown
2016-07-27 17:15 ` Vinod Koul
2016-07-28 8:44 ` Arnd Bergmann
2016-07-28 23:48 ` Alexandre Belloni
2016-07-29 0:06 ` Stephen Rothwell
2016-07-31 17:57 ` Vinod Koul
2016-08-01 6:56 ` Arnd Bergmann
2016-08-01 7:36 ` Laurent Pinchart
2016-08-01 14:10 ` Arnd Bergmann
2016-08-02 4:46 ` Vinod Koul
2016-08-02 6:48 ` Peter Ujfalusi
2016-08-02 7:27 ` Arnd Bergmann
2016-08-02 8:29 ` Peter Ujfalusi
2016-08-02 8:33 ` Laurent Pinchart
2016-08-02 9:49 ` Tony Lindgren
2016-08-02 8:41 ` Russell King - ARM Linux
2016-08-02 9:21 ` Laurent Pinchart
2016-08-02 9:27 ` Russell King - ARM Linux
2016-09-02 10:46 ` Vinod Koul
2016-09-02 17:25 ` Linus Torvalds
2016-09-02 20:06 ` Arnd Bergmann
2016-09-02 20:26 ` Linus Torvalds
2016-09-02 20:43 ` Julia Lawall
2016-09-02 20:50 ` Linus Torvalds
2016-09-02 22:16 ` Benjamin Herrenschmidt
2016-09-03 14:02 ` Michael Ellerman
2016-09-02 23:35 ` Arnd Bergmann
2016-09-04 17:45 ` Geert Uytterhoeven
2016-09-04 17:59 ` Linus Torvalds
2016-09-03 0:07 ` Mark Brown
2016-07-27 12:59 ` Daniel Vetter
2016-07-27 13:03 ` Daniel Vetter
2016-08-01 14:42 ` Jani Nikula
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='CALq1K=L7MWcQVCbQE+QzjMxuUbhwXk=65_T30UThuvaKDo2V-A@mail.gmail.com' \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox