Re: [PATCH 05/18] docs: core-api: add cachetlb documentation

Hi Jani, On Tue, May 08, 2018 at 05:40:56PM +0300, Jani Nikula wrote: > On Mon, 07 May 2018, Andrea Parri wrote: > > On Mon, May 07, 2018 at 06:35:41AM -0300, Mauro Carvalho Chehab wrote: > >> The cachetlb.txt is already in ReST format. So, move it to the > >>

Re: [PATCH 04/18] docs: admin-guide: add bcache documentation

On Mon, 7 May 2018 06:35:40 -0300 Mauro Carvalho Chehab wrote: > The bcache.txt is already in ReST format. So, move it to the > admin guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab Applied, thanks. jon -- To

Re: [PATCH 03/18] docs: */index.rst: Add newer documents to their respective index.rst

On Mon, 7 May 2018 06:35:39 -0300 Mauro Carvalho Chehab wrote: > A number of new docs were added, but they're currently not on > the index.rst from the session they're supposed to be, causing > Sphinx warnings. > > Add them. > > Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH 06/18] docs: core-api: add cgroup-v2 documentation

On Mon, 7 May 2018 06:35:42 -0300 Mauro Carvalho Chehab wrote: > The cgroup-v2.txt is already in ReST format. So, move it to the > core-api guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab Honestly, this seems to me

Re: [PATCH 02/18] docs: fix location of request_firmware & friends

On Mon, May 07, 2018 at 06:35:38AM -0300, Mauro Carvalho Chehab wrote: > commit 5d6d1ddd2730 ("firmware: move firmware loader into its own directory") > and other commits renamed the old firmware_class.c file and split it > into separate files, but documentation was not changed accordingly, >

Re: [PATCH 0/3] docs/vm: move numa_memory_policy.rst to admin-guide/mm

On Tue, 8 May 2018 10:02:07 +0300 Mike Rapoport wrote: > These patches include minor formatting and spelling updates to > Documentation/vm/numa_memory_policy.rst and move this file to > Documentation/admin-guide/mm. Set applied - thanks! jon -- To unsubscribe from

Re: coresight: documentation: update sysfs section

On 7 May 2018 at 16:29, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got

Re: [RFC PATCH v3 0/6] Documentation/features: Provide and apply 'features-refresh.sh'

On Mon, 7 May 2018 12:43:37 +0200 Andrea Parri wrote: > This series provides the script 'features-refresh.sh', which operates on > the arch support status files, and it applies this script to refresh the > status files in place; previous discussions about this

Re: [PATCH] Documentation: block: cmdline-partition.txt fixes and additions

On Sun, 6 May 2018 11:50:29 -0700 Randy Dunlap wrote: > Make the description of the kernel command line option "blkdevparts" > a bit more flowing and readable. > > Fix a few typos. > Add the optional and suffixes. > Note that size can be "-" to indicate all of the

Re: [PATCH] vfio: fix documentation

On Mon, 7 May 2018 11:02:10 +0800 "dongbo (E)" wrote: > Update vfio_add_group_dev description to match the current API. > > Signed-off-by: Dong Bo Applied, thanks. jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body

[PATCH] Documentation/admin-guide/pm/intel_pstate: fix Active Mode w/o HWP paragraph

P-state selection algorithm (powersave or performance) is selected by echoing the desired choice to scaling_governor sysfs attribute and not to scaling_cur_freq (as currently stated). Fix it. Signed-off-by: Juri Lelli Cc: Jonathan Corbet Cc: "Rafael J.

Re: [PATCH 4/6] mm, arm64: untag user addresses in mm/gup.c

On Wed, May 02, 2018 at 07:25:17PM +0200, Andrey Konovalov wrote: > On Wed, May 2, 2018 at 5:36 PM, Kirill A. Shutemov > wrote: > > On Wed, May 02, 2018 at 02:38:42PM +, Andrey Konovalov wrote: > >> > Does having a tagged address here makes any difference? I

Re: [PATCH] doc: botching-up-ioctls: Make it clearer why structs must be padded

