public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Woodruff,
	Robert J"
	<robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Tziporet Koren <tziporet-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
	<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
	"linux-rdma
	(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] - Proposal for new process for OFED releases
Date: Thu, 1 Dec 2011 17:22:32 -0700	[thread overview]
Message-ID: <20111202002232.GG7230@obsidianresearch.com> (raw)
In-Reply-To: <382A478CAD40FA4FB46605CF81FE39F40107F9C50F-osO9UTpF0URzLByeVOV5+bfspsVTdybXVpNB7YpNyf8@public.gmane.org>

On Thu, Dec 01, 2011 at 04:13:41PM -0800, Woodruff, Robert J wrote:
> Sean wrote,
> >> - OFED will offer only backports to the distros  (no fixes)
> > I think this point needs to be clarified - at least to me anyway. :)
> 
> What this means is that the OFED code base will be identical to what
> is included in the upstream kernel and libs. 
> OFED will provide only backports to allow that 
> code to be run on other kernels.
> 
> If people find a bug or want a new feature, they need to submit the
> patch for the bug or new code upstream and have it accepted there
> before it will go into any OFED release.
> 
> We may need some other way for people to try out experimental new
> feature/code that is not upstream, but we won't include any
> non-upstream code in the production OFED release.
> 
> Hope this helps clarify the proposal.

This is what many of us, including myself, have been asking OFED to be
for some time now. I hope the EWG adopts this proposal.

FWIW, I think it would be ideal if code that is thought important
enough to flow into OFED is also marked for the kernel.org stable
series. This increases the chance important work is brought into the
disto kernel updates quickly.

I think it would be fairly simple for vendors looking to beta features
to provide that via their own packaging, possibly derived from OFED,
pretty much exactly as we've seen to date anyhow.

Non-upstreamable features like SDP could be split into separate
packaging, and built after the appropriate OFED/distro headers are
setup.

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-12-02  0:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcywYuukNsUYemDYTNKYAFgsoWs2mw==>
2011-12-01 19:53 ` [RFC] – Proposal for new process for OFED releases Tziporet Koren
     [not found]   ` <CD250C48050CFB4D95E78C95F2FDDD6E237661EA-fViJhHBwANKuSA5JZHE7gA@public.gmane.org>
2011-12-02  0:04     ` Hefty, Sean
     [not found]       ` <1828884A29C6694DAF28B7E6B8A8237323FC20F5-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-12-02  0:13         ` [RFC] - " Woodruff, Robert J
     [not found]           ` <382A478CAD40FA4FB46605CF81FE39F40107F9C50F-osO9UTpF0URzLByeVOV5+bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-12-02  0:22             ` Jason Gunthorpe [this message]
2011-12-02  7:06         ` [RFC] – " Bart Van Assche
     [not found]           ` <CAO+b5-pDHQ3m18V7hFbqLxnf3-D+E3==R09+jHzAjEhNMJDzKA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-02 18:12             ` Christoph Lameter
     [not found]               ` <alpine.DEB.2.00.1112021211520.13405-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2011-12-02 18:35                 ` Bart Van Assche
2011-12-05  7:05         ` Or Gerlitz
     [not found]           ` <4EDC6D4A.7060407-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-12-06 15:16             ` Steve Wise
2011-12-06 18:59             ` Roland Dreier
2011-12-02 18:15     ` Christoph Lameter
2011-12-05 20:02     ` [ewg] " Doug Ledford
2011-12-23 10:40     ` Bart Van Assche

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=20111202002232.GG7230@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=tziporet-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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