Currently these flags are lost in the call
drm_display_mode_from_videomode()
Signed-off-by: Lothar Waßmann
---
drivers/gpu/drm/imx/imx-drm-core.c | 12 +++
drivers/gpu/drm/imx/imx-drm.h | 7 ---
drivers/gpu/drm/imx/imx-ldb.c | 37
Currently these flags are lost in the call
drm_display_mode_from_videomode()
Signed-off-by: Lothar Waßmann
---
drivers/gpu/drm/imx/imx-drm-core.c | 12 +++
drivers/gpu/drm/imx/imx-drm.h | 7 ---
drivers/gpu/drm/imx/imx-ldb.c | 37
This patch allows to select a specific video mode from a list of modes
defined in DT by setting the 'native-mode' property appropriately.
This change does not affect the behaviour of existing platforms, since
they either:
- have just one display-timings subnode
- have the native-mode
Replace the existing macros in "plx9080.h" that define values for the
LBRD0 and LBRD1 registers. Use the prefix `PLX_LBRD_` for macros that
apply to both registers, `PLX_LBRD0_` for macros that apply only to the
LBRD0 register, and `PLX_LBRD1_` for macros that apply only to the LBRD1
register.
The 'de-active' and 'pixelclk-active' DT properties are evaluated
by of_parse_display_timing() called from of_get_drm_display_mode(),
but later lost in the conversion from videomode.flags to
drm_display_mode.flags.
Use an open coded version of of_get_drm_display_mode() to get access
to these
This patch allows to select a specific video mode from a list of modes
defined in DT by setting the 'native-mode' property appropriately.
This change does not affect the behaviour of existing platforms, since
they either:
- have just one display-timings subnode
- have the native-mode
Replace the existing macros in "plx9080.h" that define values for the
LBRD0 and LBRD1 registers. Use the prefix `PLX_LBRD_` for macros that
apply to both registers, `PLX_LBRD0_` for macros that apply only to the
LBRD0 register, and `PLX_LBRD1_` for macros that apply only to the LBRD1
register.
The 'de-active' and 'pixelclk-active' DT properties are evaluated
by of_parse_display_timing() called from of_get_drm_display_mode(),
but later lost in the conversion from videomode.flags to
drm_display_mode.flags.
Use an open coded version of of_get_drm_display_mode() to get access
to these
Replace `enum marb_bits` in "plx9080.h" with a bunch of macros defining
values for the MARBR and DMAARB registers (which are the same
Mode/Arbitation register at two different offsets). Use the prefix
`PLX_MARBR_` for the macros. Make use of the `BIT(x)` and
`GENMASK(h,l)` macros to define the
The 'mode_valid' flag is never set in this driver. Remove it and the
code that depends on it.
Signed-off-by: Lothar Waßmann
---
drivers/gpu/drm/imx/parallel-display.c | 12
1 file changed, 12 deletions(-)
diff --git
Replace `enum marb_bits` in "plx9080.h" with a bunch of macros defining
values for the MARBR and DMAARB registers (which are the same
Mode/Arbitation register at two different offsets). Use the prefix
`PLX_MARBR_` for the macros. Make use of the `BIT(x)` and
`GENMASK(h,l)` macros to define the
The 'mode_valid' flag is never set in this driver. Remove it and the
code that depends on it.
Signed-off-by: Lothar Waßmann
---
drivers/gpu/drm/imx/parallel-display.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/imx/parallel-display.c
Replace the existing macros in "plx9080.h" that define values for the
DMPBAM register. Use the prefix `PLX_DMPBAM_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
DMPBAM register. Use the prefix `PLX_DMPBAM_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 48
For the PLX PCI 9080, the read-only PCIHIDR register is hard-coded with
the value `0x908010b5`. Add a macro `PLX_PCIHIDR_9080` that expands to
this value.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 3 +++
1 file changed, 3 insertions(+)
diff
Replace the existing macros in "plx9080.h" that define values for the
DMAMODE0 and DMAMODE1 registers. Use the prefix `PLX_DMAMODE_` for the
macros. Make use of the `BIT(x)` and `GENMASK(h,l)` macros to define
the values.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
INTCSR register. Use the prefix `PLX_INTCSR_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
CNTRL register. Use the prefix `PLX_CNTRL_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
Replace `enum bigend_bits` in "plx9080.h" with a bunch of macros
defining values for the BIGEND register. Use the prefix `PLX_BIGEND_`
for the macro names. Make use of the `BIT(x)` and `GENMASK(h,l)` macros
to define the values.
Signed-off-by: Ian Abbott
---
For the PLX PCI 9080, the read-only PCIHIDR register is hard-coded with
the value `0x908010b5`. Add a macro `PLX_PCIHIDR_9080` that expands to
this value.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 3 +++
1 file changed, 3 insertions(+)
diff --git
Replace the existing macros in "plx9080.h" that define values for the
DMAMODE0 and DMAMODE1 registers. Use the prefix `PLX_DMAMODE_` for the
macros. Make use of the `BIT(x)` and `GENMASK(h,l)` macros to define
the values.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
INTCSR register. Use the prefix `PLX_INTCSR_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/cb_pcidas64.c | 14 +++--
Replace the existing macros in "plx9080.h" that define values for the
CNTRL register. Use the prefix `PLX_CNTRL_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/cb_pcidas64.c | 31
Replace `enum bigend_bits` in "plx9080.h" with a bunch of macros
defining values for the BIGEND register. Use the prefix `PLX_BIGEND_`
for the macro names. Make use of the `BIT(x)` and `GENMASK(h,l)` macros
to define the values.
Signed-off-by: Ian Abbott
---
Add macros in "plx9080.h" that define values for the DMATHR register
values. Use the prefix `PLX_DMATHR_` for the macros. Make use of the
`BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 41
Add macros in "plx9080.h" that define values for the DMATHR register
values. Use the prefix `PLX_DMATHR_` for the macros. Make use of the
`BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 41
Add `#include` lines to declare stuff used by "plx9080.h" itself.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/staging/comedi/drivers/plx9080.h
Use the usual block comment style and remove some excess spaces from
single-line comments. Remove some obvious stuff about register offsets
being zero relative. Remove some text about the original history of the
file, as it bears hardly any resemblance to it now.
Signed-off-by: Ian Abbott
Replace the existing macros in "plx9080.h" that define values for the
DMACSR0 and DMACSR0 registers. Use the prefix `PLX_DMACSR_` for the
macros. Make use of the `BIT(x)` macro to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/cb_pcidas64.c
Document the DMA descriptor `struct plx_dma_desc`, and the DMA abort
function `plx9080_abort_dma()`.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 35 ++--
1 file changed, 29 insertions(+), 6 deletions(-)
diff --git
Add `#include` lines to declare stuff used by "plx9080.h" itself.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/staging/comedi/drivers/plx9080.h
b/drivers/staging/comedi/drivers/plx9080.h
index
Use the usual block comment style and remove some excess spaces from
single-line comments. Remove some obvious stuff about register offsets
being zero relative. Remove some text about the original history of the
file, as it bears hardly any resemblance to it now.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
DMACSR0 and DMACSR0 registers. Use the prefix `PLX_DMACSR_` for the
macros. Make use of the `BIT(x)` macro to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/cb_pcidas64.c | 22
Document the DMA descriptor `struct plx_dma_desc`, and the DMA abort
function `plx9080_abort_dma()`.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 35 ++--
1 file changed, 29 insertions(+), 6 deletions(-)
diff --git
Replace the existing macros in "plx9080.h" that define values for the
DMCFGA register. Use the prefix `PLX_DMCFGA_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
DMCFGA register. Use the prefix `PLX_DMCFGA_` for the macros. Make use
of the `BIT(x)` and `GENMASK(h,l)` macros to define the values.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/plx9080.h | 29
The defines related to the Power-Up Test Suite (PUTS) are just cruft that
has nothing to do with the PLX PCI-9080 chip. They seem to have been
inherited from "drivers/net/plx9060.h" in the kernel 2.2.16 sources for
use by the "wanxl" driver. Remove them.
Signed-off-by: Ian Abbott
Replace the existing macros in "plx9080.h" that define values for the
DMADPR0 and DMADPR1 registers. (A little-endian version of the register
value is also placed in the `next` member of `struct plx_dma_desc`.)
Use the prefix `PLX_DMADPR_` for the macros. Make use of the `BIT(x)`
and
The defines related to the Power-Up Test Suite (PUTS) are just cruft that
has nothing to do with the PLX PCI-9080 chip. They seem to have been
inherited from "drivers/net/plx9060.h" in the kernel 2.2.16 sources for
use by the "wanxl" driver. Remove them.
Signed-off-by: Ian Abbott
---
Replace the existing macros in "plx9080.h" that define values for the
DMADPR0 and DMADPR1 registers. (A little-endian version of the register
value is also placed in the `next` member of `struct plx_dma_desc`.)
Use the prefix `PLX_DMADPR_` for the macros. Make use of the `BIT(x)`
and
Rename the macros for the PLX PCI 9080 LAS0RR and LAS1RR registers in
"plx9080.h", using the prefix `PLX_LASRR_`. Make use of the `BIT(x)`
and `GENMASK(h,l)` macros to define the values.
Define a macro `PLX_LASRR_PREFETCH` for the "prefetchable memory" bit in
this register, and define a macro
Re-do "drivers/staging/comedi/drivers/plx9080.h". It mostly contains
defines for register offsets and values for the PLX PCI 9080 PCI
interface chip. To make it easier to follow, base the macro names for
register offsets on the register names from the PLX PCI 9080 data book.
Base the macro names
Re-do "drivers/staging/comedi/drivers/plx9080.h". It mostly contains
defines for register offsets and values for the PLX PCI 9080 PCI
interface chip. To make it easier to follow, base the macro names for
register offsets on the register names from the PLX PCI 9080 data book.
Base the macro names
Rename the macros for the PLX PCI 9080 LAS0RR and LAS1RR registers in
"plx9080.h", using the prefix `PLX_LASRR_`. Make use of the `BIT(x)`
and `GENMASK(h,l)` macros to define the values.
Define a macro `PLX_LASRR_PREFETCH` for the "prefetchable memory" bit in
this register, and define a macro
On Fri, May 20, 2016 at 06:51:20PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user_nul to duplicate a memory region from user-space
> to kernel-space and terminate with a NULL, instead of open coding
> using kmalloc + copy_from_user and explicitly NULL terminating.
>
> Signed-off-by:
On Fri, May 20, 2016 at 06:51:20PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user_nul to duplicate a memory region from user-space
> to kernel-space and terminate with a NULL, instead of open coding
> using kmalloc + copy_from_user and explicitly NULL terminating.
>
> Signed-off-by:
On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
> On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote:
> >
> > Please explain. How does that express DRP but prefered master?
>
> Sorry but I'm not sure what you mean here. If the port is capable of
> being used as dual role port
On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
> On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote:
> >
> > Please explain. How does that express DRP but prefered master?
>
> Sorry but I'm not sure what you mean here. If the port is capable of
> being used as dual role port
Crude conversion. This one doesn't use kernel-doc.
Signed-off-by: Jani Nikula
---
Documentation/index.rst | 5 +-
Documentation/kernel-hacking.rst | 795 +++
2 files changed, 799 insertions(+), 1 deletion(-)
create mode
Crude conversion. This one doesn't use kernel-doc.
Signed-off-by: Jani Nikula
---
Documentation/index.rst | 5 +-
Documentation/kernel-hacking.rst | 795 +++
2 files changed, 799 insertions(+), 1 deletion(-)
create mode 100644
From: Peter Enderborg
When sending data the socket allocates memory for
payload on a cache or a page alloc. The page alloc
then might trigger compation that takes long time.
This can be avoided with smaller chunks. But
userspace can not know what is the right
From: Peter Enderborg
When sending data the socket allocates memory for
payload on a cache or a page alloc. The page alloc
then might trigger compation that takes long time.
This can be avoided with smaller chunks. But
userspace can not know what is the right size for
the smaller sends. For
On Friday 20 May 2016 07:02 PM, Jon Hunter wrote:
On 20/05/16 12:59, Laxman Dewangan wrote:
+/* tegra_io_pads_config_info: Tegra IO pads bit config info.
+ * @dpd_config_bit: DPD configuration bit position. -1 if not supported.
+ * @voltage_config_bit: Voltage configuration bit position. -1 if
On Friday 20 May 2016 07:02 PM, Jon Hunter wrote:
On 20/05/16 12:59, Laxman Dewangan wrote:
+/* tegra_io_pads_config_info: Tegra IO pads bit config info.
+ * @dpd_config_bit: DPD configuration bit position. -1 if not supported.
+ * @voltage_config_bit: Voltage configuration bit position. -1 if
On Fri, May 20, 2016 at 06:38:33AM -0700, Andi Kleen wrote:
> > > @@ -82,6 +87,12 @@ void perf_stat__reset_shadow_stats(void)
> > > sizeof(runtime_transaction_stats));
> > > memset(runtime_elision_stats, 0, sizeof(runtime_elision_stats));
> > > memset(_nsecs_stats, 0,
On Fri, May 20, 2016 at 06:38:33AM -0700, Andi Kleen wrote:
> > > @@ -82,6 +87,12 @@ void perf_stat__reset_shadow_stats(void)
> > > sizeof(runtime_transaction_stats));
> > > memset(runtime_elision_stats, 0, sizeof(runtime_elision_stats));
> > > memset(_nsecs_stats, 0,
Here's an updated patch without the extra line
---
Implement the TopDown formulas in perf stat. The topdown basic metrics
reported by the kernel are collected, and the formulas are computed
and output as normal metrics.
See the kernel commit exporting the events for details on the used
metrics.
Here's an updated patch without the extra line
---
Implement the TopDown formulas in perf stat. The topdown basic metrics
reported by the kernel are collected, and the formulas are computed
and output as normal metrics.
See the kernel commit exporting the events for details on the used
metrics.
The Sphinx output directory is generated.
Signed-off-by: Jani Nikula
---
Documentation/.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 Documentation/.gitignore
diff --git a/Documentation/.gitignore b/Documentation/.gitignore
new file mode 100644
The Sphinx output directory is generated.
Signed-off-by: Jani Nikula
---
Documentation/.gitignore | 1 +
1 file changed, 1 insertion(+)
create mode 100644 Documentation/.gitignore
diff --git a/Documentation/.gitignore b/Documentation/.gitignore
new file mode 100644
index
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be
Tell Sphinx where to find the extension, and pass on the kernel src tree
and kernel-doc paths to the extension.
With this, any .rst files under Documentation may contain the kernel-doc
rst directive to include kernel-doc documentation from any source file.
While building, it may be handy to pass
Tell Sphinx where to find the extension, and pass on the kernel src tree
and kernel-doc paths to the extension.
With this, any .rst files under Documentation may contain the kernel-doc
rst directive to include kernel-doc documentation from any source file.
While building, it may be handy to pass
Add an extension to handle kernel-doc directives, to call kernel-doc
according to the arguments and parameters given to the reStructuredText
directive.
The syntax for the kernel-doc directive is:
.. kernel-doc:: FILENAME
:export:
:internal:
:functions: FUNCTION [FUNCTION ...]
:doc:
Crude conversion. This one uses kernel-doc.
Signed-off-by: Jani Nikula
---
Documentation/index.rst | 1 +
Documentation/kernel-api.rst | 419 +++
2 files changed, 420 insertions(+)
create mode 100644
Add an extension to handle kernel-doc directives, to call kernel-doc
according to the arguments and parameters given to the reStructuredText
directive.
The syntax for the kernel-doc directive is:
.. kernel-doc:: FILENAME
:export:
:internal:
:functions: FUNCTION [FUNCTION ...]
:doc:
Crude conversion. This one uses kernel-doc.
Signed-off-by: Jani Nikula
---
Documentation/index.rst | 1 +
Documentation/kernel-api.rst | 419 +++
2 files changed, 420 insertions(+)
create mode 100644 Documentation/kernel-api.rst
diff --git
From: Jonathan Corbet
This script uses pandoc to convert existing DocBook template files to RST
templates. A couple of sed scripts are need to massage things both before
and after the conversion, but the result is then usable with no hand
editing.
[Jani: Change usage to tmplcvt
From: Jonathan Corbet
This script uses pandoc to convert existing DocBook template files to RST
templates. A couple of sed scripts are need to massage things both before
and after the conversion, but the result is then usable with no hand
editing.
[Jani: Change usage to tmplcvt . Fix escaping
Hi Jon, all -
I've had a few moments of spare time to look into Sphinx. This is a sort
of status report on the progress.
I suppose we all thought it would be easiest to use docproc for the
Sphinx toolchain, for starters. I tried it, hard, and even sent a bunch
of docproc prep patches. However I
Currently we use docproc to figure out which symbols are exported, and
then docproc calls kernel-doc on specific functions, to get
documentation on exported functions. According to git blame and docproc
comments, this is due to historical reasons, as functions and their
corresponding
Hi Jon, all -
I've had a few moments of spare time to look into Sphinx. This is a sort
of status report on the progress.
I suppose we all thought it would be easiest to use docproc for the
Sphinx toolchain, for starters. I tried it, hard, and even sent a bunch
of docproc prep patches. However I
Currently we use docproc to figure out which symbols are exported, and
then docproc calls kernel-doc on specific functions, to get
documentation on exported functions. According to git blame and docproc
comments, this is due to historical reasons, as functions and their
corresponding
> > @@ -82,6 +87,12 @@ void perf_stat__reset_shadow_stats(void)
> > sizeof(runtime_transaction_stats));
> > memset(runtime_elision_stats, 0, sizeof(runtime_elision_stats));
> > memset(_nsecs_stats, 0, sizeof(walltime_nsecs_stats));
> > + memset(runtime_topdown_total_slots, 0,
On 20 May 2016 at 13:46, Adrian Hunter wrote:
> On 13/05/16 16:16, Ludovic Desroches wrote:
>> Activating wakeup event is not enough to get a wakeup signal. The
>> corresponding events have to be enabled in the Interrupt Status Enable
>> Register too. It follows the
> > @@ -82,6 +87,12 @@ void perf_stat__reset_shadow_stats(void)
> > sizeof(runtime_transaction_stats));
> > memset(runtime_elision_stats, 0, sizeof(runtime_elision_stats));
> > memset(_nsecs_stats, 0, sizeof(walltime_nsecs_stats));
> > + memset(runtime_topdown_total_slots, 0,
On 20 May 2016 at 13:46, Adrian Hunter wrote:
> On 13/05/16 16:16, Ludovic Desroches wrote:
>> Activating wakeup event is not enough to get a wakeup signal. The
>> corresponding events have to be enabled in the Interrupt Status Enable
>> Register too. It follows the specification and is needed at
I'm not quite sure why the errors below are happening, but this fixes
them.
Use of uninitialized value in string ne at ./scripts/kernel-doc line 1819,
line 6494.
Use of uninitialized value $_[0] in join or string at ./scripts/kernel-doc line
1759, line 6494.
Signed-off-by: Jani Nikula
I'm not quite sure why the errors below are happening, but this fixes
them.
Use of uninitialized value in string ne at ./scripts/kernel-doc line 1819,
line 6494.
Use of uninitialized value $_[0] in join or string at ./scripts/kernel-doc line
1759, line 6494.
Signed-off-by: Jani Nikula
---
On 20/05/16 12:59, Laxman Dewangan wrote:
> The IO pins of Tegra SoCs are grouped for common control of IO
> interface like setting voltage signal levels and power state of
> the interface. The group is generally referred as IO pads. The
> power state and voltage control of IO pins can be done at
On 20/05/16 12:59, Laxman Dewangan wrote:
> The IO pins of Tegra SoCs are grouped for common control of IO
> interface like setting voltage signal levels and power state of
> the interface. The group is generally referred as IO pads. The
> power state and voltage control of IO pins can be done at
On Fri 20-05-16 15:19:12, Vlastimil Babka wrote:
> On 05/20/2016 03:06 PM, Michal Hocko wrote:
[...]
> > Why don't we need also to count also retries?
>
> We could, but not like you suggest.
>
> > ---
> > diff --git a/mm/migrate.c b/mm/migrate.c
> > index 53ab6398e7a2..ef9c5211ae3c 100644
> >
On Fri 20-05-16 15:19:12, Vlastimil Babka wrote:
> On 05/20/2016 03:06 PM, Michal Hocko wrote:
[...]
> > Why don't we need also to count also retries?
>
> We could, but not like you suggest.
>
> > ---
> > diff --git a/mm/migrate.c b/mm/migrate.c
> > index 53ab6398e7a2..ef9c5211ae3c 100644
> >
Hi Guenter,
> building mips images with a consistent infrastructure is becoming more and
> more difficult.
As the current MIPS binutils maintainer I am sorry to hear about this,
and apologise for the state of affairs. Of course I can't help with any
sins of the past, but at least I can help
Hi Guenter,
> building mips images with a consistent infrastructure is becoming more and
> more difficult.
As the current MIPS binutils maintainer I am sorry to hear about this,
and apologise for the state of affairs. Of course I can't help with any
sins of the past, but at least I can help
Use memdup_user_nul to duplicate a memory region from user-space
to kernel-space and terminate with a NULL, instead of open coding
using kmalloc + copy_from_user and explicitly NULL terminating.
Signed-off-by: Muhammad Falak R Wani
---
drivers/s390/char/keyboard.c | 11
Use memdup_user_nul to duplicate a memory region from user-space
to kernel-space and terminate with a NULL, instead of open coding
using kmalloc + copy_from_user and explicitly NULL terminating.
Signed-off-by: Muhammad Falak R Wani
---
drivers/s390/char/keyboard.c | 11 +++
1 file
On 05/20/2016 03:06 PM, Michal Hocko wrote:
On Thu 19-05-16 15:11:23, David Rientjes wrote:
If page migration fails due to -ENOMEM, nr_failed should still be
incremented for proper statistics.
This was encountered recently when all page migration vmstats showed 0,
and inferred that
On 05/20/2016 03:06 PM, Michal Hocko wrote:
On Thu 19-05-16 15:11:23, David Rientjes wrote:
If page migration fails due to -ENOMEM, nr_failed should still be
incremented for proper statistics.
This was encountered recently when all page migration vmstats showed 0,
and inferred that
You have been chosen to benefit from Bernard Arnault Philanthropic Donation.
Contact him with his Personal Email:: bena12...@qq.com
You have been chosen to benefit from Bernard Arnault Philanthropic Donation.
Contact him with his Personal Email:: bena12...@qq.com
On Fri, May 20, 2016 at 05:52:16PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
>
On Fri, May 20, 2016 at 05:52:16PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
> ---
> drivers/s390/char/keyboard.c | 10
On Thu 19-05-16 15:13:26, Yang Shi wrote:
[...]
> diff --git a/init/main.c b/init/main.c
> index b3c6e36..2075faf 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -606,7 +606,6 @@ asmlinkage __visible void __init start_kernel(void)
> initrd_start = 0;
> }
> #endif
> -
On Thu 19-05-16 15:13:26, Yang Shi wrote:
[...]
> diff --git a/init/main.c b/init/main.c
> index b3c6e36..2075faf 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -606,7 +606,6 @@ asmlinkage __visible void __init start_kernel(void)
> initrd_start = 0;
> }
> #endif
> -
Mauro Carvalho Chehab writes:
> Em Thu, 19 May 2016 16:25:45 +0200
> Richard Weinberger escreveu:
>
>> On Thu, May 19, 2016 at 2:57 PM, Kalle Valo wrote:
>> > (Changed the subject from "Re: [PATCH v6 0/3] auxdisplay:
Mauro Carvalho Chehab writes:
> Em Thu, 19 May 2016 16:25:45 +0200
> Richard Weinberger escreveu:
>
>> On Thu, May 19, 2016 at 2:57 PM, Kalle Valo wrote:
>> > (Changed the subject from "Re: [PATCH v6 0/3] auxdisplay: Introduce
>> > ht16k33 driver")
>> >
>> > Robin van der Gracht writes:
>> >
On 2016/5/20 20:58, Heiko Stuebner wrote:
Am Freitag, 20. Mai 2016, 20:35:53 schrieb Shawn Lin:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
On 2016/5/20 20:58, Heiko Stuebner wrote:
Am Freitag, 20. Mai 2016, 20:35:53 schrieb Shawn Lin:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
701 - 800 of 1358 matches
Mail list logo