public inbox for linux-nvdimm@lists.01.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>, 914348@bugs.debian.org
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] daxctl: link against libndctl, in case its use doesn't get pruned
Date: Fri, 2 Aug 2019 20:36:51 +0200	[thread overview]
Message-ID: <20190802183651.GA3797@angband.pl> (raw)
In-Reply-To: <47f7555596eae0f7daef0d6a0a9ce0bae96f6af4.camel@intel.com>

On Fri, Aug 02, 2019 at 05:15:21PM +0000, Verma, Vishal L wrote:
> On Thu, 2019-08-01 at 03:00 +0200, Adam Borowski wrote:
> > util/json.c uses libndctl symbols, and is included by daxctl.  These
> > functions should then get pruned as unused, but on some platforms the
> > toolchain fails to do so.

> > this has been requested in https://bugs.debian.org/914348

> Thanks for the report and the patch - however, historically, we've
> avoided linking from daxctl to libndctl.
> 
> I think we can still avoid this by moving the libndctl users in
> util/json.c and util/filter.c into respective ndctl/util/ files.
> 
> The same goes for libdaxctl users in those files - they move into
> daxctl/util/
> 
> I think that would be a cleaner approach, and I can take a shot at
> making the split next week, however we're close to a v66 release, and it
> will have to be after that happens.
> 
> Perhaps the debian package can temporarily carry your patch for the
> archs that fail?

Sounds like a plan.

CCing the bug.  Breno: could you please take this patch for v65 or v66,
until it gets done a better (but more intrusive) way?


喵!
-- 
⢀⣴⠾⠻⢶⣦⠀ Latin:   meow 4 characters, 4 columns,  4 bytes
⣾⠁⢠⠒⠀⣿⡁ Greek:   μεου 4 characters, 4 columns,  8 bytes
⢿⡄⠘⠷⠚⠋  Runes:   ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes
⠈⠳⣄⠀⠀⠀⠀ Chinese: 喵   1 character,  2 columns,  3 bytes <-- best!
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      reply	other threads:[~2019-08-02 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01  1:00 [PATCH] daxctl: link against libndctl, in case its use doesn't get pruned Adam Borowski
2019-08-02 17:15 ` Verma, Vishal L
2019-08-02 18:36   ` Adam Borowski [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=20190802183651.GA3797@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=914348@bugs.debian.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox