On 14/1/19 5:12 pm, Joel Stanley wrote:
This shows up in the index of https://www.kernel.org/doc/html/latest/ so
I figured it should be updated.
Fixes: bfeffd15528 ("Linux 5.0-rc1")
Signed-off-by: Joel Stanley
--
We could also remove the version number instead of applying this patch.
You miss
A small patchset to update the verbs API documentation with some
information regarding the ioctl syscall. First patch converts the
file format to ReST, since this is the new preferred format. 2nd
patch links this file to the main index so we can actually find
it by browsing (search will work in any
Replace the existing Documentation/infiniband/user_verbs.txt with
Documentation/infiniband/user_verbs.rst. No substantial changes to
the content - just some minor reformatting to have the rendering
come out nicely.
This is in preparation for updating the content in a subsequent
patch.
Signed-off-b
Link the previously converted Documentation/infiniband/user_verbs.rst
to the main index by creating a new subsystem (Infiniband) under the
root document. This manifests as a new section under "Kernel API
Documentation" in the index.html, as well as a new section in the
table of contents pane.
This
It is important to understand the existing framework when implementing
a new verb. The majority of existing API functions are implemented using
the write syscall, but this has been superceded by the ioctl syscall
for new commands. This patch updates the documentation regarding how
to go about imple
On Mon, Jan 14, 2019 at 09:52:14AM +0800, lijiang wrote:
> I would like to remove this variable and post again.
No, you should remove the vmcoreinfo export too:
kernel/crash_core.c:398:VMCOREINFO_OSRELEASE(init_uts_ns.name.release);
after making sure userspace is not using it and *then*
On Mon, Jan 14, 2019 at 01:30:30PM +0800, lijiang wrote:
> I noticed that the checkpatch was coded in Perl. But i am not familiar with
> the Perl program language, that would be beyond my ability to do this, i have
> to learn the Perl program language step by step. :-)
You could give it a try - it
svn commit 231296 matches commit d29e939c63b71 ("Add fuzzing coverage
support") in the gcc git. The change is part of gcc 6.1.0.
Replace the svn commit number with a gcc version which everyone can
easily compare.
Signed-off-by: Sebastian Andrzej Siewior
---
Documentation/dev-tools/kcov.rst | 2
On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> +/*
> + * psi_update_work represents slowpath accounting part while
> + * psi_group_change represents hotpath part.
> + * There are two potential races between these path:
> + * 1. Changes to group->polling when slowpath checks f
Hi Rafael,
sorry for the delay.
On 10/01/2019 11:20, Rafael J. Wysocki wrote:
[ ... ]
>>> if (entered_state >= 0) {
>>> + s64 diff, delay = drv->states[entered_state].exit_latency;
>>> + int i;
>>> +
>>> /*
>>>* Update cpuidle counte
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
>
> This commit adds PECI client driver.
It looks like it's a PECI driver for the three CPU families, and it
implements cpu and dimm temp, with sideband functions deferred to the
future. If you add that information with a few more words it would
ma
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
>
> This commit adds hwmon documents for PECI cputemp and dimmtemp drivers.
>
> Cc: Guenter Roeck
> Cc: Jean Delvare
> Cc: Jonathan Corbet
> Cc: Jason M Biils
> Cc: Randy Dunlap
> Signed-off-by: Jae Hyun Yoo
> Reviewed-by: Haiyue Wang
> Revie
Mention that when a part of a slab cache might be exported to the
userspace, the cache should be created using kmem_cache_create_usercopy()
Signed-off-by: Mike Rapoport
---
Documentation/core-api/memory-allocation.rst | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Do
Fix "reference to nonexisting document" warnings.
Fixes: b255e500c8dc ("net: documentation: build a directory structure
for drivers")
Signed-off-by: Otto Sabart
---
Documentation/networking/index.rst | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a
On Sat, Jan 12, 2019 at 02:57:01PM +0800, Changbin Du wrote:
> This patch adds a new trace option 'funcgraph-retval' and is disabled by
> default. When this option is enabled, fgraph tracer will show the return
> value of each function. This is useful to find/analyze a original error
> source in a
On Fri, 11 Jan 2019, Liviu Dudau wrote:
> On Thu, Jan 03, 2019 at 05:44:26PM -0300, Ezequiel Garcia wrote:
>> Hi Liviu,
>>
>> On Mon, 2018-12-03 at 11:31 +, Ayan Halder wrote:
>> > From: Brian Starkey
>> >
>> > AFBC is a flexible, proprietary, lossless compression protocol and
>> > format,
Hi Jani,
On Mon, Jan 14, 2019 at 02:23:46PM +0200, Jani Nikula wrote:
> On Fri, 11 Jan 2019, Liviu Dudau wrote:
> > On Thu, Jan 03, 2019 at 05:44:26PM -0300, Ezequiel Garcia wrote:
> >> Hi Liviu,
> >>
> >> On Mon, 2018-12-03 at 11:31 +, Ayan Halder wrote:
> >> > From: Brian Starkey
> >> >
On Mon, 14 Jan 2019, Brian Starkey wrote:
> AFBC is a relatively well-established name, whereas arm-fbc is not a
> term anyone will be familiar with.
First time I ever heard of AFBC. ;)
> We could name the file "arm-afbc.rst", though I am slightly against
> namespacing it that way for the reason
On Sat, 12 Jan 2019 12:05:33 +0800
Changbin Du wrote:
> Hi Steven, Have you checked this serias yet? :)
>
Not yet, I'll try to do it today.
-- Steve
On Sun, 13 Jan 2019 19:28:58 -0800
Randy Dunlap wrote:
> Fix Sphinx warning in coding-style.rst:
>
> Documentation/process/coding-style.rst:446: WARNING: Inline interpreted text
> or phrase reference start-string without end-string.
>
> Signed-off-by: Randy Dunlap
Applied, thanks.
jon
On Sun, 13 Jan 2019 19:21:46 -0800
Randy Dunlap wrote:
> Fix Sphinx warnings in ibmvmc.rst, add an index.rst file in
> Documentation/misc-devices/, and insert that index file into the
> top-level index file.
>
> Documentation/misc-devices/ibmvmc.rst:2: WARNING: Explicit markup ends
> without a
On Mon, Jan 14, 2019 at 12:11:56PM +, Mark Rutland wrote:
> On Sat, Jan 12, 2019 at 02:57:01PM +0800, Changbin Du wrote:
> > This patch adds a new trace option 'funcgraph-retval' and is disabled by
> > default. When this option is enabled, fgraph tracer will show the return
> > value of each fu
On Sat, 12 Jan 2019 14:57:01 +0800
Changbin Du wrote:
> This patch adds a new trace option 'funcgraph-retval' and is disabled by
> default. When this option is enabled, fgraph tracer will show the return
> value of each function. This is useful to find/analyze a original error
> source in a call
On Mon, Jan 14, 2019 at 11:00:50AM +0200, Joel Nider wrote:
> Link the previously converted Documentation/infiniband/user_verbs.rst
> to the main index by creating a new subsystem (Infiniband) under the
> root document. This manifests as a new section under "Kernel API
> Documentation" in the index
On Mon, Jan 14, 2019 at 11:00:49AM +0200, Joel Nider wrote:
> Replace the existing Documentation/infiniband/user_verbs.txt with
> Documentation/infiniband/user_verbs.rst. No substantial changes to
> the content - just some minor reformatting to have the rendering
> come out nicely.
> This is in pre
On Fri, Jan 11, 2019 at 07:29:40AM -1000, Joey Pabalinas wrote:
> On Thu, Jan 10, 2019 at 11:48:13PM +, Jason Gunthorpe wrote:
> > There has been some confusion since checkpatch started warning about bool
> > use in structures, and people have been avoiding using it.
> >
> > Many people feel t
On Sun, Jan 13, 2019 at 08:49:36AM -0800, Matthew Wilcox wrote:
> On Thu, Jan 10, 2019 at 11:48:13PM +, Jason Gunthorpe wrote:
> > +The Linux kernel bool type is an alias for the C99 _Bool type. bool values
> > can
> > +only evaluate to 0 or 1, and implicit or explicit conversion to bool
> > +
On Sun, Jan 13, 2019 at 05:01:39PM +0100, Federico Vaga wrote:
> > -17) Don't re-invent the kernel macros
> > +17) Using bool
> > +--
> > +
> > +The Linux kernel bool type is an alias for the C99 _Bool type. bool
> > values can
> > +only evaluate to 0 or 1, and implicit or explicit con
On Mon, 14 Jan 2019 09:56:21 -0700
Jason Gunthorpe wrote:
> > Documentation/infiniband/user_verbs.rst | 70
> > +
> > Documentation/infiniband/user_verbs.txt | 69
> >
> > 2 files changed, 70 insertions(+), 69 deletions(-)
> > c
On 1/11/2019 7:33 AM, Borislav Petkov wrote:
> On Thu, Jan 10, 2019 at 08:19:43PM +0800, Lianbo Jiang wrote:
>> +init_uts_ns.name.release
>> +
>> +
>> +The version of the Linux kernel. Used to find the corresponding source
>> +code from which the kernel has been built.
>> +
On Mon, Jan 14, 2019 at 05:48:48PM +, Kazuhito Hagio wrote:
> As for makedumpfile, it will be not impossible to remove the
> init_uts_ns.name.relase (OSRELEASE), but some fixes are needed.
> Because historically OSRELEASE has been a kind of a mandatory entry
> in vmcoreinfo from the beginning o
Fix the mismatch between "Useful GFP flag combinations" section naming in
the DOC: section in include/linux/gfp.h and
Documentation/core-api/mm-api.rst
Signed-off-by: Mike Rapoport
---
Documentation/core-api/mm-api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documenta
Jonathan Corbet wrote on 01/14/2019 07:34:21 PM:
> From: Jonathan Corbet
> To: Jason Gunthorpe
> Cc: Joel Nider , Leon Romanovsky ,
Doug
> Ledford , Mike Rapoport ,
linux-
> d...@vger.kernel.org, linux-ker...@vger.kernel.org
> Date: 01/14/2019 07:37 PM
> Subject: Re: [PATCH 1/3] docs-rst: in
On Mon, Jan 14, 2019 at 08:52:14PM +0200, Joel Nider wrote:
> > > Jonathan/linux-doc: Can you Ack at least the build system parts of
> > > this please? I can take it through the rdma tree, unless you prefer
> > > otherwise?
> >
> > Can I make a request? This appears to be user-oriented documentat
- Original Message -
> On Mon, Jan 14, 2019 at 05:48:48PM +, Kazuhito Hagio wrote:
> > As for makedumpfile, it will be not impossible to remove the
> > init_uts_ns.name.relase (OSRELEASE), but some fixes are needed.
> > Because historically OSRELEASE has been a kind of a mandatory en
On Mon, Jan 14, 2019 at 01:58:32PM -0500, Dave Anderson wrote:
> Preferably it would be left as-is. The crash utility has a "crash
> --osrelease vmcore"
> option that only looks at the dumpfile header, and just dump the string.
> With respect
> to compressed kdumps, crash could alternatively lo
On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
>
> On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > +/*
> > + * psi_update_work represents slowpath accounting part while
> > + * psi_group_change represents hotpath part.
> > + * There are two potential races between th
- Original Message -
> On Mon, Jan 14, 2019 at 01:58:32PM -0500, Dave Anderson wrote:
> > Preferably it would be left as-is. The crash utility has a "crash
> > --osrelease vmcore"
> > option that only looks at the dumpfile header, and just dump the string.
> > With respect
> > to compr
On Mon, Jan 14, 2019 at 11:30:12AM -0800, Suren Baghdasaryan wrote:
> On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
> >
> > On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > > +/*
> > > + * psi_update_work represents slowpath accounting part while
> > > + * psi_group_
On Mon, Jan 14, 2019 at 02:36:47PM -0500, Dave Anderson wrote:
> There's no reading of the dumpfile's memory involved, and that being the case,
> the vmlinux file is not utilized. That's the whole point of the crash
> option, i.e.,
> taking a vmcore file, and trying to determine what kernel shoul
- Original Message -
> On Mon, Jan 14, 2019 at 02:36:47PM -0500, Dave Anderson wrote:
> > There's no reading of the dumpfile's memory involved, and that being the
> > case,
> > the vmlinux file is not utilized. That's the whole point of the crash
> > option, i.e.,
> > taking a vmcore
On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote:
> That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and
> pulls out the OSRELEASE string from it, so that a user can determine what
> vmlinux file should be used with that vmcore for normal crash analysis.
And th
- Original Message -
> On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote:
> > That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and
> > pulls out the OSRELEASE string from it, so that a user can determine what
> > vmlinux file should be used with that vm
On Mon, Jan 14, 2019 at 03:26:32PM -0500, Dave Anderson wrote:
> No. It needs *both* the vmlinux file and the vmcore file in order to read
> kernel
> virtual memory, so just having a kernel virtual address is insufficient.
>
> So it's a chicken-and-egg situation. This particular --osrelease opt
On Mon, Jan 14, 2019 at 11:42 AM Johannes Weiner wrote:
>
> On Mon, Jan 14, 2019 at 11:30:12AM -0800, Suren Baghdasaryan wrote:
> > On Mon, Jan 14, 2019 at 2:22 AM Peter Zijlstra wrote:
> > >
> > > On Thu, Jan 10, 2019 at 02:07:18PM -0800, Suren Baghdasaryan wrote:
> > > > +/*
> > > > + * psi_upd
- Original Message -
> On Mon, Jan 14, 2019 at 03:26:32PM -0500, Dave Anderson wrote:
> > No. It needs *both* the vmlinux file and the vmcore file in order to read
> > kernel
> > virtual memory, so just having a kernel virtual address is insufficient.
> >
> > So it's a chicken-and-egg
On 01/11/2019 02:52 PM, Thomas Gleixner wrote:
> On Wed, 19 Dec 2018, Waiman Long wrote:
>
>> With the default SPEC_STORE_BYPASS_SECCOMP/SPEC_STORE_BYPASS_PRCTL mode,
>> the TIF_SSBD bit will be inherited when a new task is fork'ed or cloned.
>>
>> As only certain class of applications (like Java)
On 1/14/2019 3:43 AM, Joel Stanley wrote:
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
This commit adds hwmon documents for PECI cputemp and dimmtemp drivers.
Cc: Guenter Roeck
Cc: Jean Delvare
Cc: Jonathan Corbet
Cc: Jason M Biils
Cc: Randy Dunlap
Signed-off-by: Jae Hyun Yoo
Review
On 1/14/2019 3:42 AM, Joel Stanley wrote:
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
This commit adds PECI client driver.
It looks like it's a PECI driver for the three CPU families, and it
implements cpu and dimm temp, with sideband functions deferred to the
future. If you add that in
On Mon, Jan 14, 2019 at 11:39 AM Daniel Lezcano
wrote:
>
>
> Hi Rafael,
>
> sorry for the delay.
>
> On 10/01/2019 11:20, Rafael J. Wysocki wrote:
>
> [ ... ]
>
> >>> if (entered_state >= 0) {
> >>> + s64 diff, delay = drv->states[entered_state].exit_latency;
> >>> +
On Fri, 11 Jan 2019 14:40:59 +0100
Christian Brauner wrote:
> This documents the Android binderfs filesystem used to dynamically add and
> remove binder devices that are private to each instance.
>
> Signed-off-by: Christian Brauner
Two quick notes:
> ---
> /* Changelog */
> v1:
> - switch fr
On Fri, 11 Jan 2019 17:14:10 +0100
Vincent Whitchurch wrote:
> Bits are usually numbered starting from zero, so 4 should be bit 2, not
> bit 3.
>
> Suggested-by: Matthew Wilcox
> Signed-off-by: Vincent Whitchurch
> ---
> Documentation/sysctl/vm.txt | 2 +-
> 1 file changed, 1 insertion(+), 1
On Mon, 14 Jan 2019 11:08:07 +0100
Sebastian Andrzej Siewior wrote:
> svn commit 231296 matches commit d29e939c63b71 ("Add fuzzing coverage
> support") in the gcc git. The change is part of gcc 6.1.0.
>
> Replace the svn commit number with a gcc version which everyone can
> easily compare.
>
>
On Mon, 14 Jan 2019 13:47:34 +0200
Mike Rapoport wrote:
> Mention that when a part of a slab cache might be exported to the
> userspace, the cache should be created using kmem_cache_create_usercopy()
>
> Signed-off-by: Mike Rapoport
Hmm...I didn't know that :)
Applied, thanks.
jon
On Mon, 14 Jan 2019 20:32:58 +0200
Mike Rapoport wrote:
> Fix the mismatch between "Useful GFP flag combinations" section naming in
> the DOC: section in include/linux/gfp.h and
> Documentation/core-api/mm-api.rst
>
> Signed-off-by: Mike Rapoport
> ---
> Documentation/core-api/mm-api.rst | 2 +
On Mon, 14 Jan 2019 09:14:59 +0200
Joel Nider wrote:
> While using this guide to learn the new documentation method, I saw
> a few phrases that I felt could be improved. These small changes
> improve the grammar and choice of words to further enhance the
> installation instructions.
>
> Signed-o
Hi Steven,
On Mon, Jan 14, 2019 at 11:21:15AM -0500, Steven Rostedt wrote:
> On Sat, 12 Jan 2019 14:57:01 +0800
> Changbin Du wrote:
>
> > This patch adds a new trace option 'funcgraph-retval' and is disabled by
> > default. When this option is enabled, fgraph tracer will show the return
> > valu
57 matches
Mail list logo