On Wed, 2 May 2018 09:51:06 +0200 Daniel Vetter wrote: > This came up in discussions when reviewing drm patches. Applied, thanks. > Aside: I wonder whether we shouldn't move this to some other place and > rst-ify it? Any good suggestions? For the moment, probably in

Re: [PATCH 05/18] docs: core-api: add cachetlb documentation

On Mon, 07 May 2018, Andrea Parri wrote: > On Mon, May 07, 2018 at 06:35:41AM -0300, Mauro Carvalho Chehab wrote: >> The cachetlb.txt is already in ReST format. So, move it to the >> core-api guide, where it belongs. >> >> Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH 18/18] w1: w1_io.c: fix a kernel-doc warning

Hi 07.05.2018, 12:36, "Mauro Carvalho Chehab" : > Add a blank line to avoid this Sphinx warning: > ./drivers/w1/w1_io.c:197: WARNING: Definition list ends without a > blank line; unexpected unindent. > > Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

Hi Masami, On 05/07/2018 09:26 PM, Masami Hiramatsu wrote: > On Mon, 7 May 2018 13:51:21 +0530 > Ravi Bangoria wrote: > >> Hi Masami, >> >> On 05/04/2018 07:51 PM, Ravi Bangoria wrote: > +} > + > +static void sdt_increment_ref_ctr(struct trace_uprobe *tu)

Re: [PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

Masami Hiramatsu wrote: On Mon, 7 May 2018 13:51:21 +0530 Ravi Bangoria wrote: BTW, same issue exists for normal uprobe. If uprobe_mmap() fails, there is no feedback to trace_uprobe and no warnigns in dmesg as well !! There was a patch by Naveen to warn such

[PATCH 1/3] docs/vm: numa_memory_policy: formatting and spelling updates

Signed-off-by: Mike Rapoport --- Documentation/vm/numa_memory_policy.rst | 24 +--- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/Documentation/vm/numa_memory_policy.rst b/Documentation/vm/numa_memory_policy.rst index

[PATCH 0/3] docs/vm: move numa_memory_policy.rst to admin-guide/mm

Hi, These patches include minor formatting and spelling updates to Documentation/vm/numa_memory_policy.rst and move this file to Documentation/admin-guide/mm. Mike Rapoport (3): docs/vm: numa_memory_policy: formatting and spelling updates docs/vm: numa_memory_policy: s/Linux memory

[PATCH 3/3] docs/vm: move numa_memory_policy.rst to Documentation/admin-guide/mm

The document describes userspace API and as such it belongs to Documentation/admin-guide/mm Signed-off-by: Mike Rapoport --- Documentation/admin-guide/mm/hugetlbpage.rst| 2 +- Documentation/admin-guide/mm/index.rst | 1 +

[PATCH 2/3] docs/vm: numa_memory_policy: s/Linux memory policy/NUMA memory policy/

The document describes NUMA memory policy and as it is a part of the Linux documentation it's obvious that this is Linux memory policy. Besides, "Linux memory policy" may refer to other policies, e.g. memory hotplug policy, and using term NUMA makes the documentation less ambiguous.

Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

On Sun, May 6, 2018 at 7:36 PM, Kees Cook wrote: > On Sun, May 6, 2018 at 2:31 PM, Paul Moore wrote: >> On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: >>> Seccomp received improved logging controls in v4.14. Applications can

Re: [PATCH v2 6/7] ocxl: Add an IOCTL so userspace knows what CPU features are available

On Tue, 2018-05-08 at 13:50 +1000, Nicholas Piggin wrote: > On Tue, 08 May 2018 10:41:55 +1000 > "Alastair D'Silva" wrote: > > > On Mon, 2018-05-07 at 20:14 +0200, Frederic Barrat wrote: > > > > > > Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : > > > > From: Alastair

Re: [PATCH v2 6/7] ocxl: Add an IOCTL so userspace knows what CPU features are available

On Tue, 08 May 2018 10:41:55 +1000 "Alastair D'Silva" wrote: > On Mon, 2018-05-07 at 20:14 +0200, Frederic Barrat wrote: > > > > Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : > > > From: Alastair D'Silva > > > > > > In order for a userspace

Re: [PATCH v2 1/7] powerpc: Add TIDR CPU feature for Power9

On Mon, 2018-05-07 at 19:17 +0200, Frederic Barrat wrote: > > Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : > > From: Alastair D'Silva > > > > This patch adds a CPU feature bit to show whether the CPU has > > the TIDR register available, enabling as_notify/wait in

Re: [PATCH 03/18] docs: */index.rst: Add newer documents to their respective index.rst

On Mon, May 07, 2018 at 06:35:39AM -0300, Mauro Carvalho Chehab wrote: > A number of new docs were added, but they're currently not on > the index.rst from the session they're supposed to be, causing > Sphinx warnings. > > Add them. > > Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH 08/18] docs: driver-api: add clk documentation

