Re: [PATCH v5 2/9] proc/sysctl: Provide additional ctl_table.flags checks

On Mon, Mar 19, 2018 at 11:35:19AM -0400, Waiman Long wrote: > On 03/16/2018 08:54 PM, Luis R. Rodriguez wrote: > > On Fri, Mar 16, 2018 at 02:13:43PM -0400, Waiman Long wrote: > >> Checking code is added to provide the following additional > >> ctl_table.flags checks: > >> > >> 1) No unknown

Re: [PATCH v5 1/9] sysctl: Add flags to support min/max range clamping

On Mon, Mar 19, 2018 at 11:39:19AM -0400, Waiman Long wrote: > On 03/16/2018 09:10 PM, Luis R. Rodriguez wrote: > > On Fri, Mar 16, 2018 at 02:13:42PM -0400, Waiman Long wrote: > >> When the CTL_FLAGS_CLAMP_RANGE flag is set in the ctl_table > >> entry, any update from the userspace will be

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

Andrew, please drop these patches until further notice. I would recommend we avoid merging these patches until we get proper Acked-by for the entire set. Waiman has a bit more work to do and even after the 5th iteration this is not right yet. Luis -- To unsubscribe from this list: send the

Re: [PATCH] docs: kernel-doc: fix parsing of arrays

