[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4gmAk=mRCVQCgdSEN9JQ9b+C_u0xug-knZpQmGNL_ywxA@mail.gmail.com>
Date: Mon, 15 Jun 2020 12:40:49 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Vaibhav Jain <vaibhav@...ux.ibm.com>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
"Oliver O'Halloran" <oohall@...il.com>,
Santosh Sivaraj <santosh@...six.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ira Weiny <ira.weiny@...el.com>,
Piotr Maziarz <piotrx.maziarz@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf
On Mon, Jun 15, 2020 at 5:56 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Mon, Jun 15, 2020 at 06:14:03PM +0530, Vaibhav Jain wrote:
> > 'seq_buf' provides a very useful abstraction for writing to a string
> > buffer without needing to worry about it over-flowing. However even
> > though the API has been stable for couple of years now its still not
> > exported to kernel loadable modules limiting its usage.
> >
> > Hence this patch proposes update to 'seq_buf.c' to mark
> > seq_buf_printf() which is part of the seq_buf API to be exported to
> > kernel loadable GPL modules. This symbol will be used in later parts
> > of this patch-set to simplify content creation for a sysfs attribute.
> >
> > Cc: Piotr Maziarz <piotrx.maziarz@...ux.intel.com>
> > Cc: Cezary Rojewski <cezary.rojewski@...el.com>
> > Cc: Christoph Hellwig <hch@...radead.org>
> > Cc: Steven Rostedt <rostedt@...dmis.org>
> > Cc: Borislav Petkov <bp@...en8.de>
> > Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
> > Signed-off-by: Vaibhav Jain <vaibhav@...ux.ibm.com>
> > ---
> > Changelog:
> >
> > v12..v13:
> > * None
> >
> > v11..v12:
> > * None
>
> Can you please resend your patchset once a week like everyone else and
> not flood inboxes with it?
Hi Boris,
I gave Vaibhav some long shot hope that his series could be included
in my libnvdimm pull request for -rc1. Save for a last minute clang
report that I misread as a gcc warning, I likely would have included.
This spin is looking to address the last of the comments I had and
something I would consider for -rc2. So, in this case the resends were
requested by me and I'll take the grumbles on Vaibhav's behalf.
Powered by blists - more mailing lists