Hi John,
Thanks for having documentation as a part of the patch. Some kernel-doc
nits below.
On Mon, Dec 03, 2018 at 04:17:19PM -0800, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> Introduces put_user_page(), which simply calls put_page().
> This provides a way to update all
Hi John,
Thanks for having documentation as a part of the patch. Some kernel-doc
nits below.
On Mon, Dec 03, 2018 at 04:17:19PM -0800, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> Introduces put_user_page(), which simply calls put_page().
> This provides a way to update all
Hi, Paul:
the enclosed is the log trigger the 120s hung_task_panic without other debug
patches, the hung task is blocked at __wait_rcu_gp, it means the rcu_cpu_stall
can't detect the scenario:
echo 1 > /proc/sys/kernel/panic_on_rcu_stall
echo 7 >
Hi, Paul:
the enclosed is the log trigger the 120s hung_task_panic without other debug
patches, the hung task is blocked at __wait_rcu_gp, it means the rcu_cpu_stall
can't detect the scenario:
echo 1 > /proc/sys/kernel/panic_on_rcu_stall
echo 7 >
On Fri, Nov 30, 2018 at 10:44:06AM -0500, Steven Rostedt wrote:
> From: Tzvetomir Stoyanov
>
> This patch installs trace-seq.h header file on "make install".
>
> Signed-off-by: Tzvetomir Stoyanov
> Signed-off-by: Steven Rostedt (VMware)
> ---
> tools/lib/traceevent/Makefile | 3 ++-
> 1 file
On Fri, Nov 30, 2018 at 10:44:06AM -0500, Steven Rostedt wrote:
> From: Tzvetomir Stoyanov
>
> This patch installs trace-seq.h header file on "make install".
>
> Signed-off-by: Tzvetomir Stoyanov
> Signed-off-by: Steven Rostedt (VMware)
> ---
> tools/lib/traceevent/Makefile | 3 ++-
> 1 file
On 12/4/18 5:04 AM, jgli...@redhat.com wrote:
From: Jérôme Glisse
Heterogeneous memory system are becoming more and more the norm, in
those system there is not only the main system memory for each node,
but also device memory and|or memory hierarchy to consider. Device
memory can comes from a
On 12/4/18 5:04 AM, jgli...@redhat.com wrote:
From: Jérôme Glisse
Heterogeneous memory system are becoming more and more the norm, in
those system there is not only the main system memory for each node,
but also device memory and|or memory hierarchy to consider. Device
memory can comes from a
On Tue, Dec 04, 2018 at 03:35:13PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/hv/channel_mgmt.c
>
> between commit:
>
> 37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
> workqueues")
On Tue, Dec 04, 2018 at 03:35:13PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/hv/channel_mgmt.c
>
> between commit:
>
> 37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
> workqueues")
On Tue, Dec 04, 2018 at 08:39:16AM +0100, Martin Kepplinger wrote:
> On 02.12.18 16:02, Richard Weinberger wrote:
> > Sasha,
> >
> > Am Sonntag, 2. Dezember 2018, 15:35:43 CET schrieb Sasha Levin:
> > > On Sun, Dec 02, 2018 at 11:50:33AM +, Sudip Mukherjee wrote:
> > > > > > Now queued up for
On Tue, Dec 04, 2018 at 08:39:16AM +0100, Martin Kepplinger wrote:
> On 02.12.18 16:02, Richard Weinberger wrote:
> > Sasha,
> >
> > Am Sonntag, 2. Dezember 2018, 15:35:43 CET schrieb Sasha Levin:
> > > On Sun, Dec 02, 2018 at 11:50:33AM +, Sudip Mukherjee wrote:
> > > > > > Now queued up for
Hi Steve,
On Mon, 3 Dec 2018 21:18:07 -0500
Steven Rostedt wrote:
> Hi Masami,
>
> I started testing some of my new code and the system got into a
> strange state. Debugging further, I found the cause came from the
> kprobe tests. It became stranger to me that I could reproduce it with
> older
Hi Steve,
On Mon, 3 Dec 2018 21:18:07 -0500
Steven Rostedt wrote:
> Hi Masami,
>
> I started testing some of my new code and the system got into a
> strange state. Debugging further, I found the cause came from the
> kprobe tests. It became stranger to me that I could reproduce it with
> older
On 02.12.18 16:02, Richard Weinberger wrote:
Sasha,
Am Sonntag, 2. Dezember 2018, 15:35:43 CET schrieb Sasha Levin:
On Sun, Dec 02, 2018 at 11:50:33AM +, Sudip Mukherjee wrote:
Now queued up for 4.14.y, thanks.
can you *please* slow a little down?
True. It will really help if you can
On 02.12.18 16:02, Richard Weinberger wrote:
Sasha,
Am Sonntag, 2. Dezember 2018, 15:35:43 CET schrieb Sasha Levin:
On Sun, Dec 02, 2018 at 11:50:33AM +, Sudip Mukherjee wrote:
Now queued up for 4.14.y, thanks.
can you *please* slow a little down?
True. It will really help if you can
On Mon 03-12-18 15:50:18, David Rientjes wrote:
> This fixes a 13.9% of remote memory access regression and 40% remote
> memory allocation regression on Haswell when the local node is fragmented
> for hugepage sized pages and memory is being faulted with either the thp
> defrag setting of "always"
On Mon 03-12-18 15:50:18, David Rientjes wrote:
> This fixes a 13.9% of remote memory access regression and 40% remote
> memory allocation regression on Haswell when the local node is fragmented
> for hugepage sized pages and memory is being faulted with either the thp
> defrag setting of "always"
On Mon 03-12-18 15:50:24, David Rientjes wrote:
> This is a full revert of ac5b2c18911f ("mm: thp: relax __GFP_THISNODE for
> MADV_HUGEPAGE mappings") and a partial revert of 89c83fb539f9 ("mm, thp:
> consolidate THP gfp handling into alloc_hugepage_direct_gfpmask").
>
> By not setting
On Mon 03-12-18 15:50:24, David Rientjes wrote:
> This is a full revert of ac5b2c18911f ("mm: thp: relax __GFP_THISNODE for
> MADV_HUGEPAGE mappings") and a partial revert of 89c83fb539f9 ("mm, thp:
> consolidate THP gfp handling into alloc_hugepage_direct_gfpmask").
>
> By not setting
After upgrading my kernel to 4.19 I got a corruption on nearly every
reboot or resume from suspend on my Acer s7-391 [UEFI boot].
Going to my UEFI setup and changing IDE mode from IDE to ATA seems to
have resolved the issue for me.
Don't know, though, if that is a valid data point or if it was a
After upgrading my kernel to 4.19 I got a corruption on nearly every
reboot or resume from suspend on my Acer s7-391 [UEFI boot].
Going to my UEFI setup and changing IDE mode from IDE to ATA seems to
have resolved the issue for me.
Don't know, though, if that is a valid data point or if it was a
Hi Steve,
On Fri, Nov 30, 2018 at 10:44:05AM -0500, Steven Rostedt wrote:
> From: Tzvetomir Stoyanov
>
> This patch implements integration with pkg-config framework.
> pkg-config can be used by the library users to determine
> required CFLAGS and LDFLAGS in order to use the library
>
>
Hi Steve,
On Fri, Nov 30, 2018 at 10:44:05AM -0500, Steven Rostedt wrote:
> From: Tzvetomir Stoyanov
>
> This patch implements integration with pkg-config framework.
> pkg-config can be used by the library users to determine
> required CFLAGS and LDFLAGS in order to use the library
>
>
On Mon, Dec 03, 2018 at 11:22:46PM +0159, Thomas Backlund wrote:
> Den 2018-12-03 kl. 11:22, skrev Sasha Levin:
>
> >
> > This is a case where theory collides with the real world. Yes, our QA is
> > lacking, but we don't have the option of not doing the current process.
> > If we stop
On Mon, Dec 03, 2018 at 11:22:46PM +0159, Thomas Backlund wrote:
> Den 2018-12-03 kl. 11:22, skrev Sasha Levin:
>
> >
> > This is a case where theory collides with the real world. Yes, our QA is
> > lacking, but we don't have the option of not doing the current process.
> > If we stop
On Mon, Dec 03, 2018 at 04:22:02PM -0600, Tom Zanussi wrote:
> Hi Namhyung,
>
> On Fri, 2018-11-23 at 11:50 +0900, Namhyung Kim wrote:
> > Hi Tom,
> >
> > On Wed, Nov 14, 2018 at 02:18:02PM -0600, Tom Zanussi wrote:
> > > From: Tom Zanussi
> > >
>
> [snip]
>
> > >
> enum handler_id {
> > >
On Mon, Dec 03, 2018 at 04:22:02PM -0600, Tom Zanussi wrote:
> Hi Namhyung,
>
> On Fri, 2018-11-23 at 11:50 +0900, Namhyung Kim wrote:
> > Hi Tom,
> >
> > On Wed, Nov 14, 2018 at 02:18:02PM -0600, Tom Zanussi wrote:
> > > From: Tom Zanussi
> > >
>
> [snip]
>
> > >
> enum handler_id {
> > >
On Tue 04-12-18 10:40:29, Xunlei Pang wrote:
> On 2018/12/4 AM 1:22, Michal Hocko wrote:
> > On Mon 03-12-18 23:20:31, Xunlei Pang wrote:
> >> On 2018/12/3 下午7:56, Michal Hocko wrote:
> >>> On Mon 03-12-18 16:01:18, Xunlei Pang wrote:
> There may be cgroup memory overcommitment, it will
Some standard SD host controllers can support both external dma
controllers as well as ADMA/SDMA in which the SD host controller
acts as DMA master. TI's omap controller is the case as an example.
Currently the generic SDHCI code supports ADMA/SDMA integrated in
the host controller but does not
On Mon, Dec 03, 2018 at 11:03:09AM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> We have received a bug report that an injected MCE about faulty memory
> prevents memory offline to succeed. The underlying reason is that the
> HWPoison page has an elevated reference count and the migration
On Tue 04-12-18 10:40:29, Xunlei Pang wrote:
> On 2018/12/4 AM 1:22, Michal Hocko wrote:
> > On Mon 03-12-18 23:20:31, Xunlei Pang wrote:
> >> On 2018/12/3 下午7:56, Michal Hocko wrote:
> >>> On Mon 03-12-18 16:01:18, Xunlei Pang wrote:
> There may be cgroup memory overcommitment, it will
Some standard SD host controllers can support both external dma
controllers as well as ADMA/SDMA in which the SD host controller
acts as DMA master. TI's omap controller is the case as an example.
Currently the generic SDHCI code supports ADMA/SDMA integrated in
the host controller but does not
On Mon, Dec 03, 2018 at 11:03:09AM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> We have received a bug report that an injected MCE about faulty memory
> prevents memory offline to succeed. The underlying reason is that the
> HWPoison page has an elevated reference count and the migration
sdhci-omap can support both external dma controller via dmaengine
framework as well as ADMA which standard SD host controller
provides.
Signed-off-by: Chunyan Zhang
---
Documentation/devicetree/bindings/mmc/sdhci-omap.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
sdhci-omap can support both external dma controller via dmaengine framework
as well as ADMA which standard SD host controller provides.
Signed-off-by: Chunyan Zhang
---
drivers/mmc/host/Kconfig | 1 +
drivers/mmc/host/sdhci-omap.c | 10 ++
2 files changed, 11 insertions(+)
diff
Am 03.12.18 um 21:14 schrieb Eric Anholt:
> With DEBUG_SLAB (poisoning on free) enabled, I could quickly produce
> an oops when tracing V3D.
Good catch, but the solution is a clear NAK.
drm_sched_entity_add_dependency_cb() can result in setting
entity->dependency to NULL. That in turn can lead
sdhci-omap can support both external dma controller via dmaengine
framework as well as ADMA which standard SD host controller
provides.
Signed-off-by: Chunyan Zhang
---
Documentation/devicetree/bindings/mmc/sdhci-omap.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
sdhci-omap can support both external dma controller via dmaengine framework
as well as ADMA which standard SD host controller provides.
Signed-off-by: Chunyan Zhang
---
drivers/mmc/host/Kconfig | 1 +
drivers/mmc/host/sdhci-omap.c | 10 ++
2 files changed, 11 insertions(+)
diff
Am 03.12.18 um 21:14 schrieb Eric Anholt:
> With DEBUG_SLAB (poisoning on free) enabled, I could quickly produce
> an oops when tracing V3D.
Good catch, but the solution is a clear NAK.
drm_sched_entity_add_dependency_cb() can result in setting
entity->dependency to NULL. That in turn can lead
Currently the generic SDHCI code in the Linux kernel supports the SD
standard DMA integrated into the host controller but does not have any
support for external DMA controllers implemented using dmaengine meaning
that custom code is needed for any systems that use a generic DMA
controller with
Currently the generic SDHCI code in the Linux kernel supports the SD
standard DMA integrated into the host controller but does not have any
support for external DMA controllers implemented using dmaengine meaning
that custom code is needed for any systems that use a generic DMA
controller with
On Tue 04-12-18 11:05:57, Pingfan Liu wrote:
> During my test on some AMD machine, with kexec -l nr_cpus=x option, the
> kernel failed to bootup, because some node's data struct can not be allocated,
> e.g, on x86, initialized by init_cpu_to_node()->init_memory_less_node(). But
> device->numa_node
On Tue 04-12-18 11:05:57, Pingfan Liu wrote:
> During my test on some AMD machine, with kexec -l nr_cpus=x option, the
> kernel failed to bootup, because some node's data struct can not be allocated,
> e.g, on x86, initialized by init_cpu_to_node()->init_memory_less_node(). But
> device->numa_node
On Tue, Dec 4, 2018 at 2:54 PM Wei Yang wrote:
>
> On Tue, Dec 04, 2018 at 11:05:57AM +0800, Pingfan Liu wrote:
> >During my test on some AMD machine, with kexec -l nr_cpus=x option, the
> >kernel failed to bootup, because some node's data struct can not be
> >allocated,
> >e.g, on x86,
On Tue, Dec 4, 2018 at 2:54 PM Wei Yang wrote:
>
> On Tue, Dec 04, 2018 at 11:05:57AM +0800, Pingfan Liu wrote:
> >During my test on some AMD machine, with kexec -l nr_cpus=x option, the
> >kernel failed to bootup, because some node's data struct can not be
> >allocated,
> >e.g, on x86,
On Tue, Dec 4, 2018 at 11:53 AM David Rientjes wrote:
>
> On Tue, 4 Dec 2018, Pingfan Liu wrote:
>
> > diff --git a/include/linux/gfp.h b/include/linux/gfp.h
> > index 76f8db0..8324953 100644
> > --- a/include/linux/gfp.h
> > +++ b/include/linux/gfp.h
> > @@ -453,6 +453,8 @@ static inline int
On Tue, Dec 4, 2018 at 11:53 AM David Rientjes wrote:
>
> On Tue, 4 Dec 2018, Pingfan Liu wrote:
>
> > diff --git a/include/linux/gfp.h b/include/linux/gfp.h
> > index 76f8db0..8324953 100644
> > --- a/include/linux/gfp.h
> > +++ b/include/linux/gfp.h
> > @@ -453,6 +453,8 @@ static inline int
Hello,
syzbot found the following crash on:
HEAD commit:4b78317679c4 Merge branch 'x86-pti-for-linus' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e979f540
kernel config: https://syzkaller.appspot.com/x/.config?x=4602730af4f872ef
Hello,
syzbot found the following crash on:
HEAD commit:4b78317679c4 Merge branch 'x86-pti-for-linus' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e979f540
kernel config: https://syzkaller.appspot.com/x/.config?x=4602730af4f872ef
On Tue, Dec 04, 2018 at 11:05:57AM +0800, Pingfan Liu wrote:
>During my test on some AMD machine, with kexec -l nr_cpus=x option, the
>kernel failed to bootup, because some node's data struct can not be allocated,
>e.g, on x86, initialized by init_cpu_to_node()->init_memory_less_node(). But
On Tue, Dec 04, 2018 at 11:05:57AM +0800, Pingfan Liu wrote:
>During my test on some AMD machine, with kexec -l nr_cpus=x option, the
>kernel failed to bootup, because some node's data struct can not be allocated,
>e.g, on x86, initialized by init_cpu_to_node()->init_memory_less_node(). But
Hi all,
Changes since 20181203:
The rdma tree gained a build failure so I used the version from
next-20181203.
The bpf-next tree gained conflicts against the bpf tree.
The char-misc tree gained a conflict against the char-misc.current tree.
The akpm tree lost its build failure but gained
Hi all,
Changes since 20181203:
The rdma tree gained a build failure so I used the version from
next-20181203.
The bpf-next tree gained conflicts against the bpf tree.
The char-misc tree gained a conflict against the char-misc.current tree.
The akpm tree lost its build failure but gained
Commit-ID: a6f1de04276d036b61c4d1dbd0367e6b430d8783
Gitweb: https://git.kernel.org/tip/a6f1de04276d036b61c4d1dbd0367e6b430d8783
Author: Paul E. McKenney
AuthorDate: Mon, 3 Dec 2018 15:04:51 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:52 +0100
tools/memory-model:
On 2018-12-03 at 05:56:13 +0200, Mihai Donțu wrote:
> Hi Paolo,
>
> On Fri, 2018-11-30 at 11:07 +0100, Paolo Bonzini wrote:
> > On 30/11/18 08:52, Zhang Yi wrote:
> > > Here is a patch-series which adding EPT-Based Sub-page Write Protection
> > > Support.
> > >
> > > Introduction:
> > >
> > >
Commit-ID: 4607abbcf464ea2be14da444215d05c73025cf6e
Gitweb: https://git.kernel.org/tip/4607abbcf464ea2be14da444215d05c73025cf6e
Author: Andrea Parri
AuthorDate: Mon, 3 Dec 2018 15:04:49 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:51 +0100
tools/memory-model: Model
Commit-ID: a6f1de04276d036b61c4d1dbd0367e6b430d8783
Gitweb: https://git.kernel.org/tip/a6f1de04276d036b61c4d1dbd0367e6b430d8783
Author: Paul E. McKenney
AuthorDate: Mon, 3 Dec 2018 15:04:51 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:52 +0100
tools/memory-model:
On 2018-12-03 at 05:56:13 +0200, Mihai Donțu wrote:
> Hi Paolo,
>
> On Fri, 2018-11-30 at 11:07 +0100, Paolo Bonzini wrote:
> > On 30/11/18 08:52, Zhang Yi wrote:
> > > Here is a patch-series which adding EPT-Based Sub-page Write Protection
> > > Support.
> > >
> > > Introduction:
> > >
> > >
Commit-ID: 4607abbcf464ea2be14da444215d05c73025cf6e
Gitweb: https://git.kernel.org/tip/4607abbcf464ea2be14da444215d05c73025cf6e
Author: Andrea Parri
AuthorDate: Mon, 3 Dec 2018 15:04:49 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:51 +0100
tools/memory-model: Model
Commit-ID: e188d24a382d609ec7ca6c1a00396202565b7831
Gitweb: https://git.kernel.org/tip/e188d24a382d609ec7ca6c1a00396202565b7831
Author: Paul E. McKenney
AuthorDate: Mon, 3 Dec 2018 15:04:50 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:52 +0100
tools/memory-model: Add
Commit-ID: e188d24a382d609ec7ca6c1a00396202565b7831
Gitweb: https://git.kernel.org/tip/e188d24a382d609ec7ca6c1a00396202565b7831
Author: Paul E. McKenney
AuthorDate: Mon, 3 Dec 2018 15:04:50 -0800
Committer: Ingo Molnar
CommitDate: Tue, 4 Dec 2018 07:29:52 +0100
tools/memory-model: Add
Add cs-gpio feature for LPSPI. Use fsl_lpspi_prepare_message() and
fsl_lpspi_unprepare_message() to enable and control cs line.
These two functions will be only called at the beginning and the ending
of a message transfer.
Still support using the mode without cs-gpio. It depends on if attribute
Add cs-gpio feature for LPSPI. Use fsl_lpspi_prepare_message() and
fsl_lpspi_unprepare_message() to enable and control cs line.
These two functions will be only called at the beginning and the ending
of a message transfer.
Still support using the mode without cs-gpio. It depends on if attribute
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements.
On msm8996, multiple cores, viz. mdss, video, etc. use this
smmu. On sdm845, this smmu is used with gpu.
Add bindings for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Rob Herring
Reviewed-by: Tomasz
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the master is added to the smmu.
Signed-off-by: Sricharan R
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements.
On msm8996, multiple cores, viz. mdss, video, etc. use this
smmu. On sdm845, this smmu is used with gpu.
Add bindings for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Rob Herring
Reviewed-by: Tomasz
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the master is added to the smmu.
Signed-off-by: Sricharan R
Remove Reset operation in fsl_lpspi_config(). This RST may cause both CLK
and CS pins go from high to low level under cs-gpio mode.
Add fsl_lpspi_reset() function after one message transfer to clear all
flags in use.
Signed-off-by: Clark Wang
Reviewed-by: Fugang Duan
---
Remove Reset operation in fsl_lpspi_config(). This RST may cause both CLK
and CS pins go from high to low level under cs-gpio mode.
Add fsl_lpspi_reset() function after one message transfer to clear all
flags in use.
Signed-off-by: Clark Wang
Reviewed-by: Fugang Duan
---
Use SR_TDF to judge if need to send data, and SR_FCF is to judge if
transmission end and to replace the waiting after transmission end.
This waiting has no actual meaning, for module will set the FCF
flag at the real end.
The changes of interrupt flag and ISR function reduce the times of
calling
Use SR_TDF to judge if need to send data, and SR_FCF is to judge if
transmission end and to replace the waiting after transmission end.
This waiting has no actual meaning, for module will set the FCF
flag at the real end.
The changes of interrupt flag and ISR function reduce the times of
calling
From: Han Xu
Enable the runtime power management for lpspi module.
Signed-off-by: Han Xu
Reviewed-by: Frank Li
---
drivers/spi/spi-fsl-lpspi.c | 117
1 file changed, 92 insertions(+), 25 deletions(-)
diff --git
From: Han Xu
Enable the runtime power management for lpspi module.
Signed-off-by: Han Xu
Reviewed-by: Frank Li
---
drivers/spi/spi-fsl-lpspi.c | 117
1 file changed, 92 insertions(+), 25 deletions(-)
diff --git
Hi Lukasz,
On 2018년 12월 03일 23:31, Lukasz Luba wrote:
> This patch adds implementation for global suspend/resume for
> devfreq framework. System suspend will next use these functions.
>
> The patch is based on earlier work by Tobias Jakobi.
Please remove it from each patch description.
>
>
Hi Lukasz,
On 2018년 12월 03일 23:31, Lukasz Luba wrote:
> This patch adds implementation for global suspend/resume for
> devfreq framework. System suspend will next use these functions.
>
> The patch is based on earlier work by Tobias Jakobi.
Please remove it from each patch description.
>
>
On Mon, 3 Dec 2018 07:39:10 -0800
Tony Lindgren wrote:
> * Stephen Boyd [181130 23:52]:
> > Quoting Tony Lindgren (2018-11-30 07:37:29)
> > > Hi,
> > >
> > > * Tero Kristo [181130 09:21]:
> > > > On 30/11/2018 09:57, Stephen Boyd wrote:
> > > > > No that is not preferred. Can the
On Mon, 3 Dec 2018 07:39:10 -0800
Tony Lindgren wrote:
> * Stephen Boyd [181130 23:52]:
> > Quoting Tony Lindgren (2018-11-30 07:37:29)
> > > Hi,
> > >
> > > * Tero Kristo [181130 09:21]:
> > > > On 30/11/2018 09:57, Stephen Boyd wrote:
> > > > > No that is not preferred. Can the
Hi Lukasz,
I add the comment about 'suspend_count'.
On 2018년 12월 04일 14:43, Chanwoo Choi wrote:
> Hi,
>
> On 2018년 12월 04일 14:36, Chanwoo Choi wrote:
>> Hi Lukasz,
>>
>> Looks good to me. But, I add the some comments.
>> If you will fix it, feel free to add my tag:
>> Reviewed-by: Chanwoo choi
Hi Lukasz,
I add the comment about 'suspend_count'.
On 2018년 12월 04일 14:43, Chanwoo Choi wrote:
> Hi,
>
> On 2018년 12월 04일 14:36, Chanwoo Choi wrote:
>> Hi Lukasz,
>>
>> Looks good to me. But, I add the some comments.
>> If you will fix it, feel free to add my tag:
>> Reviewed-by: Chanwoo choi
On 04/12/2018 06:49, H. Peter Anvin wrote:
> On 12/3/18 9:32 PM, Juergen Gross wrote:
>>
>> I'd like to send a followup patch doing that. And I'd like to not only
>> test sentinel for being non-zero, but all padding fields as well. This
>> should be 4.21 material, though.
>>
>
> No, you can't do
On 2018-12-03, Christian Brauner wrote:
> > > As I pointed out in another mail my I is to make this work by using
> > > file descriptors for /proc//task/. I don't want this in the
> > > initial patchset though. I prefer to slowly add those features once
> > > we have gotten the basic
On 04/12/2018 06:49, H. Peter Anvin wrote:
> On 12/3/18 9:32 PM, Juergen Gross wrote:
>>
>> I'd like to send a followup patch doing that. And I'd like to not only
>> test sentinel for being non-zero, but all padding fields as well. This
>> should be 4.21 material, though.
>>
>
> No, you can't do
On 2018-12-03, Christian Brauner wrote:
> > > As I pointed out in another mail my I is to make this work by using
> > > file descriptors for /proc//task/. I don't want this in the
> > > initial patchset though. I prefer to slowly add those features once
> > > we have gotten the basic
Hi Kishon,
On Tue, Dec 04, 2018 at 10:38:19AM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On 27/11/18 3:37 PM, Shawn Guo wrote:
> > It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> > is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs.
>
> Is this
Hi Kishon,
On Tue, Dec 04, 2018 at 10:38:19AM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On 27/11/18 3:37 PM, Shawn Guo wrote:
> > It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> > is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs.
>
> Is this
On Mon, 3 Dec 2018 11:52:41 +0530
Ravi Bangoria wrote:
> Hi Steve,
>
> Please pull this patch.
>
Please send a v2 version of the patch with the updated change log. And
should it have a Fixes and be tagged for stable?
-- Steve
> Thanks.
>
> On 11/15/18 6:13 PM, Oleg Nesterov wrote:
> > On
On Mon, 3 Dec 2018 11:52:41 +0530
Ravi Bangoria wrote:
> Hi Steve,
>
> Please pull this patch.
>
Please send a v2 version of the patch with the updated change log. And
should it have a Fixes and be tagged for stable?
-- Steve
> Thanks.
>
> On 11/15/18 6:13 PM, Oleg Nesterov wrote:
> > On
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
fs/exec.c
between commit:
67fe1224adc5 ("Revert "exec: make de_thread() freezable"")
from the pm tree and patch:
"fs/: remove caller signal_pending branch predictions"
from the akpm tree.
I fixed it up (see
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
fs/exec.c
between commit:
67fe1224adc5 ("Revert "exec: make de_thread() freezable"")
from the pm tree and patch:
"fs/: remove caller signal_pending branch predictions"
from the akpm tree.
I fixed it up (see
On 12/3/18 9:32 PM, Juergen Gross wrote:
>
> I'd like to send a followup patch doing that. And I'd like to not only
> test sentinel for being non-zero, but all padding fields as well. This
> should be 4.21 material, though.
>
No, you can't do that. That breaks backwards compatibility.
On 12/3/18 9:32 PM, Juergen Gross wrote:
>
> I'd like to send a followup patch doing that. And I'd like to not only
> test sentinel for being non-zero, but all padding fields as well. This
> should be 4.21 material, though.
>
No, you can't do that. That breaks backwards compatibility.
於 2018年12月3日 週一 上午5:34寫道：
>
> From: qii wang
>
> Add i2c compatible for MT8183. Compare to 2712 i2c controller, MT8183 has
> different registers, offsets, clock, and multi-user function.
>
> Signed-off-by: qii wang
> ---
> drivers/i2c/busses/i2c-mt65xx.c | 136
>
On Mon, 3 Dec 2018 22:51:52 +0100
Arnd Bergmann wrote:
> On Mon, Dec 3, 2018 at 8:22 PM Will Deacon wrote:
> >
> > Hi Anders,
> >
> > On Fri, Nov 30, 2018 at 04:09:56PM +0100, Anders Roxell wrote:
> > > Both of those functions end up calling ftrace_modify_code(), which is
> > > expensive
於 2018年12月3日 週一 上午5:34寫道：
>
> From: qii wang
>
> Add i2c compatible for MT8183. Compare to 2712 i2c controller, MT8183 has
> different registers, offsets, clock, and multi-user function.
>
> Signed-off-by: qii wang
> ---
> drivers/i2c/busses/i2c-mt65xx.c | 136
>
On Mon, 3 Dec 2018 22:51:52 +0100
Arnd Bergmann wrote:
> On Mon, Dec 3, 2018 at 8:22 PM Will Deacon wrote:
> >
> > Hi Anders,
> >
> > On Fri, Nov 30, 2018 at 04:09:56PM +0100, Anders Roxell wrote:
> > > Both of those functions end up calling ftrace_modify_code(), which is
> > > expensive
Hi,
On 2018년 12월 04일 14:36, Chanwoo Choi wrote:
> Hi Lukasz,
>
> Looks good to me. But, I add the some comments.
> If you will fix it, feel free to add my tag:
> Reviewed-by: Chanwoo choi
Sorry. Fix typo 'choi' to 'Choi' as following.
Reviewed-by: Chanwoo Choi
>
> On 2018년 12월 03일 23:31,
Hi,
On 2018년 12월 04일 14:36, Chanwoo Choi wrote:
> Hi Lukasz,
>
> Looks good to me. But, I add the some comments.
> If you will fix it, feel free to add my tag:
> Reviewed-by: Chanwoo choi
Sorry. Fix typo 'choi' to 'Choi' as following.
Reviewed-by: Chanwoo Choi
>
> On 2018년 12월 03일 23:31,
Hi,
On 2018년 12월 04일 13:39, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 2018년 12월 03일 23:31, Lukasz Luba wrote:
>> The refactoring is needed for the new client in devfreq: suspend.
>> To avoid code duplication, move it to the new local function
>> devfreq_set_target.
>>
>> The patch is based on
Hi,
On 2018년 12월 04일 13:39, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 2018년 12월 03일 23:31, Lukasz Luba wrote:
>> The refactoring is needed for the new client in devfreq: suspend.
>> To avoid code duplication, move it to the new local function
>> devfreq_set_target.
>>
>> The patch is based on
1 - 100 of 1632 matches
Mail list logo
