Linux Power Management development
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpupower: Use conventional shared library versioning
Date: Wed, 15 Jun 2016 12:13:33 +0100	[thread overview]
Message-ID: <1465989213.3529.264.camel@decadent.org.uk> (raw)
In-Reply-To: <2753168.d7n2N2ZaIy@skinner>

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

On Wed, 2016-06-15 at 13:03 +0200, Thomas Renninger wrote:
> Hi Ben,
> 
> On Friday, June 10, 2016 02:05:54 AM Ben Hutchings wrote:
> > The current choice of variable names is rather confusing.  LIB_MIN is
> > used for the soname version, which would normally be the *major* part
> > of the version.
> > 
> > - Rename LIB_MAJ (the full version) to LIB_VER and LIB_MIN (the soname
> >   version) to LIB_SONAME_VER
> > - Define LIB_SONAME_VER to be the first component of LIB_VER
> > - Bump the full version to 1.0.0, since the soname version is currently 1
> 
> I am currently working on adding rapl/powercapping things into
> cpupower.
> I will collect/integrate your patches and send them altogether.

The ABI break has already happened, so changing the soname version is a
bug fix that should go into 4.7.  But I agree this second patch doesn't
need to.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-06-15 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10  1:05 [PATCH] cpupower: Use conventional shared library versioning Ben Hutchings
2016-06-15 11:03 ` Thomas Renninger
2016-06-15 11:13   ` Ben Hutchings [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=1465989213.3529.264.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=linux-pm@vger.kernel.org \
    --cc=trenn@suse.de \
    /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