From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "dave@stgolabs.net" <dave@stgolabs.net>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality
Date: Wed, 26 Apr 2023 22:01:10 +0000 [thread overview]
Message-ID: <5c61fcd5b226b12abc5f22104a6034f60173363e.camel@intel.com> (raw)
In-Reply-To: <qfnmbur5kofs6tyje7e4xyui6jyifv4lt3oyydre5n2z5igzsm@wgwqdb4hbazf>
On Wed, 2023-04-26 at 11:25 -0700, Davidlohr Bueso wrote:
> On Wed, 26 Apr 2023, Verma, Vishal L wrote:
>
> > These mostly look good - just one thing about the symbol script
> > additions in both this patch and the next one - The different LIBCXL_N
> > sections in this correspond to a library release, and are used for
> > libtool versioning.
> >
> > New symbols in a new release all go together in a new section in this
> > file. e.g. the pending branch has a 'LIBCXL_5' section for symbols
> > going in the v77 release (corresponding to kernel v6.3). Assuming these
> > patches are targeting v78 / v6.4, its new symbols should go in a new
> > LIBCXL_6 section.
>
> I really have no specific version of ndctl in mind here, and for the kernel
> I'm "targeting" v6.5, so no hurry with this. It was mostly have the cxl
> tool support there for whenever the kernel bits landed (plus recycle testing
> to exercise the sysfs poll(2) support).
>
> Would it make sense for you to update the libcxl.sym file for whenever you
> pick this up? If so I can just get rid of the entries in a v2.
Ah right - agreed on 6.5 as I think that's the target for mw-update as
well, 6.4 stuff is already 'frozen'.
Don't remove the .sym entries - I think the build might even complain -
but it is a safe bet to base on the last released version (v76), and
then just add a new section for your entries. And I can fix up the
inevitable merge-conflicts arising from this (which happens pretty
frequently for these anyway).
>
> Thanks,
> Davidlohr
next prev parent reply other threads:[~2023-04-26 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 1:59 [PATCH -ndctl 0/2] cxl: Support memdev sanitation Davidlohr Bueso
2023-04-23 1:59 ` [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality Davidlohr Bueso
2023-04-26 18:19 ` Verma, Vishal L
2023-04-26 18:25 ` Davidlohr Bueso
2023-04-26 22:01 ` Verma, Vishal L [this message]
2023-04-23 1:59 ` [PATCH 2/2] cxl/memdev: Introduce sanitize-memdev functionality Davidlohr Bueso
2023-04-25 15:52 ` Davidlohr Bueso
-- strict thread matches above, loose matches on Subject: below --
2023-07-13 19:54 [PATCH -ndctl v2 0/2] cxl: Support memdev sanitation Davidlohr Bueso
2023-07-13 19:54 ` [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality Davidlohr Bueso
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=5c61fcd5b226b12abc5f22104a6034f60173363e.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.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