Enabling the Interrupts before registering the irq handler is a bad
idea. This patch corrects the same for XADC driver.
Signed-off-by: Manish Narani
---
drivers/iio/adc/xilinx-xadc-core.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On 20-Jul 18:23, Suren Baghdasaryan wrote:
> Hi Patrick,
Hi Sure,
thank!
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
[...]
> > @@ -977,13 +991,21 @@ static inline void uclamp_cpu_get_id(struct
> > task_struct *p,
> > uc_grp = >uclamp.group[clamp_id][0];
> >
This patch series resolves code style problems as reported by code analysis
tools.
Changes in v2:
- From the first version of patches, 2 patches are dropped in this
series.
- In the v1 patch set, 1/4 was not required as the issue is in
checkpatch.pl script and
This patch series resolves code style problems as reported by code analysis
tools.
Changes in v2:
- From the first version of patches, 2 patches are dropped in this
series.
- In the v1 patch set, 1/4 was not required as the issue is in
checkpatch.pl script and
This patch avoids getting irq number in xadc_remove function. Instead
store 'irq' in xadc struct and use xadc->irq wherever needed.
This patch also resolves a warning reported by coverity where it asks to
check return value of platform_get_irq() for any errors in xadc_remove.
Signed-off-by:
This patch avoids getting irq number in xadc_remove function. Instead
store 'irq' in xadc struct and use xadc->irq wherever needed.
This patch also resolves a warning reported by coverity where it asks to
check return value of platform_get_irq() for any errors in xadc_remove.
Signed-off-by:
This patch adds check for return values from clock related functions.
This was reported by static code analysis tool.
Signed-off-by: Manish Narani
---
drivers/iio/adc/xilinx-xadc-core.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
This patch adds check for return values from clock related functions.
This was reported by static code analysis tool.
Signed-off-by: Manish Narani
---
drivers/iio/adc/xilinx-xadc-core.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
This patch limits the xadc pcap clock frequency value to be less than
200MHz. This fixes the issue when zynq is booted at higher frequency
values, pcap crosses the maximum limit of 200MHz(Fmax) as it is derived
from IOPLL.
If this limit is crossed it is required to alter the WEDGE and REDGE
bits
This patch limits the xadc pcap clock frequency value to be less than
200MHz. This fixes the issue when zynq is booted at higher frequency
values, pcap crosses the maximum limit of 200MHz(Fmax) as it is derived
from IOPLL.
If this limit is crossed it is required to alter the WEDGE and REDGE
bits
On Mon, Jul 23, 2018 at 04:59:44PM +0200, Peter Zijlstra wrote:
> On Thu, Mar 08, 2018 at 06:15:41PM -0800, kan.li...@linux.intel.com wrote:
> > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> > index ef47a418d819..86149b87cce8 100644
> > ---
On Mon, Jul 23, 2018 at 04:59:44PM +0200, Peter Zijlstra wrote:
> On Thu, Mar 08, 2018 at 06:15:41PM -0800, kan.li...@linux.intel.com wrote:
> > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> > index ef47a418d819..86149b87cce8 100644
> > ---
Signed-off-by: Ivan Bornyakov
---
drivers/staging/gasket/gasket_page_table.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/gasket/gasket_page_table.c
b/drivers/staging/gasket/gasket_page_table.c
index 9f8116112e0a..3ffc8d67ec05 100644
---
Signed-off-by: Ivan Bornyakov
---
drivers/staging/gasket/gasket_page_table.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/gasket/gasket_page_table.c
b/drivers/staging/gasket/gasket_page_table.c
index 9f8116112e0a..3ffc8d67ec05 100644
---
On Mon, 23 Jul 2018 14:25:31 +0200
Dominique Martinet wrote:
> Greg Kurz wrote on Mon, Jul 23, 2018:
> > The patch is quite big and I'm not sure I can find time to review it
> > carefully, but I'll try to help anyway.
>
> No worry, thanks for this already.
>
> > > Sorry for coming back to
On Mon, 23 Jul 2018 14:25:31 +0200
Dominique Martinet wrote:
> Greg Kurz wrote on Mon, Jul 23, 2018:
> > The patch is quite big and I'm not sure I can find time to review it
> > carefully, but I'll try to help anyway.
>
> No worry, thanks for this already.
>
> > > Sorry for coming back to
On Wed, Jun 13, 2018 at 10:45:37AM -0500, Serge Hallyn wrote:
> On Thu, Jun 07, 2018 at 01:43:48PM +0200, Christian Brauner wrote:
> > When running in a container with a user namespace, if you call getxattr
> > with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
> > silently
On Wed, Jun 13, 2018 at 10:45:37AM -0500, Serge Hallyn wrote:
> On Thu, Jun 07, 2018 at 01:43:48PM +0200, Christian Brauner wrote:
> > When running in a container with a user namespace, if you call getxattr
> > with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
> > silently
On Thu, Mar 08, 2018 at 06:15:41PM -0800, kan.li...@linux.intel.com wrote:
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index ef47a418d819..86149b87cce8 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -2280,7 +2280,10 @@ static
On Thu, Mar 08, 2018 at 06:15:41PM -0800, kan.li...@linux.intel.com wrote:
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index ef47a418d819..86149b87cce8 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -2280,7 +2280,10 @@ static
On Sun, 22 Jul 2018 21:00:51 +0200
Marcus Folkesson wrote:
> Hi Jonathan,
>
> Thanks, all good catches.
>
> On Sun, Jul 22, 2018 at 09:08:38AM +0100, Jonathan Cameron wrote:
> > On Sat, 21 Jul 2018 23:19:48 +0200 (CEST)
> > Peter Meerwald-Stadler wrote:
> >
> > > Hello,
> > >
> > > >
On Sun, 22 Jul 2018 21:00:51 +0200
Marcus Folkesson wrote:
> Hi Jonathan,
>
> Thanks, all good catches.
>
> On Sun, Jul 22, 2018 at 09:08:38AM +0100, Jonathan Cameron wrote:
> > On Sat, 21 Jul 2018 23:19:48 +0200 (CEST)
> > Peter Meerwald-Stadler wrote:
> >
> > > Hello,
> > >
> > > >
On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski wrote:
>
>> On Jul 16, 2018, at 6:05 AM, H.J. Lu wrote:
>>
>>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski
>>> wrote:
>>> I'm not at all convinced that this is the problem, but the series here
>>> will give a better diagnostic if the issue
On Fri, Jul 20, 2018 at 2:35 PM, Andy Lutomirski wrote:
>
>> On Jul 16, 2018, at 6:05 AM, H.J. Lu wrote:
>>
>>> On Fri, Jul 13, 2018 at 7:08 PM, Andy Lutomirski
>>> wrote:
>>> I'm not at all convinced that this is the problem, but the series here
>>> will give a better diagnostic if the issue
According to commit [1], dwarf2 unwinder had some issues that prevented the
fault injection stacktrace filter from working on x86-64.
Does anyone know whether this issue still exists 11 years later?
Are there any objections to revert this patch?
Gal
[1] 6d690dcac92a ("fault injection: disable
According to commit [1], dwarf2 unwinder had some issues that prevented the
fault injection stacktrace filter from working on x86-64.
Does anyone know whether this issue still exists 11 years later?
Are there any objections to revert this patch?
Gal
[1] 6d690dcac92a ("fault injection: disable
On 23 July 2018 00:28, Daniel Kurtz wrote:
> Some systems do not have software controllable regulators driving the
> DA7219's supplies, nor can they use device tree to create "always-on fixed
> regulators" to easily pretend like they do.
>
> On these systems the call to devm_regulator_bulk_get()
On 23 July 2018 00:28, Daniel Kurtz wrote:
> Some systems do not have software controllable regulators driving the
> DA7219's supplies, nor can they use device tree to create "always-on fixed
> regulators" to easily pretend like they do.
>
> On these systems the call to devm_regulator_bulk_get()
Stephen Rothwell writes:
> Hi all,
>
> Changes since 20180720:
>
> Dropped trees: xarray, ida (complex conflicts)
>
> The drm-msm tree gained a conflict against the drm tree and a build
> failure due to an interaction with the drm tree for which I added a
> merge fix patch.
>
> The kvm-arm tree
Stephen Rothwell writes:
> Hi all,
>
> Changes since 20180720:
>
> Dropped trees: xarray, ida (complex conflicts)
>
> The drm-msm tree gained a conflict against the drm tree and a build
> failure due to an interaction with the drm tree for which I added a
> merge fix patch.
>
> The kvm-arm tree
On 23-Jul 16:13, Peter Zijlstra wrote:
> On Mon, Jul 23, 2018 at 01:49:46PM +0100, Patrick Bellasi wrote:
> > On 23-Jul 11:49, Peter Zijlstra wrote:
> >
> > [...]
> >
> > > > -void __getparam_dl(struct task_struct *p, struct sched_attr *attr)
> > > > +void __getparam_dl(struct task_struct *p,
On 23-Jul 16:13, Peter Zijlstra wrote:
> On Mon, Jul 23, 2018 at 01:49:46PM +0100, Patrick Bellasi wrote:
> > On 23-Jul 11:49, Peter Zijlstra wrote:
> >
> > [...]
> >
> > > > -void __getparam_dl(struct task_struct *p, struct sched_attr *attr)
> > > > +void __getparam_dl(struct task_struct *p,
HI Kevin
On 07/23/2018 10:12 PM, Kevin Hilman wrote:
> Yixun Lan writes:
>
> [...]
>
>>>
Second, we might like to convert eMMC driver to also use mmc-clkc model.
>>>
>>> IMO, this should be done as part of merging this series. Otherwise, we
>>> have duplicated code for the same thing.
>>
HI Kevin
On 07/23/2018 10:12 PM, Kevin Hilman wrote:
> Yixun Lan writes:
>
> [...]
>
>>>
Second, we might like to convert eMMC driver to also use mmc-clkc model.
>>>
>>> IMO, this should be done as part of merging this series. Otherwise, we
>>> have duplicated code for the same thing.
>>
A few new instructions including direct stores (movdiri and movdir64b)
and user wait (umwait, umonitor, and tpause) and IA32_MWAIT_CONTROL MSR to
control umwait/umonitor/tpause behaviors will be available in Tremont and
other future x86 processors.
This patch set enumerates the instructions, adds
A few new instructions including direct stores (movdiri and movdir64b)
and user wait (umwait, umonitor, and tpause) and IA32_MWAIT_CONTROL MSR to
control umwait/umonitor/tpause behaviors will be available in Tremont and
other future x86 processors.
This patch set enumerates the instructions, adds
UMWAIT or TPAUSE called by user process makes processor to reside in
a light-weight power/performance optimized state (C0.1 state) or an
improved power/performance optimized state (C0.2 state).
IA32_UMWAIT_CONTROL MSR register allows OS to set global maximum umwait
time and disable C0.2 on the
UMWAIT or TPAUSE called by user process makes processor to reside in
a light-weight power/performance optimized state (C0.1 state) or an
improved power/performance optimized state (C0.2 state).
IA32_UMWAIT_CONTROL MSR register allows OS to set global maximum umwait
time and disable C0.2 on the
MOVDIR64B moves 64-bytes as direct-store with 64-bytes write atomicity.
Direct store is implemented by using write combining (WC) for writing
data directly into memory without caching the data.
In low latency offload (e.g. Non-Volatile Memory, etc), MOVDIR64B writes
work descriptors (and data in
User wants to query if direct store instructions are supported and use
the instructions. The vDSO functions provides fast interface for user
to query the support and use the instructions.
movdiri_supported and its alias __vdso_movdiri_supported check if
movdiri instructions are supported.
MOVDIR64B moves 64-bytes as direct-store with 64-bytes write atomicity.
Direct store is implemented by using write combining (WC) for writing
data directly into memory without caching the data.
In low latency offload (e.g. Non-Volatile Memory, etc), MOVDIR64B writes
work descriptors (and data in
User wants to query if direct store instructions are supported and use
the instructions. The vDSO functions provides fast interface for user
to query the support and use the instructions.
movdiri_supported and its alias __vdso_movdiri_supported check if
movdiri instructions are supported.
The selftest tool tests the vDSO functions for calling the instructions
including movdiri32, movdiri64, movdir64b, umonitor, umwait, tpause,
and their support checking.
Limited by testing environment, the selftest doesn't contain some
complex tests e.g. wake up process by writing the monitor
The selftest tool tests the vDSO functions for calling the instructions
including movdiri32, movdiri64, movdir64b, umonitor, umwait, tpause,
and their support checking.
Limited by testing environment, the selftest doesn't contain some
complex tests e.g. wake up process by writing the monitor
User wants to query if user wait instructions (umonitor, umwait, and
tpause) are supported and use the instructions. The vDSO functions
provides fast interface for user to check the support and use the
instructions.
waitpkg_supported and its alias __vdso_waitpkg_supported check if
user wait
User wants to query if user wait instructions (umonitor, umwait, and
tpause) are supported and use the instructions. The vDSO functions
provides fast interface for user to check the support and use the
instructions.
waitpkg_supported and its alias __vdso_waitpkg_supported check if
user wait
MOVDIRI moves doubleword or quadword from register to memory through
direct store which is implemented by using write combining (WC) for
writing data directly into memory without caching the data.
Programmable agents can handle streaming offload (e.g. high speed packet
processing in network).
UMONITOR, UMWAIT, and TPAUSE are a set of user wait instructions.
UMONITOR arms address monitoring hardware using an address. A store
to an address within the specified address range triggers the
monitoring hardware to wake up the processor waiting in umwait.
UMWAIT instructs the processor to
MOVDIRI moves doubleword or quadword from register to memory through
direct store which is implemented by using write combining (WC) for
writing data directly into memory without caching the data.
Programmable agents can handle streaming offload (e.g. high speed packet
processing in network).
UMONITOR, UMWAIT, and TPAUSE are a set of user wait instructions.
UMONITOR arms address monitoring hardware using an address. A store
to an address within the specified address range triggers the
monitoring hardware to wake up the processor waiting in umwait.
UMWAIT instructs the processor to
On 07/23/2018 03:55 PM, Steven Rostedt wrote:
> Can you add a comment here stating something to the affect of:
> /* task is now visible to other tasks */
>
> -- Steve
Sure, but isn't that a bit misleading? It will have been visible since
some unknown point in time between waking up
On 07/23/2018 03:55 PM, Steven Rostedt wrote:
> Can you add a comment here stating something to the affect of:
> /* task is now visible to other tasks */
>
> -- Steve
Sure, but isn't that a bit misleading? It will have been visible since
some unknown point in time between waking up
On Fri, Jul 20, 2018 at 12:58 PM Paul Cercueil wrote:
>
> Hi Rob,
>
> Le ven. 20 juil. 2018 à 17:30, Rob Herring a écrit :
> > On Fri, Jul 13, 2018 at 04:38:40PM +0200, Paul Cercueil wrote:
> >> The UART in the jz4725b works just like in the other JZ SoCs, so
> >> this
> >> commit simply adds
On Fri, Jul 20, 2018 at 12:58 PM Paul Cercueil wrote:
>
> Hi Rob,
>
> Le ven. 20 juil. 2018 à 17:30, Rob Herring a écrit :
> > On Fri, Jul 13, 2018 at 04:38:40PM +0200, Paul Cercueil wrote:
> >> The UART in the jz4725b works just like in the other JZ SoCs, so
> >> this
> >> commit simply adds
init_ohci1394_wait_for_busresets() and
init_ohci1394_reset_and_init_dma() are never called in atomic context.
They call mdelay() to busily wait, which is not necessary.
mdelay() can be replaced with msleep().
This is found by a static analysis tool named DCNS written by myself.
Signed-off-by:
init_ohci1394_wait_for_busresets() and
init_ohci1394_reset_and_init_dma() are never called in atomic context.
They call mdelay() to busily wait, which is not necessary.
mdelay() can be replaced with msleep().
This is found by a static analysis tool named DCNS written by myself.
Signed-off-by:
Hi,
Le lun. 23 juil. 2018 à 16:18, Rob Herring a écrit :
On Fri, Jul 20, 2018 at 1:04 PM Paul Cercueil
wrote:
Hi,
Le ven. 20 juil. 2018 à 17:39, Rob Herring a
écrit :
> On Sat, Jul 14, 2018 at 03:50:08PM +0200, Paul Cercueil wrote:
>>
>>
>> Le sam. 14 juil. 2018 à 15:32,
Hi,
Le lun. 23 juil. 2018 à 16:18, Rob Herring a écrit :
On Fri, Jul 20, 2018 at 1:04 PM Paul Cercueil
wrote:
Hi,
Le ven. 20 juil. 2018 à 17:39, Rob Herring a
écrit :
> On Sat, Jul 14, 2018 at 03:50:08PM +0200, Paul Cercueil wrote:
>>
>>
>> Le sam. 14 juil. 2018 à 15:32,
On Fri, Jul 20, 2018 at 1:04 PM Paul Cercueil wrote:
>
> Hi,
>
> Le ven. 20 juil. 2018 à 17:39, Rob Herring a écrit :
> > On Sat, Jul 14, 2018 at 03:50:08PM +0200, Paul Cercueil wrote:
> >>
> >>
> >> Le sam. 14 juil. 2018 à 15:32, Alexandre Belloni
> >> a écrit :
> >> > On 14/07/2018
On Fri, Jul 20, 2018 at 1:04 PM Paul Cercueil wrote:
>
> Hi,
>
> Le ven. 20 juil. 2018 à 17:39, Rob Herring a écrit :
> > On Sat, Jul 14, 2018 at 03:50:08PM +0200, Paul Cercueil wrote:
> >>
> >>
> >> Le sam. 14 juil. 2018 à 15:32, Alexandre Belloni
> >> a écrit :
> >> > On 14/07/2018
On 07/22/2018 04:58 AM, Liu Xiang wrote:
> The URL of bq27441-g1 and bq27426 are missing and bq27520-g4 is duplicated.
>
> Signed-off-by: Liu Xiang
> ---
Acked-by: Andrew F. Davis
> drivers/power/supply/bq27xxx_battery.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff
On 07/22/2018 04:58 AM, Liu Xiang wrote:
> The URL of bq27441-g1 and bq27426 are missing and bq27520-g4 is duplicated.
>
> Signed-off-by: Liu Xiang
> ---
Acked-by: Andrew F. Davis
> drivers/power/supply/bq27xxx_battery.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff
On 13:56-20180723, Jassi Brar wrote:
> On Mon, Jul 23, 2018 at 6:59 PM, Nishanth Menon wrote:
[...]
> >> .../bindings/mailbox/ti,secure-proxy.txt | 50 +++
> >> drivers/mailbox/ti-msgmgr.c| 353
> >> +
> &g
On 13:56-20180723, Jassi Brar wrote:
> On Mon, Jul 23, 2018 at 6:59 PM, Nishanth Menon wrote:
[...]
> >> .../bindings/mailbox/ti,secure-proxy.txt | 50 +++
> >> drivers/mailbox/ti-msgmgr.c| 353
> >> +
> &g
On Mon, Jul 23, 2018 at 08:30:06AM -0500, Josh Poimboeuf wrote:
> On Thu, Jul 19, 2018 at 11:19:54PM +0200, Peter Zijlstra wrote:
> > --- a/include/uapi/linux/perf_event.h
> > +++ b/include/uapi/linux/perf_event.h
> > @@ -143,6 +143,8 @@ enum perf_event_sample_format {
> >
On Mon, Jul 23, 2018 at 08:30:06AM -0500, Josh Poimboeuf wrote:
> On Thu, Jul 19, 2018 at 11:19:54PM +0200, Peter Zijlstra wrote:
> > --- a/include/uapi/linux/perf_event.h
> > +++ b/include/uapi/linux/perf_event.h
> > @@ -143,6 +143,8 @@ enum perf_event_sample_format {
> >
On Mon, Jul 23, 2018 at 01:49:46PM +0100, Patrick Bellasi wrote:
> On 23-Jul 11:49, Peter Zijlstra wrote:
>
> [...]
>
> > > -void __getparam_dl(struct task_struct *p, struct sched_attr *attr)
> > > +void __getparam_dl(struct task_struct *p, struct sched_attr *attr,
> > > +unsigned
On Mon, Jul 23, 2018 at 01:49:46PM +0100, Patrick Bellasi wrote:
> On 23-Jul 11:49, Peter Zijlstra wrote:
>
> [...]
>
> > > -void __getparam_dl(struct task_struct *p, struct sched_attr *attr)
> > > +void __getparam_dl(struct task_struct *p, struct sched_attr *attr,
> > > +unsigned
Yixun Lan writes:
[...]
>>
>>> Second, we might like to convert eMMC driver to also use mmc-clkc model.
>>
>> IMO, this should be done as part of merging this series. Otherwise, we
>> have duplicated code for the same thing.
>
> IMO, I'd leave this out of this series, since this patch series
Yixun Lan writes:
[...]
>>
>>> Second, we might like to convert eMMC driver to also use mmc-clkc model.
>>
>> IMO, this should be done as part of merging this series. Otherwise, we
>> have duplicated code for the same thing.
>
> IMO, I'd leave this out of this series, since this patch series
Hi!
> here are 3 patches which update the PTI-x86-32 patches recently merged
> into the tip-tree. The patches are ordered by importance:
It seems PTI is now in -next. I'll test that soon.
Meanwhile... it looks like gcc is not slowed down significantly, but
other stuff sees 30% .. 40%
Hi!
> here are 3 patches which update the PTI-x86-32 patches recently merged
> into the tip-tree. The patches are ordered by importance:
It seems PTI is now in -next. I'll test that soon.
Meanwhile... it looks like gcc is not slowed down significantly, but
other stuff sees 30% .. 40%
On Mon, Jul 23, 2018 at 04:20:32AM -0700, Srikar Dronamraju wrote:
> > If you maybe write that like:
> >
> > if (time_after(jiffies, next_window) &&
> > xchg(>numabalancing_migrate_nr_pages, 0UL)) {
> >
> > do {
> > next_window += interval;
> >
On Mon, Jul 23, 2018 at 04:20:32AM -0700, Srikar Dronamraju wrote:
> > If you maybe write that like:
> >
> > if (time_after(jiffies, next_window) &&
> > xchg(>numabalancing_migrate_nr_pages, 0UL)) {
> >
> > do {
> > next_window += interval;
> >
On Fri, Jul 20, 2018 at 11:54 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 20, 2018 at 10:26 AM, Rob Herring wrote:
> > On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
> >>
> >> Rob,
> >>
> >> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
> >> > On Fri, Jul 06, 2018 at 04:31:42PM
On Fri, Jul 20, 2018 at 11:54 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jul 20, 2018 at 10:26 AM, Rob Herring wrote:
> > On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
> >>
> >> Rob,
> >>
> >> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
> >> > On Fri, Jul 06, 2018 at 04:31:42PM
On Sun, Jul 22, 2018 at 07:28:01PM -0700, Hugh Dickins wrote:
> Whether or not that fixed syzbot's kernel BUG at mm/shmem.c:815!
> I don't know, but I'm afraid it has not fixed linux-next breakage of
> huge tmpfs: I get a similar page_to_pgoff BUG at mm/filemap.c:1466!
>
> Please try something
On Fri, Jul 20, 2018 at 2:00 PM Logan Gunthorpe wrote:
>
> This commit fixes pingpong support for existing drivers that do not
> implement ntb_default_port_number() and ntb_default_peer_port_number().
> This is required for hardware (like the crosslink topology of
> switchtec) which cannot assign
On Sun, Jul 22, 2018 at 07:28:01PM -0700, Hugh Dickins wrote:
> Whether or not that fixed syzbot's kernel BUG at mm/shmem.c:815!
> I don't know, but I'm afraid it has not fixed linux-next breakage of
> huge tmpfs: I get a similar page_to_pgoff BUG at mm/filemap.c:1466!
>
> Please try something
On Fri, Jul 20, 2018 at 2:00 PM Logan Gunthorpe wrote:
>
> This commit fixes pingpong support for existing drivers that do not
> implement ntb_default_port_number() and ntb_default_peer_port_number().
> This is required for hardware (like the crosslink topology of
> switchtec) which cannot assign
On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> Srikar Dronamraju (19):
> sched/numa: Remove redundant field.
> sched/numa: Evaluate move once per node
> sched/numa: Simplify load_too_imbalanced
> sched/numa: Set preferred_node based on best_cpu
> sched/numa: Use
On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> Srikar Dronamraju (19):
> sched/numa: Remove redundant field.
> sched/numa: Evaluate move once per node
> sched/numa: Simplify load_too_imbalanced
> sched/numa: Set preferred_node based on best_cpu
> sched/numa: Use
Add some debugging to be able to check the proper initialization
of the BQ25896 part.
Enable the BQ25896 part.
Add 2 new parameters "voltage_now" and "model_name".
Signed-off-by: Angus Ainslie
---
drivers/power/supply/bq25890_charger.c | 68 ++
1 file changed, 58
Add some debugging to be able to check the proper initialization
of the BQ25896 part.
Enable the BQ25896 part.
Add 2 new parameters "voltage_now" and "model_name".
Signed-off-by: Angus Ainslie
---
drivers/power/supply/bq25890_charger.c | 68 ++
1 file changed, 58
> -Original Message-
> From: Lucas Stach [mailto:l.st...@pengutronix.de]
> Sent: 2018年7月23日 18:54
> To: Robin Gong ; vk...@kernel.org;
> dan.j.willi...@intel.com; s.ha...@pengutronix.de; li...@armlinux.org.uk
> Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> ker...@pengutronix.de;
ndings: mailbox: Add support for secure proxy threads
>> mailbox: ti-msgmgr: Add support for Secure Proxy
>>
>> .../bindings/mailbox/ti,secure-proxy.txt | 50 +++
>> drivers/mailbox/ti-msgmgr.c | 353
>> +
&g
On Mon, 23 Jul 2018 15:42:10 +0200
Snild Dolkow wrote:
> There was a window for racing when task->comm was being written. The
> vsnprintf function writes 16 bytes, then counts the rest, then null
> terminates. In the meantime, other threads could see the non-terminated
> comm value. In our case,
> -Original Message-
> From: Lucas Stach [mailto:l.st...@pengutronix.de]
> Sent: 2018年7月23日 18:54
> To: Robin Gong ; vk...@kernel.org;
> dan.j.willi...@intel.com; s.ha...@pengutronix.de; li...@armlinux.org.uk
> Cc: dmaeng...@vger.kernel.org; dl-linux-imx ;
> ker...@pengutronix.de;
ndings: mailbox: Add support for secure proxy threads
>> mailbox: ti-msgmgr: Add support for Secure Proxy
>>
>> .../bindings/mailbox/ti,secure-proxy.txt | 50 +++
>> drivers/mailbox/ti-msgmgr.c | 353
>> +
&g
On Mon, 23 Jul 2018 15:42:10 +0200
Snild Dolkow wrote:
> There was a window for racing when task->comm was being written. The
> vsnprintf function writes 16 bytes, then counts the rest, then null
> terminates. In the meantime, other threads could see the non-terminated
> comm value. In our case,
Hello,
On Fri, 15 Jun 2018 19:04:45 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 06/15/2018 06:52 PM, Thomas Petazzoni wrote:
>
> > The fast path of get_user_pages_fast() disables IRQs and then does:
> >
> > - gup_pud_range()
> >- gup_pmd_range()
> > - gup_pte_range()
> >-
Hello,
On Fri, 15 Jun 2018 19:04:45 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 06/15/2018 06:52 PM, Thomas Petazzoni wrote:
>
> > The fast path of get_user_pages_fast() disables IRQs and then does:
> >
> > - gup_pud_range()
> >- gup_pmd_range()
> > - gup_pte_range()
> >-
Hi Leonard,
On Mon, Jul 23, 2018 at 10:42 AM, Leonard Crestez
wrote:
> This is one of the default lcdif panel options for several imx
> development boards. Now that we switched to CONFIG_DRM_MXSFB=y this
> should be enabled as well.
>
> Signed-off-by: Leonard Crestez
Already sent as part of a
Hi Leonard,
On Mon, Jul 23, 2018 at 10:42 AM, Leonard Crestez
wrote:
> This is one of the default lcdif panel options for several imx
> development boards. Now that we switched to CONFIG_DRM_MXSFB=y this
> should be enabled as well.
>
> Signed-off-by: Leonard Crestez
Already sent as part of a
commit a5b8bd47dcc57 ("bpf tools: Collect eBPF programs from their own
sections")
cause a compiler error when building the perf tool in the linux-next tree.
I compile it using a FEDORA 28 installation, my gcc compiler version:
gcc (GCC) 8.0.1 20180324 (Red Hat 8.0.1-0.20)
Here is the error
commit a5b8bd47dcc57 ("bpf tools: Collect eBPF programs from their own
sections")
cause a compiler error when building the perf tool in the linux-next tree.
I compile it using a FEDORA 28 installation, my gcc compiler version:
gcc (GCC) 8.0.1 20180324 (Red Hat 8.0.1-0.20)
Here is the error
This is one of the default lcdif panel options for several imx
development boards. Now that we switched to CONFIG_DRM_MXSFB=y this
should be enabled as well.
Signed-off-by: Leonard Crestez
---
arch/arm/configs/imx_v6_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
This is one of the default lcdif panel options for several imx
development boards. Now that we switched to CONFIG_DRM_MXSFB=y this
should be enabled as well.
Signed-off-by: Leonard Crestez
---
arch/arm/configs/imx_v6_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
There was a window for racing when task->comm was being written. The
vsnprintf function writes 16 bytes, then counts the rest, then null
terminates. In the meantime, other threads could see the non-terminated
comm value. In our case, it got into the trace system's saved cmdlines
and could cause
There was a window for racing when task->comm was being written. The
vsnprintf function writes 16 bytes, then counts the rest, then null
terminates. In the meantime, other threads could see the non-terminated
comm value. In our case, it got into the trace system's saved cmdlines
and could cause
801 - 900 of 1916 matches
Mail list logo