On Mon, May 07, 2018 at 06:35:44AM -0300, Mauro Carvalho Chehab wrote: > The clk.rst is already in ReST format. So, move it to the > driver-api guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab Reviewed-by: Greg Kroah-Hartman

Re: [PATCH 02/18] docs: fix location of request_firmware & friends

On Mon, May 07, 2018 at 06:35:38AM -0300, Mauro Carvalho Chehab wrote: > commit 5d6d1ddd2730 ("firmware: move firmware loader into its own directory") > and other commits renamed the old firmware_class.c file and split it > into separate files, but documentation was not changed accordingly, >

Re: [PATCH 17/18] docs: uio-howto.rst: use a code block to solve a warning

On Mon, May 07, 2018 at 06:35:53AM -0300, Mauro Carvalho Chehab wrote: > /devel/v4l/docs/Documentation/driver-api/uio-howto.rst:715: WARNING: > Unexpected indentation. > > Signed-off-by: Mauro Carvalho Chehab Reviewed-by: Greg Kroah-Hartman

Re: [PATCH v2 6/7] ocxl: Add an IOCTL so userspace knows what CPU features are available

On Mon, 2018-05-07 at 20:14 +0200, Frederic Barrat wrote: > > Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : > > From: Alastair D'Silva > > > > In order for a userspace AFU driver to call the Power9 specific > > OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can

Re: [PATCH v2 3/7] powerpc: use task_pid_nr() for TID allocation

On Mon, 2018-05-07 at 19:37 +0200, Frederic Barrat wrote: > > Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : > > From: Alastair D'Silva > > > > The current implementation of TID allocation, using a global IDR, > > may > > result in an errant process starving the system

Re: [PATCH v7 3/5] cpuset: Add a root-only cpus.isolated v2 control file

On 05/02/2018 10:08 AM, Peter Zijlstra wrote: > On Thu, Apr 19, 2018 at 09:47:02AM -0400, Waiman Long wrote: >> diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt >> index c970bd7..8d89dc2 100644 >> --- a/Documentation/cgroup-v2.txt >> +++ b/Documentation/cgroup-v2.txt >> @@

Re: [PATCH v7 3/4] ipc: Allow boot time extension of IPCMNI from 32k to 2M

On 05/07/2018 07:17 PM, Luis R. Rodriguez wrote: > On Mon, May 07, 2018 at 04:59:11PM -0400, Waiman Long wrote: >> diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c >> index 49f9bf4..d62335f 100644 >> --- a/ipc/ipc_sysctl.c >> +++ b/ipc/ipc_sysctl.c >> @@ -120,7 +120,8 @@ static int

Re: [PATCH v7 1/4] ipc: IPCMNI limit check for msgmni and shmmni

On 05/07/2018 06:39 PM, Luis R. Rodriguez wrote: > On Mon, May 07, 2018 at 04:59:09PM -0400, Waiman Long wrote: >> A user can write arbitrary integer values to msgmni and shmmni sysctl >> parameters without getting error, but the actual limit is really >> IPCMNI (32k). This can mislead users as

Re: [PATCH v7 3/4] ipc: Allow boot time extension of IPCMNI from 32k to 2M