On Thu, 29 Mar 2018 10:58:59 -0400 Mauro Carvalho Chehab wrote: > The logic with parses array has a bug that prevents it to > parse arrays like: > struct { > ... > struct { > u64 msdu[IEEE80211_NUM_TIDS + 1]; >

Re: [PATCH] Documentation/process: update FUSE project website

On Tue, 27 Mar 2018 14:59:50 +0200 Martin Kepplinger wrote: > According to the old project site, https://sourceforge.net/projects/fuse/ > the project has moved to https://github.com/libfuse/ so we update the > link to point to the latest libfuse release. Applied, thanks. jon

Re: [PATCH 00/32] docs/vm: convert to ReST format

On Wed, 21 Mar 2018 21:22:16 +0200 Mike Rapoport wrote: > These patches convert files in Documentation/vm to ReST format, add an > initial index and link it to the top level documentation. > > There are no contents changes in the documentation, except few spelling >

Re: [PATCH] Documentation/wimax: Point dead link to working copy

On Wed, 28 Mar 2018 22:47:07 +0800 Sanjeev Gupta wrote: > The linuxwimax.org domain, registered by the Linux Foundation, > no longer has any DNS entries. Locate a copy on archive.org and > update the documentation. Hmm...I worry a bit about pointing into archive.org; it's not

Re: [PATCH v5 1/9] sysctl: Add flags to support min/max range clamping

On Thu, Mar 29, 2018 at 02:47:18PM -0400, Waiman Long wrote: > On 03/29/2018 02:15 PM, Luis R. Rodriguez wrote: > > On Mon, Mar 19, 2018 at 11:39:19AM -0400, Waiman Long wrote: > >> On 03/16/2018 09:10 PM, Luis R. Rodriguez wrote: > >>> On Fri, Mar 16, 2018 at 02:13:42PM -0400, Waiman Long wrote:

Re: [PATCH v5 1/9] sysctl: Add flags to support min/max range clamping

On 03/29/2018 02:15 PM, Luis R. Rodriguez wrote: > On Mon, Mar 19, 2018 at 11:39:19AM -0400, Waiman Long wrote: >> On 03/16/2018 09:10 PM, Luis R. Rodriguez wrote: >>> On Fri, Mar 16, 2018 at 02:13:42PM -0400, Waiman Long wrote: When the CTL_FLAGS_CLAMP_RANGE flag is set in the ctl_table

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

On Thu, Mar 29, 2018 at 06:19:35PM +, Luis R. Rodriguez wrote: > Andrew, > > please drop these patches until further notice. I would recommend we avoid > merging > these patches until we get proper Acked-by for the entire set. Waiman has a > bit more > work to do and even after the 5th

nested structs parsing

Hi, For a while I haven't looked at my documentation for 802.11, and now I noticed I'm getting warnings due to the nested parsing. However, something seems to be wrong? I have, for example, this (in net/mac80211/sta_info.h) struct sta_info { ... struct { u64

Re: nested structs parsing

On Thu, 2018-03-29 at 11:46 +0200, Johannes Berg wrote: > Hi, > > For a while I haven't looked at my documentation for 802.11, and now I > noticed I'm getting warnings due to the nested parsing. > > However, something seems to be wrong? I have, for example, this (in > net/mac80211/sta_info.h) >

Re: [PATCH] Documentation/usb: Fix dead links and convert others to https

On Thu, Mar 29, 2018 at 12:07:52AM +0800, Sanjeev Gupta wrote: > All links checked, for those dead, I have replaced with copies on > archive.org. For some, https is not supported, http has been > kept. > > The git log says this was last done by Justin P. Mattock in 2010. > Hi, Justin! Not sure

[lwn:docs-next 73/74] htmldocs: include/net/mac80211.h:950: warning: Function parameter or member 'control.rates' not described in 'ieee80211_tx_info'

tree: git://git.lwn.net/linux-2.6 docs-next head: 86afad7d87f535ebb1a0e978bc32a8c58ac99268 commit: d404d57955a6f67365423f9d0b89ad1881799087 [73/74] docs: kernel-doc: fix parsing of arrays reproduce: make htmldocs All warnings (new ones prefixed by >>): WARNING: convert(1) not found, for

[PATCH v4 5/6] coresight: Set and clear sink device handler for kdump node

If Coresight path is enabled for specific CPU, the sink device handler need to be set to kdump node; on the other hand we also need to clear sink device handler when path is disabled. This patch sets sink devices handler for kdump node for two separate Coresight enabling modes: CS_MODE_SYSFS and

[PATCH v4 2/6] doc: Add documentation for Coresight panic kdump

Add detailed documentation for Coresight panic kdump, which contains the idea for why need Coresight panic kdump and introduce the implementation of Coresight panic kdump framework; the last section is to explain what's usage. Credits to Mathieu Poirier for many suggestions since the first

[PATCH v4 3/6] coresight: Support panic kdump functionality

After kernel panic happens, Coresight tracing data has much useful info which can be used for analysis. For example, the trace info from ETB RAM can be used to check the CPU execution flows before the crash. So we can save the tracing data from sink devices, and rely on kdump to save DDR content

[PATCH v4 6/6] coresight: etm4x: Support panic kdump

ETMv4 hardware information and configuration needs to be saved as metadata; the metadata format should be compatible with 'perf' tool and finally is used by tracing data decoder. ETMv4 works as tracer per CPU, we cannot wait for gathering ETM info after CPU panic has happened in case there have

[PATCH v4 4/6] coresight: tmc: Hook callback for panic kdump

Since Coresight panic kdump functionality has been ready, this patch is to hook panic callback function for ETB/ETF driver. The driver data structure has allocated a buffer when the session started, so simply save tracing data into this buffer when panic happens and update buffer related info for

[PATCH v4 0/6] Coresight: Support panic kdump

This patch set is to explore Coresight tracing data for postmortem debugging. When kernel panic happens, the Coresight panic kdump can help to save on-chip tracing data and tracer metadata into DRAM, later relies on kdump and crash/perf tools to recovery tracing data for "offline" analysis. The

Re: nested structs parsing

Hi, > The original patchset for nested structs was supporting it only > when not inlined. This should be fixed on this patchset: > > https://lkml.org/lkml/2018/2/19/387 > > Do you have those patches on your tree? No, looks like I don't have those yet. I'll wait for those then. > With

Re: [PATCH v4 7/8] clocksource: Add a new timer-ingenic driver

Le mer. 28 mars 2018 à 18:25, Daniel Lezcano a écrit : On 28/03/2018 17:15, Paul Cercueil wrote: Le 2018-03-24 07:26, Daniel Lezcano a écrit : On 18/03/2018 00:29, Paul Cercueil wrote: This driver will use the TCU (Timer Counter Unit) present on the Ingenic

Re: nested structs parsing

Em Thu, 29 Mar 2018 11:47:07 +0200 Johannes Berg escreveu: > On Thu, 2018-03-29 at 11:46 +0200, Johannes Berg wrote: > > Hi, > > > > For a while I haven't looked at my documentation for 802.11, and now I > > noticed I'm getting warnings due to the nested parsing. > >

Re: nested structs parsing

Em Thu, 29 Mar 2018 16:26:33 +0200 Johannes Berg escreveu: > Hi, > > > The original patchset for nested structs was supporting it only > > when not inlined. This should be fixed on this patchset: > > > > https://lkml.org/lkml/2018/2/19/387 > > > > Do you have

[PATCH] docs: kernel-doc: fix parsing of arrays

The logic with parses array has a bug that prevents it to parse arrays like: struct { ... struct { u64 msdu[IEEE80211_NUM_TIDS + 1]; ... ... Fix the parser to accept it. Signed-off-by: Mauro Carvalho Chehab

Re: [PATCH v4 4/8] dt-bindings: Add doc for the Ingenic TCU drivers

Hi Rob, Le mer. 28 mars 2018 à 18:28, Rob Herring a écrit : On Wed, Mar 28, 2018 at 10:33 AM, Paul Cercueil wrote: Le 2018-03-27 16:46, Rob Herring a écrit : On Sun, Mar 18, 2018 at 12:28:57AM +0100, Paul Cercueil wrote: Add documentation about