linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	RDMA mailing list
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-core] Remove the obsolete libibcm library
Date: Thu, 28 Dec 2017 07:30:29 +0200	[thread overview]
Message-ID: <20171228053029.GO3494@mtr-leonro.local> (raw)
In-Reply-To: <20171227201945.GG25436-uk2M96/98Pc@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Wed, Dec 27, 2017 at 01:19:45PM -0700, Jason Gunthorpe wrote:
> On Mon, Dec 25, 2017 at 02:31:32PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> >
> > The libibcm library was marked as obsolete long time ago,
> > the following patch is first step before removing ucm from
> > the kernel.
>
> I understand the distros will not want to loose libibcm in their
> stable releases.
>
> It might make more sense instead to just not build libibcm by default
> with a cmake option but still keep the sources..

We are not removing it from the stable branches, so if they want to keep it
till last person who used this library dies, they are free to do it.

The disabled build doesn't give much benefit at all. It will be dead code exactly
as now, but without any alert that it is broken. Most possible, it will be broken
till some distro will notice it.

Exactly as some distros have EOL, this libibcm library came to its EOL.

Thanks

>
> Jason

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-12-28  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25 12:31 [PATCH rdma-core] Remove the obsolete libibcm library Leon Romanovsky
     [not found] ` <20171225123132.6063-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-12-27 20:19   ` Jason Gunthorpe
     [not found]     ` <20171227201945.GG25436-uk2M96/98Pc@public.gmane.org>
2017-12-28  5:30       ` Leon Romanovsky [this message]
     [not found]         ` <20171228053029.GO3494-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-02 14:18           ` Hal Rosenstock
     [not found]             ` <ea55cca5-1bf9-dd54-9be1-6450ca9002ef-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2018-01-02 14:26               ` Leon Romanovsky
     [not found]                 ` <20180102142658.GF10145-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-02 14:32                   ` Hal Rosenstock
     [not found]                     ` <3146d449-0d75-9954-8c0b-bb122aaaa102-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2018-01-02 15:10                       ` Leon Romanovsky
2018-01-02 15:04               ` Jason Gunthorpe

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=20171228053029.GO3494@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).