On Mon, May 07, 2018 at 04:59:11PM -0400, Waiman Long wrote: > diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c > index 49f9bf4..d62335f 100644 > --- a/ipc/ipc_sysctl.c > +++ b/ipc/ipc_sysctl.c > @@ -120,7 +120,8 @@ static int proc_ipc_sem_dointvec(struct ctl_table *table, > int write, > static

Re: [PATCH v7 1/4] ipc: IPCMNI limit check for msgmni and shmmni

On Mon, May 07, 2018 at 04:59:09PM -0400, Waiman Long wrote: > A user can write arbitrary integer values to msgmni and shmmni sysctl > parameters without getting error, but the actual limit is really > IPCMNI (32k). This can mislead users as they think they can get a > value that is not real. > >

coresight: documentation: update sysfs section

- Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management

[PATCH v7 2/4] ipc: IPCMNI limit check for semmni

For SysV semaphores, the semmni value is the last part of the 4-element sem number array. To make semmni behave in a similar way to msgmni and shmmni, we can't directly use the _minmax handler. Instead, a special sem specific handler is added to check the last argument to make sure that it is

[PATCH v7 1/4] ipc: IPCMNI limit check for msgmni and shmmni

A user can write arbitrary integer values to msgmni and shmmni sysctl parameters without getting error, but the actual limit is really IPCMNI (32k). This can mislead users as they think they can get a value that is not real. The right limits are now set for msgmni and shmmni so that the users

[PATCH v7 3/4] ipc: Allow boot time extension of IPCMNI from 32k to 2M

The maximum number of unique System V IPC identifiers was limited to 32k. That limit should be big enough for most use cases. However, there are some users out there requesting for more. To satisfy the need of those users, a new boot time kernel option "ipcmni_extend" is added to extend the

[PATCH v7 4/4] ipc: Conserve sequence numbers in extended IPCMNI mode

The mixing in of a sequence number into the IPC IDs is probably to avoid ID reuse in userspace as much as possible. With extended IPCMNI mode, the number of usable sequence numbers is greatly reduced leading to higher chance of ID reuse. To address this issue, we need to conserve the sequence

[PATCH v7 0/4] ipc: IPCMNI limit check for *mni & increase that limit

v6->v7: - Drop the range clamping code and just return error instead for now until there is user request for clamping support. - Fix compilation error when CONFIG_SYSVIPC_SYSCTL isn't defined. v5->v6: - Consolidate the 3 ctl_table flags into 2. - Make similar changes to

Re: [PATCH v6 0/8] ipc: Clamp *mni to the real IPCMNI limit & increase that limit

On 05/02/2018 11:06 AM, Eric W. Biederman wrote: > >>> and or users that may or may not exist. If you can find something that >>> will care sure. We need to avoid breaking userspace and causing >>> regressions. However as this stands it looks you are making maintenance >>> of the kernel more

Re: [PATCH 01/18] docs: can.rst: fix a footnote reference

+ Robert Schwebel (who thankfully did the txt -> rst conversion for can.txt) On 05/07/2018 11:35 AM, Mauro Carvalho Chehab wrote: > As stated at: > > http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#footnotes > > A footnote should contain either a number, a reference

Re: [PATCH v2 7/7] ocxl: Document new OCXL IOCTLs

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva Signed-off-by: Alastair D'Silva --- Acked-by: Frederic Barrat Fred Documentation/accelerators/ocxl.rst | 11 +++ 1 file

Re: [PATCH v2 6/7] ocxl: Add an IOCTL so userspace knows what CPU features are available

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva In order for a userspace AFU driver to call the Power9 specific OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually make that call. Signed-off-by: Alastair D'Silva

Re: [PATCH v2 5/7] ocxl: Expose the thread_id needed for wait on p9

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU.

Re: [PATCH v2 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva --- Acked-by: Frederic Barrat

Re: [PATCH v2 3/7] powerpc: use task_pid_nr() for TID allocation

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original

Re: [PATCH v2 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva --- Reviewed-by: Frederic Barrat

Re: [PATCH v2 1/7] powerpc: Add TIDR CPU feature for Power9

Le 18/04/2018 à 03:08, Alastair D'Silva a écrit : From: Alastair D'Silva This patch adds a CPU feature bit to show whether the CPU has the TIDR register available, enabling as_notify/wait in userspace. Signed-off-by: Alastair D'Silva ---

Re: [PATCH 15/18] iio: iio.h: use nested struct support on kernel-doc markup

On Mon, 7 May 2018 06:35:51 -0300 Mauro Carvalho Chehab wrote: > Solve those Sphinx warnings: > > ./include/linux/iio/iio.h:270: warning: Function parameter or member > 'scan_type.sign' not described in 'iio_chan_spec' > ./include/linux/iio/iio.h:270:

Re: [PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

On Mon, 7 May 2018 13:51:21 +0530 Ravi Bangoria wrote: > Hi Masami, > > On 05/04/2018 07:51 PM, Ravi Bangoria wrote: > > > >>> +} > >>> + > >>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu) > >>> +{ > >>> + struct uprobe_map_info *info; > >>> + > >>> +

Re: [PATCH] libata: remove ata_sff_data_xfer_noirq()

On 2018-05-07 08:49:08 [-0700], Tejun Heo wrote: > Hello, Sebastian. > > On Fri, May 04, 2018 at 05:06:20PM +0200, Sebastian Andrzej Siewior wrote: > > ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The > > latter is invoked by ata_pio_sector(), atapi_send_cdb() and > >

Re: [PATCH] libata: remove ata_sff_data_xfer_noirq()

Hello, Sebastian. On Fri, May 04, 2018 at 05:06:20PM +0200, Sebastian Andrzej Siewior wrote: > ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The > latter is invoked by ata_pio_sector(), atapi_send_cdb() and > __atapi_pio_bytes() which in turn is invoked by ata_sff_hsm_move().

[PATCH] certificate handling: Update references to the documentation

Commit 94e980cc45f2b2 ("Documentation/module-signing.txt: convert to ReST markup") converted the .txt doc. to ReST markup, but it did not update the references to the doc. (including in MAINTAINERS). Signed-off-by: Andrea Parri --- MAINTAINERS | 2 +-

Re: [PATCH 10/18] rcu: rcupdate.h: get rid of Sphinx warnings at rcu_pointer_handoff()

On Mon, May 07, 2018 at 06:35:46AM -0300, Mauro Carvalho Chehab wrote: > The code example at rcupdate.h currently produce lots of warnings: > > ./include/linux/rcupdate.h:572: WARNING: Unexpected indentation. > ./include/linux/rcupdate.h:576: WARNING: Unexpected indentation. >

Re: [PATCH 09/18] net: mac80211.h: fix a bad comment line

On Mon, 2018-05-07 at 15:37 +0300, Kalle Valo wrote: > Mauro Carvalho Chehab writes: > > > Sphinx produces a lot of errors like this: > > ./include/net/mac80211.h:2083: warning: bad line: > > > > > Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH 09/18] net: mac80211.h: fix a bad comment line

Mauro Carvalho Chehab writes: > Sphinx produces a lot of errors like this: > ./include/net/mac80211.h:2083: warning: bad line: > > > Signed-off-by: Mauro Carvalho Chehab Randy already submitted a similar patch:

Re: [PATCH 07/18] docs: core-api: add circular-buffers documentation

On Mon, May 07, 2018 at 06:35:43AM -0300, Mauro Carvalho Chehab wrote: > The circular-buffers.txt is already in ReST format. So, move it to the > core-api guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab > --- > Documentation/00-INDEX

Re: [PATCH 05/18] docs: core-api: add cachetlb documentation

On Mon, May 07, 2018 at 06:35:41AM -0300, Mauro Carvalho Chehab wrote: > The cachetlb.txt is already in ReST format. So, move it to the > core-api guide, where it belongs. > > Signed-off-by: Mauro Carvalho Chehab > --- > Documentation/00-INDEX

Re: [PATCH 16/18] mtd: rawnand.h: use nested union kernel-doc markups

Hi Boris, Em Mon, 7 May 2018 11:46:50 +0200 Boris Brezillon escreveu: > Hi Mauro, > > diff --git a/include/linux/mtd/rawnand.h b/include/linux/mtd/rawnand.h > > index 5dad59b31244..b986f94906df 100644 > > --- a/include/linux/mtd/rawnand.h > > +++

[RFC PATCH v3 1/6] Documentation/features: Add script that refreshes the arch support status files in place

Provides the script: Documentation/features/scripts/features-refresh.sh which operates on the arch-support.txt files and refreshes them in place. This way [1], "[...] we soft- decouple the refreshing of the entries from the introduction of the features, while still making it all

[RFC PATCH v3 4/6] Documentation/features/locking: Use '!RWSEM_GENERIC_SPINLOCK' as Kconfig for 'rwsem-optimized'

Uses '!RWSEM_GENERIC_SPINLOCK' in place of 'Optimized asm/rwsem.h' as Kconfig for 'rwsem-optimized': the new Kconfig expresses this feature equivalently, while also enabling the script 'features-refresh.sh' to operate on the corresponding arch support status file. Also refreshes the status matrix

[RFC PATCH v3 2/6] Documentation/features: Refresh the arch support status files in place

Now that the script 'features-refresh.sh' is available, uses this script to refresh all the arch-support.txt files in place. Signed-off-by: Andrea Parri Cc: Ingo Molnar Cc: Jonathan Corbet Cc: Andrew Morton

[RFC PATCH v3 3/6] Documentation/features/core: Add arch support status files for 'cBPF-JIT' and 'eBPF-JIT'

Commit 606b5908e split 'HAVE_BPF_JIT' into cBPF and eBPF variant. Adds arch support status files for the new variants, and removes the status file corresponding to 'HAVE_BPT_JIT'. The new status matrices were auto-generated using the script 'features-refresh.sh'. Signed-off-by: Andrea Parri

[RFC PATCH v3 5/6] Documentation/features/lib: Remove arch support status file for 'strncasecmp'

Suggested-by: Ingo Molnar Signed-off-by: Andrea Parri Cc: Ingo Molnar Cc: Jonathan Corbet Cc: Andrew Morton --- .../features/lib/strncasecmp/arch-support.txt | 33

[RFC PATCH v3 6/6] Documentation/features/vm: Remove arch support status file for 'pte_special'

Suggested-by: Ingo Molnar Signed-off-by: Andrea Parri Cc: Ingo Molnar Cc: Jonathan Corbet Cc: Andrew Morton --- .../features/vm/pte_special/arch-support.txt | 33

[RFC PATCH v3 0/6] Documentation/features: Provide and apply 'features-refresh.sh'

Hi, This series provides the script 'features-refresh.sh', which operates on the arch support status files, and it applies this script to refresh the status files in place; previous discussions about this series are at [1]. The series is organized as follows. - Patch 1/6 adds the script to

Re: [PATCH 16/18] mtd: rawnand.h: use nested union kernel-doc markups

Hi Mauro, On Mon, 7 May 2018 06:35:52 -0300 Mauro Carvalho Chehab wrote: > Gets rid of those warnings and better document the parameters. > > ./include/linux/mtd/rawnand.h:752: warning: Function parameter or member > 'timings.sdr' not described in

[PATCH 04/18] docs: admin-guide: add bcache documentation

The bcache.txt is already in ReST format. So, move it to the admin guide, where it belongs. Signed-off-by: Mauro Carvalho Chehab --- Documentation/00-INDEX | 2 -- Documentation/{bcache.txt => admin-guide/bcache.rst} | 0

[PATCH 06/18] docs: core-api: add cgroup-v2 documentation

The cgroup-v2.txt is already in ReST format. So, move it to the core-api guide, where it belongs. Signed-off-by: Mauro Carvalho Chehab --- Documentation/00-INDEX | 2 -- Documentation/{cgroup-v2.txt => admin-guide/cgroup-v2.rst} |

[PATCH 08/18] docs: driver-api: add clk documentation

The clk.rst is already in ReST format. So, move it to the driver-api guide, where it belongs. Signed-off-by: Mauro Carvalho Chehab --- Documentation/00-INDEX | 2 -- Documentation/admin-guide/kernel-parameters.txt | 2 +-

[PATCH 12/18] time: timer.c: adjust a kernel-doc comment

Those three warnings can easily solved by using :: to indicate a code block: ./kernel/time/timer.c:1259: WARNING: Unexpected indentation. ./kernel/time/timer.c:1261: WARNING: Unexpected indentation. ./kernel/time/timer.c:1262: WARNING: Block quote ends without a blank

[PATCH 03/18] docs: */index.rst: Add newer documents to their respective index.rst

A number of new docs were added, but they're currently not on the index.rst from the session they're supposed to be, causing Sphinx warnings. Add them. Signed-off-by: Mauro Carvalho Chehab --- Documentation/crypto/index.rst | 1 +

[PATCH 05/18] docs: core-api: add cachetlb documentation

The cachetlb.txt is already in ReST format. So, move it to the core-api guide, where it belongs. Signed-off-by: Mauro Carvalho Chehab --- Documentation/00-INDEX| 2 -- Documentation/{cachetlb.txt => core-api/cachetlb.rst} | 0

[PATCH 02/18] docs: fix location of request_firmware & friends

commit 5d6d1ddd2730 ("firmware: move firmware loader into its own directory") and other commits renamed the old firmware_class.c file and split it into separate files, but documentation was not changed accordingly, causing Sphinx errors. Change the location accordingly at the documentation files.

[PATCH 14/18] fbdev: modedb.c: fix a kernel-doc markup

Use code blocks to avoid those warnings and make it look nicer. ./drivers/video/fbdev/core/modedb.c:647: WARNING: Inline strong start-string without end-string. ./drivers/video/fbdev/core/modedb.c:647: WARNING: Inline strong start-string without end-string.

[PATCH 01/18] docs: can.rst: fix a footnote reference

As stated at: http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#footnotes A footnote should contain either a number, a reference or an auto number, e. g.: [1], [#f1] or [#]. While using [*] accidentaly works for html, it fails for other document outputs. In

[PATCH 17/18] docs: uio-howto.rst: use a code block to solve a warning

/devel/v4l/docs/Documentation/driver-api/uio-howto.rst:715: WARNING: Unexpected indentation. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/uio-howto.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 07/18] docs: core-api: add circular-buffers documentation

The circular-buffers.txt is already in ReST format. So, move it to the core-api guide, where it belongs. Signed-off-by: Mauro Carvalho Chehab --- Documentation/00-INDEX | 2 -- .../{circular-buffers.txt =>

[PATCH 16/18] mtd: rawnand.h: use nested union kernel-doc markups

Gets rid of those warnings and better document the parameters. ./include/linux/mtd/rawnand.h:752: warning: Function parameter or member 'timings.sdr' not described in 'nand_data_interface' ./include/linux/mtd/rawnand.h:817: warning: Function parameter or member 'buf' not described in

[PATCH 11/18] docs: crypto_engine.rst: Fix two parse warnings

./Documentation/crypto/crypto_engine.rst:13: WARNING: Unexpected indentation. ./Documentation/crypto/crypto_engine.rst:15: WARNING: Block quote ends without a blank line; unexpected unindent. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 18/18] w1: w1_io.c: fix a kernel-doc warning

Add a blank line to avoid this Sphinx warning: ./drivers/w1/w1_io.c:197: WARNING: Definition list ends without a blank line; unexpected unindent. Signed-off-by: Mauro Carvalho Chehab --- drivers/w1/w1_io.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 09/18] net: mac80211.h: fix a bad comment line

Sphinx produces a lot of errors like this: ./include/net/mac80211.h:2083: warning: bad line: > Signed-off-by: Mauro Carvalho Chehab --- include/net/mac80211.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/net/mac80211.h

[PATCH 13/18] wait: wait.h: Get rid of a kernel-doc/Sphinx warnings

The flow diagram should be inside a code-block to avoid those warnings: ./include/linux/wait.h:110: WARNING: Block quote ends without a blank line; unexpected unindent. ./include/linux/wait.h:113: WARNING: Unexpected indentation. ./include/linux/wait.h:115: WARNING: Block

[PATCH 00/18] Fix some build warnings/errors with Sphinx

I decided to give a try with Sphinx last stable version (1.17.4), and noticed several issues. The worse one was with the networking book: a non-standard footnote there with [*] instead of a number causes it to break PDF building. So, I took some spare time to address some warnings all over the

[PATCH 10/18] rcu: rcupdate.h: get rid of Sphinx warnings at rcu_pointer_handoff()

The code example at rcupdate.h currently produce lots of warnings: ./include/linux/rcupdate.h:572: WARNING: Unexpected indentation. ./include/linux/rcupdate.h:576: WARNING: Unexpected indentation. ./include/linux/rcupdate.h:580: WARNING: Block quote ends without a blank

Re: [PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

Hi Masami, On 05/04/2018 07:51 PM, Ravi Bangoria wrote: > >>> +} >>> + >>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu) >>> +{ >>> + struct uprobe_map_info *info; >>> + >>> + uprobe_down_write_dup_mmap(); >>> + info = uprobe_build_map_info(tu->inode->i_mapping, >>> +

Re: [PATCH] vfio: fix documentation

On Mon, 7 May 2018 11:02:10 +0800 "dongbo (E)" wrote: > From: Dong Bo > > Update vfio_add_group_dev description to match the current API. > > Signed-off-by: Dong Bo > --- > Documentation/vfio.txt | 5 ++--- > 1 file changed, 2

Re: [PATCH] VFIO: Fix Documentation

Hi, Alex. On 2018/5/1 2:38, Alex Williamson wrote: > On Fri, 20 Apr 2018 18:07:27 +0800 > "dongbo (E)" wrote: > >> From: Dong Bo >> >> Signed-off-by: Dong Bo >> --- > > Hi Dong Bo, > > The patch is corrupted, please resend and also

[PATCH] vfio: fix documentation

From: Dong Bo Update vfio_add_group_dev description to match the current API. Signed-off-by: Dong Bo --- Documentation/vfio.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt

RE: [PATCH] Documentation: block: cmdline-partition.txt fixes and additions

> -Original Message- > From: Randy Dunlap [mailto:rdun...@infradead.org] > Sent: Monday, May 07, 2018 2:50 AM > To: linux-bl...@vger.kernel.org; axboe > Cc: LKML ; Caizhiyong > ; Andrew Morton

Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

On Sun, May 6, 2018 at 2:31 PM, Paul Moore wrote: > On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: >> Seccomp received improved logging controls in v4.14. Applications can opt >> into >> logging of "handled" actions (SECCOMP_RET_TRAP,

Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: > Seccomp received improved logging controls in v4.14. Applications can opt into > logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, > SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading

[PATCH] Documentation: block: cmdline-partition.txt fixes and additions

From: Randy Dunlap Make the description of the kernel command line option "blkdevparts" a bit more flowing and readable. Fix a few typos. Add the optional and suffixes. Note that size can be "-" to indicate all of the remaining space. Signed-off-by: Randy Dunlap

Wohltätigkeitsspende in Höhe von € 2.000.000,00

Lieber Freund, Ich bin Herr Richard Wahl der Mega-Gewinner von $ 533M In Mega Millions Jackpot spende ich an 5 zufällige Personen, wenn Sie diese E-Mail erhalten, dann wurde Ihre E-Mail nach einem Spinball ausgewählt. Ich habe den größten Teil meines Vermögens auf eine Reihe von

Re: [PATCH] Documentation: refcount-vs-atomic: Update reference to LKMM doc.

On Fri, May 04, 2018 at 02:13:59PM -0700, Kees Cook wrote: > On Fri, May 4, 2018 at 2:11 PM, Andrea Parri > wrote: > > The LKMM project has moved to 'tools/memory-model/'. > > > > Signed-off-by: Andrea Parri > > --- > >

Re: [PATCH] Documentation: refcount-vs-atomic: Update reference to LKMM doc.

On Fri, May 4, 2018 at 2:11 PM, Andrea Parri wrote: > The LKMM project has moved to 'tools/memory-model/'. > > Signed-off-by: Andrea Parri > --- > Documentation/core-api/refcount-vs-atomic.rst | 2 +- > 1 file changed, 1

[PATCH] Documentation: refcount-vs-atomic: Update reference to LKMM doc.

The LKMM project has moved to 'tools/memory-model/'. Signed-off-by: Andrea Parri --- Documentation/core-api/refcount-vs-atomic.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/core-api/refcount-vs-atomic.rst

<    3   4   5   6   7   8   9   10   11   12   >