Some user might want to go through all registered wakeup sources
and doing things accordingly. For example, SoC PM driver might need to
do HW programming to prevent powering down specific IP which wakeup
source depending on. So add this API to help walk through all registered
wakeup source objects
On 2019/10/23 5:04, Bjorn Helgaas wrote:
> On Sat, Oct 19, 2019 at 02:45:43PM +0800, Yunsheng Lin wrote:
>> As the disscusion in [1]:
>
> We need to justify this patch right here in the commit log, not with a
> pointer to a 50+ message email thread.
Ok, thanks.
>
>> A PCI device really _MUST_
On 2019/10/16 22:25, Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 16, 2019 at 09:50:17PM +0800, Yunfeng Ye escreveu:
>> There are memory leaks and file descriptor resource leaks in
>> process_mapfile() and main().
>>
>> Fix this by adding free(), fclose() and free_arch_std_events()
>> on the
> Fixes: e932900a3279 ("arm: zynq: Use standard timer binding")
How do you think about to add the tag “Reported-by” for Michal Simek?
https://lore.kernel.org/linux-arm-kernel/2a6cdb63-397b-280a-7379-740e8f43d...@xilinx.com/
Hi Arthur,
I added this patch to my pull request, but I have a request for a follow-up
patch:
On 10/2/19 2:46 AM, Arthur Moraes do Lago wrote:
> Add mean window size parameter for debayer filter as a control in
> vimc-debayer.
>
> vimc-debayer was patched to allow changing mean window parameter
On Tue 22-10-19 22:28:02, Hillf Danton wrote:
>
> On Tue, 22 Oct 2019 14:42:41 +0200 Michal Hocko wrote:
> >
> > On Tue 22-10-19 20:14:39, Hillf Danton wrote:
> > >
> > > On Mon, 21 Oct 2019 14:27:28 +0200 Michal Hocko wrote:
> > [...]
> > > > Why do we care and which workloads would benefit
Hi, Xiang, Pratik,
On 2019/10/23 12:05, Gao Xiang wrote:
> From: Pratik Shinde
>
> Introduce superblock checksum feature in order to check
> a number of given blocks at mounting time.
>
> Signed-off-by: Pratik Shinde
> Signed-off-by: Gao Xiang
> ---
> changes from v3:
> (based on Pratik's
On Fri, 28 Jun 2019 at 09:10, Frederic Weisbecker wrote:
>
> On Fri, Jun 28, 2019 at 08:43:12AM +0800, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > On a machine, cpu 0 is used for housekeeping, the other 39 cpus in the
> > same socket are in nohz_full mode. We can observe huge time burn in the
next.git/commit/devicetree/bindings/rng/samsung,exynos5250-trng.txt?h=next-20191023=85552c22f03c9066c33f26f34538b67fee6a91a8
Thanks,
Andreas
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
Hi Brian,
Thank you for working on this!
On 13.10.19 г. 11:08 ч., Brian Masney wrote:
> Add interconnect support for msm8974-based SoCs in order to support the
> GPU on this platform.
>
> Signed-off-by: Brian Masney
> ---
> arch/arm/configs/qcom_defconfig | 3 +++
> 1 file changed, 3
On 23/10/2019 08:28, Jyri Sarha wrote:
On 22/10/2019 16:22, Roger Quadros wrote:
Based on this GPIO state we need to configure LN10
bit to swap lane0 and lane1 if required (flipped connector).
Type-C companions typically need some time after the cable is
plugged before and before they
пн, 9 сент. 2019 г. в 19:33, Matwey V. Kornilov :
>
> вт, 2 июл. 2019 г. в 20:33, Bin Liu :
> >
> > Matwey,
> >
> > On Tue, Jul 02, 2019 at 08:29:03PM +0300, Matwey V. Kornilov wrote:
> > > Ping?
> >
> > I was offline and just got back. I will review it soon. Sorry for the
> > delay.
>
> Ping?
>
Kishon,
On 23/10/2019 10:36, Kishon Vijay Abraham I wrote:
Roger,
On 22/10/19 6:52 PM, Roger Quadros wrote:
This is required if type C driver needs to hold
global reset on J7ES to perform LN10 swap.
Can you replace "This" with something more specific.
I meant this patch, but I will revise
On Wed 23-10-19 12:44:48, Hillf Danton wrote:
>
> On Tue, 22 Oct 2019 15:58:32 +0200 Michal Hocko wrote:
> >
> > On Tue 22-10-19 21:30:50, Hillf Danton wrote:
[...]
> > > in this RFC after ripping pages off
> > > the first victim, the work finishes with the first ancestor of the victim
> > >
On 23/10/2019 10:45, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/phy/ti/phy-dm816x-usb.c:192:29: warning:
variable phy_data set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
Reviewed-by: Roger
On Wed, Oct 23, 2019 at 03:57:17PM +0800, Yi Wang wrote:
> We get two warnings when build kernel W=1:
> arch/x86/kernel/cpu/mce/amd.c:586:6: warning: no previous prototype for
> ‘disable_err_thresholding’ [-Wmissing-prototypes]
>
> Make the function static to fix this.
>
> Signed-off-by: Yi
Sebastian suggested to try this here:
--- a/drivers/net/usb/lan78xx.c
+++ b/drivers/net/usb/lan78xx.c
@@ -1264,8 +1264,11 @@ static void lan78xx_status(struct lan78xx_net *dev,
struct urb *urb)
netif_dbg(dev, link, dev->net, "PHY INTR: 0x%08x\n", intdata);
Add missing curly brace to charger node example.
Signed-off-by: Matti Vaittinen
---
Resending as I forgot to add the LKML in first attempt. Sorry peeps.
Documentation/devicetree/bindings/mfd/max77693.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed, Oct 23, 2019 at 2:31 PM Mao Wenan wrote:
>
> If SND_SOC_MT8183_MT6358_TS3A227E_MAX98357A=y,
> below errors can be seen:
> sound/soc/codecs/cros_ec_codec.o: In function `send_ec_host_command':
> cros_ec_codec.c:(.text+0x534): undefined reference to
> `cros_ec_cmd_xfer_status'
>
On Tue, Oct 22, 2019 at 08:03:00PM +0200, Geert Uytterhoeven wrote:
> On Tue, Oct 22, 2019 at 7:29 PM Andy Shevchenko
> wrote:
> > Instead of customized approach convert the driver to use bitmap API.
> > #define MAX_BANK 5
> > #define BANK_SZ 8
> > +#define MAX_LINE (MAX_BANK * BANK_SZ)
> In the implementation of ttc_setup_clockevent() release the allocated
> memory for ttcce if clk_notifier_register() fails.
I got other wording preferences. Thus I imagine that such a change
description can still be improved another bit.
Would you like to express the addition of a jump target
Hi,
On 22. 10. 19 10:19, Alvaro Gamez Machado wrote:
> Signed-off-by: Alvaro Gamez Machado
please put there reasonable description to commit message.
> ---
> arch/microblaze/mm/init.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/microblaze/mm/init.c
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c:1221:24: warning: variable adev set but
not used [-Wunused-but-set-variable]
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c:488:24: warning: variable adev set but
not used [-Wunused-but-set-variable]
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c:547:24: warning:
We get two warnings when build kernel W=1:
arch/x86/kernel/cpu/mce/amd.c:586:6: warning: no previous prototype for
‘disable_err_thresholding’ [-Wmissing-prototypes]
Make the function static to fix this.
Signed-off-by: Yi Wang
---
arch/x86/kernel/cpu/mce/amd.c | 2 +-
1 file changed, 1
On Wed, Oct 16, 2019 at 10:22:24AM +0200, Jiri Olsa wrote:
> hi,
> Andi reported that maps cloning is eating lot of memory and
> it's probably unnecessary, because they keep the same data.
>
> This 'maps sharing' seems to save lot of heap for reports with
> many forks/cloned mmaps (over 60% in
drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:4484:6:
warning: variable rate_mask set but not used [-Wunused-but-set-variable]
It is never used since commit a9bb0b515778 ("rtl8xxxu: Improve
TX performance of RTL8723BU on rtl8xxxu driver")
Signed-off-by: YueHaibing
---
On Tue, Oct 22, 2019 at 06:00:06PM -0500, Bjorn Helgaas wrote:
> On Mon, Aug 12, 2019 at 05:31:33PM +0300, Mika Westerberg wrote:
> > If there are more than one PCIe switch with hotplug downstream ports
> > hot-removing them leads to a following deadlock:
> >
> > INFO: task irq/126-pciehp:198
drivers/staging/comedi/drivers/ni_routes.c:52:21: warning:
route_table_size defined but not used [-Wunused-const-variable=]
It is never used since introduction.
Signed-off-by: YueHaibing
---
drivers/staging/comedi/drivers/ni_routes.c | 2 --
1 file changed, 2 deletions(-)
diff --git
Tested-by: kernel test robot
On 10/23/2019 12:46 AM, Vincent Guittot wrote:
The task, for which the scheduler looks for the idlest group of CPUs, must
be discounted from all statistics in order to get a fair comparison
between groups. This includes utilization, load, nr_running and idle_cpus.
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to guarantee hardware behavior. But it could trigger unnecessary
vmexit if kernel is running as guest in virtualization environtment.
If it's in virtualization environment, the deeper C state enter
operation (inb()) will
drivers/staging/comedi/drivers/dt2814.c:193:6:
warning: variable data set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/staging/comedi/drivers/dt2814.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff
> > Wouldn't handle_nested_irq() work here instead of the simple thingy?
>
> Daniel could you try this suggestion? Would it work?
[6.427289] [ cut here ]
[6.431977] kernel BUG at drivers/net/phy/mdio_bus.c:626!
[6.437453] Internal error: Oops - BUG: 0 [#1]
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/phy/ti/phy-dm816x-usb.c:192:29: warning:
variable phy_data set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/phy/ti/phy-dm816x-usb.c | 3 ---
1 file changed, 3
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/net/wireless/atmel/atmel_cs.c:120:21:
warning: variable dev set but not used [-Wunused-but-set-variable]
It is never used, so can remove it.
Signed-off-by: YueHaibing
---
drivers/net/wireless/atmel/atmel_cs.c | 2 --
1 file changed, 2
Fix parameter name in comment and adjust the order.
No functional change.
Signed-off-by: Yi Wang
---
arch/x86/kernel/uprobes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/uprobes.c b/arch/x86/kernel/uprobes.c
index 8cd745e..15e5aad 100644
---
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/net/wireless/admtek/adm8211.c:1784:16:
warning: variable mem_addr set but not used [-Wunused-but-set-variable]
drivers/net/wireless/admtek/adm8211.c:1785:15:
warning: variable io_addr set but not used [-Wunused-but-set-variable]
They are
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/net/usb/lan78xx.c:3995:6: warning:
variable event set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/net/usb/lan78xx.c | 3 ---
1 file changed, 3 deletions(-)
diff
Roger,
On 22/10/19 6:52 PM, Roger Quadros wrote:
> This is required if type C driver needs to hold
> global reset on J7ES to perform LN10 swap.
Can you replace "This" with something more specific.
Thanks
Kishon
>
> Signed-off-by: Roger Quadros
> Signed-off-by: Sekhar Nori
> ---
>
On 23. 10. 19 6:31, Navid Emamdoost wrote:
> In the implementation of ttc_setup_clockevent() release the allocated
> memory for ttcce if clk_notifier_register() fails.
>
> Fixes: 70504f311d4b ("clocksource/drivers/cadence_ttc: Convert init function
> to return error")
> Signed-off-by: Navid
xrun may happen at the end of stream, the
trigger->fsl_esai_trigger_stop maybe called in the middle of
fsl_esai_hw_reset, this may cause esai in wrong state
after stop, and there may be endless xrun interrupt.
So Add spin lock to lock these two function.
Fixes: 7ccafa2b3879 ("ASoC: fsl_esai:
Hi Linus,
please pull,
thx.
---
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
tags/edac_urgent_for_5.4
for you to
On Mon, Oct 21, 2019 at 3:21 AM Peter Zijlstra wrote:
>
> On Thu, Oct 17, 2019 at 05:27:46PM -0700, Stephane Eranian wrote:
> > This patch complements the following commit:
> > 7fa343b7fdc4 ("perf/core: Fix corner case in perf_rotate_context()")
> >
> > The fix from Song addresses the
On Tue, Oct 22, 2019 at 09:11:04PM -0700, Andy Lutomirski wrote:
> Trying again. It looks like I used the wrong address for Pavel.
Thanks for CC Andy! I must confess I didn't dive into userfaultfd engine
personally but let me CC more people involved from criu side. (overquoting
left untouched
On 2019/10/23 下午3:07, Tiwei Bie wrote:
On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote:
On 2019/10/23 上午11:02, Tiwei Bie wrote:
On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote:
On 2019/10/22 下午5:52, Tiwei Bie wrote:
This patch introduces a mdev based hardware vhost
> Add the necessary infrastructure to keep timestamp history of commands,
> events and other useful info for debugging complex issues. This helps in
> diagnosing events leading upto failure.
Why not use tracepoints, for that?
Thanks
Tomas
> Signed-off-by: Can Guo
> ---
>
Hello,
syzbot found the following crash on:
HEAD commit:d72e90f3 Linux 4.18-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104dc65840
kernel config: https://syzkaller.appspot.com/x/.config?x=68af3495408deac5
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:3b7c59a1 Merge tag 'pinctrl-v5.4-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=131abff760
kernel config: https://syzkaller.appspot.com/x/.config?x=420126a10fdda0f1
> In the implementation of ttc_setup_clocksource() when
> clk_notifier_register() fails the execution should go to error handling.
> Additionally, to avoid memory leak the allocated memory for ttccs should
> be released, too.
I got other wording preferences. Thus I imagine that such a change
Hello,
syzbot found the following crash on:
HEAD commit:4f5cafb5 Linux 5.4-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e1d2a0e0
kernel config: https://syzkaller.appspot.com/x/.config?x=de66e73d1c10cebb
dashboard link:
On 10/23/19 4:55 AM, Mike Kravetz wrote:
On 10/22/19 12:09 AM, Piotr Sarna wrote:
On 10/21/19 7:17 PM, Mike Kravetz wrote:
On 10/15/19 4:37 PM, Mike Kravetz wrote:
On 10/15/19 3:50 AM, Michal Hocko wrote:
On Tue 15-10-19 11:01:12, Piotr Sarna wrote:
With hugetlbfs, a common pattern for
Install Intel specific PMU task context synchronization adapter and
extend optimized context switch path with PMU specific task context
synchronization to fix LBR callstack virtualization on context switches.
Signed-off-by: Alexey Budankov
---
arch/x86/events/intel/core.c | 7 +++
Implement intel_pmu_lbr_swap_task_ctx() method updating counters
of the events that requested LBR callstack data on a sample.
The counter can be zero for the case when task context belongs to
a thread that has just come from a block on a futex and the context
contains saved (lbr_stack_state ==
On 22/10/2019 13:23, Nicolas Saenz Julienne wrote:
> On Mon, 2019-10-21 at 16:36 -0400, Qian Cai wrote:
>> I managed to get more information here,
>>
>> [0.00] cma: dma_contiguous_reserve(limit c000)
>> [0.00] cma: dma_contiguous_reserve: reserving 64 MiB for global area
>>
Bridge perf core and x86 swap_task_ctx() method calls.
Signed-off-by: Alexey Budankov
---
arch/x86/events/core.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 7b21455d7504..6e3f0c18908e 100644
--- a/arch/x86/events/core.c
+++
Declare swap_task_ctx() methods at the generic and x86 specific
pmu types to bridge calls to platform specific pmu code on optimized
context switch path between equivalent task perf event contexts.
Signed-off-by: Alexey Budankov
---
arch/x86/events/perf_event.h | 8
On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote:
> On 2019/10/23 上午11:02, Tiwei Bie wrote:
> > On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote:
> > > On 2019/10/22 下午5:52, Tiwei Bie wrote:
> > > > This patch introduces a mdev based hardware vhost backend.
> > > > This backend
1.Add the dmaengine bindings for the X1000 SoC from Ingenic.
2.Add support for probing the dma-jz4780 driver on the
X1000 SoC from Ingenic.
On Mon, Oct 21, 2019 at 3:06 AM Peter Zijlstra wrote:
>
> On Thu, Oct 17, 2019 at 05:27:46PM -0700, Stephane Eranian wrote:
> > @@ -2153,6 +2157,7 @@ __perf_remove_from_context(struct perf_event *event,
> > void *info)
> > {
> > unsigned long flags = (unsigned
Restore Intel LBR call stack from cloned inactive task perf context on
a context switch. This change inherently addresses inconsistency in LBR
call stack data provided on a sample in record profiling mode:
$ perf record -N -B -T -R --call-graph lbr \
-e
On 22/10/2019 17.01, Christophe Leroy wrote:
>
>
> On 10/18/2019 12:52 PM, Rasmus Villemoes wrote:
>> In preparation for allowing to build QE support for architectures
>> other than PPC, replace the ppc-specific io accessors. Done via
>>
>
> This patch is not transparent in terms of
The auto string detection algorithm checks if the current WLED
sink configuration is valid. It tries enabling every sink and
checks if the OVP fault is observed. Based on this information
it detects and enables the valid sink configuration.
Auto calibration will be triggered when the OVP fault
From: Lars-Peter Clausen
On some platforms the adp5589 is used in GPIO only mode. On these platforms
we do not want to register a input device, so make that optional and only
create the input device if a keymap is supplied.
Signed-off-by: Lars-Peter Clausen
Signed-off-by: Alexandru Ardelean
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/net/ieee802154/cc2520.c:221:5: warning:
variable status set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/net/ieee802154/cc2520.c | 3 ---
1 file changed, 3
Hi Vinod,
On 2019年10月23日 13:15, Vinod Koul wrote:
On 23-10-19, 11:05, Zhou Yanjie wrote:
1.Add the DMA bindings for the X1000 SoC from Ingenic.
2.Add support for probing the dma-jz4780 driver on the
X1000 SoC from Ingenic.
The subsystem in dmaengine and not dma
Please resend with correct
Add the dmaengine bindings for the X1000 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
---
.../devicetree/bindings/dma/jz4780-dma.txt | 3 +-
include/dt-bindings/dma/x1000-dma.h| 40 ++
2 files changed, 42 insertions(+), 1 deletion(-)
create mode
Add support for probing the dma-jz4780 driver on the X1000 Soc.
Signed-off-by: Zhou Yanjie
---
drivers/dma/dma-jz4780.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c
index cafb1cc0..f809a6e 100644
--- a/drivers/dma/dma-jz4780.c
This change documents the CS setup, host & inactive times. They were
omitted when the fields were added, and were caught by one of the build
bots.
Fixes: 25093bdeb6bc ("spi: implement SW control for CS times")
Reported-by: kbuild test robot
Signed-off-by: Alexandru Ardelean
---
On Tue 22-10-19 16:15:18, Johannes Weiner wrote:
> Setting a memory.high limit below the usage makes almost no effort to
> shrink the cgroup to the new target size.
>
> While memory.high is a "soft" limit that isn't supposed to cause OOM
> situations, we should still try harder to meet a user
Hi Geert,
On 2019/10/23 14:44, Geert Uytterhoeven wrote:
> On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
> wrote:
>> +Cc: Mark Salyzyn
>>
>> There is a compiler failure on arm64 platform, as follow:
>> zhangshaokun@ubuntu:~/linux-next$ make -j64
>> CALLscripts/atomic/check-atomics.sh
>>
On 10/22/19 11:44 PM, Geert Uytterhoeven wrote:
> On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
> wrote:
>> +Cc: Mark Salyzyn
>>
>> There is a compiler failure on arm64 platform, as follow:
>> zhangshaokun@ubuntu:~/linux-next$ make -j64
>> CALLscripts/atomic/check-atomics.sh
>> CC
Sehr geehrter Herr / Frau,
Bitte verzeihen Sie mir, wenn meine Anfrage von Ihrer freundlichen
Person nicht akzeptiert wird. Ich bin Aisha Al-Qaddafi; Ich bin die
einzige leibliche Tochter meines verstorbenen Vaters (Oberst Muammar
Gaddafi, der der frühere libysche Präsident war).
Ich bitte um
Hi Rob,
On Tue, Oct 22, 2019 at 11:17:35AM -0500, Rob Herring wrote:
> On Mon, Oct 7, 2019 at 5:48 AM Maxime Ripard wrote:
> >
> > On Mon, Oct 07, 2019 at 03:45:29PM +0530, Amit Kucheria wrote:
> > > On Mon, Oct 7, 2019 at 3:35 PM Maxime Ripard wrote:
> > > >
> > > > On Sat, Oct 05, 2019 at
On Tue 22-10-19 16:15:17, Johannes Weiner wrote:
> When the reclaim loop in memory_max_write() is ^C'd or similar, we set
> err to -EINTR. But we don't return err. Once the limit is set, we
> always return success (nbytes). Delete the dead code.
>
> Signed-off-by: Johannes Weiner
Acked-by:
Hi Mike,
On Wed, Oct 23, 2019 at 12:36:39AM +0100, Mike Leach wrote:
> Hi Leo,
>
> Two points here - both related.
>
> On Tue, 22 Oct 2019 at 06:10, Leo Yan wrote:
> >
> > Hi Mathieu,
> >
> > On Fri, Oct 11, 2019 at 02:16:06PM -0600, Mathieu Poirier wrote:
> > > On Sat, Oct 05, 2019 at
On Wed, 23 Oct 2019, Anup Patel wrote:
> On Wed, Oct 23, 2019 at 11:30 AM Paul Walmsley
> wrote:
>
> > Is drivers/platform/goldfish/goldfish_pipe.c required for the Goldfish RTC
> > driver or not?
>
> No, it's not required.
>
> > If not, then the first patch that was sent isn't the right fix.
On Wed, 2019-10-23 at 14:34 +0800, Anson Huang wrote:
> Machine compatible string normally is located in board DT, remove
> the duplicated one from SoC dtsi.
>
> Signed-off-by: Anson Huang
Reviewed-by: Daniel Baluta
> ---
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 -
> 1 file changed, 1
On Wed, 2019-10-23 at 14:34 +0800, Anson Huang wrote:
> Machine compatible string normally is located in board DT, remove
> the duplicated one from SoC dtsi.
>
> Signed-off-by: Anson Huang
Reviewed-by: Daniel Baluta
> ---
> arch/arm64/boot/dts/freescale/imx8mn.dtsi | 1 -
> 1 file changed, 1
On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
wrote:
> +Cc: Mark Salyzyn
>
> There is a compiler failure on arm64 platform, as follow:
> zhangshaokun@ubuntu:~/linux-next$ make -j64
> CALLscripts/atomic/check-atomics.sh
> CC arch/arm64/kernel/asm-offsets.s
> In file included from
On Tue 22-10-19 19:37:08, Johannes Weiner wrote:
> While upgrading from 4.16 to 5.2, we noticed these allocation errors
> in the log of the new kernel:
>
> [ 8642.253395] SLUB: Unable to allocate memory on node -1,
> gfp=0xa20(GFP_ATOMIC)
> [ 8642.269170] cache: tw_sock_TCPv6(960:helper-logs),
On Tue, Oct 22, 2019 at 11:46 PM Mark Salyzyn wrote:
>
> Check impure, opaque, origin & meta xattr with no sepolicy audit
> (using __vfs_getxattr) since these operations are internal to
> overlayfs operations and do not disclose any data. This became
> an issue for credential override off since
On 2019/10/23 下午2:19, Zhu, Lingshan wrote:
On 10/22/2019 9:05 PM, Jason Wang wrote:
On 2019/10/22 下午2:53, Zhu Lingshan wrote:
On 10/21/2019 6:19 PM, Jason Wang wrote:
On 2019/10/21 下午5:53, Zhu, Lingshan wrote:
On 10/16/2019 6:19 PM, Jason Wang wrote:
On 2019/10/16 上午9:30, Zhu
Machine compatible string normally is located in board DT, remove
the duplicated one from SoC dtsi.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi
Machine compatible string normally is located in board DT, remove
the duplicated one from SoC dtsi.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mn.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi
From: Eric Long
The Spreadtrum Audio compress offload mode will use 2-stage DMA transfer
to save power. That means we can request 2 dma channels, one for source
channel, and another one for destination channel. Once the source channel's
transaction is done, it will trigger the destination
If SND_SOC_MT8183_MT6358_TS3A227E_MAX98357A=y,
below errors can be seen:
sound/soc/codecs/cros_ec_codec.o: In function `send_ec_host_command':
cros_ec_codec.c:(.text+0x534): undefined reference to `cros_ec_cmd_xfer_status'
cros_ec_codec.c:(.text+0x101c): undefined reference to
No functional change.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_plane.c | 36 +++---
1 file changed, 21 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c
b/drivers/gpu/drm/virtio/virtgpu_plane.c
index
Be consistent with the rest of the code base.
No functional change.
v2:
- fix sparse warnings for virtio_gpu_cmd_transfer_to_host_2d call.
- move convert_to_hw_box helper function.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 5 +++--
fs/fuse/virtio_fs.c:983:20: warning:
variable fc set but not used [-Wunused-but-set-variable]
It is not used since commit 7ee1e2e631db ("virtiofs:
No need to check fpq->connected state")
Signed-off-by: YueHaibing
---
fs/fuse/virtio_fs.c | 2 --
1 file changed, 2 deletions(-)
diff --git
Hi
>
> On Thu, Oct 17, 2019 at 02:21:08PM +0800, Shengjiu Wang wrote:
> > For P2P output, the output divider should align with the output sample
>
> I think we should avoid "P2P" (or "M2M") keyword in the mainline code as
> we know M2M will never get merged while somebody working with the
>
On Sat, 21 Sep 2019 at 16:47, Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sat, 21 Sep 2019 18:32:46 +0200
>
> Simplify this function implementation by using a known wrapper function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
On 10/22/2019 9:05 PM, Jason Wang wrote:
On 2019/10/22 下午2:53, Zhu Lingshan wrote:
On 10/21/2019 6:19 PM, Jason Wang wrote:
On 2019/10/21 下午5:53, Zhu, Lingshan wrote:
On 10/16/2019 6:19 PM, Jason Wang wrote:
On 2019/10/16 上午9:30, Zhu Lingshan wrote:
This commit introduced IFC VF
On Tue 22-10-19 14:59:02, Andrew Morton wrote:
> On Tue, 22 Oct 2019 12:21:56 -0400 Waiman Long wrote:
[...]
> > - for (mtype = 0; mtype < MIGRATE_TYPES; mtype++) {
> > - seq_printf(m, "Node %4d, zone %8s, type %12s ",
> > - pgdat->node_id,
> > -
On Wed, Oct 23, 2019 at 11:30 AM Paul Walmsley wrote:
>
> On Wed, 23 Oct 2019, Anup Patel wrote:
>
> > On Wed, Oct 23, 2019 at 6:37 AM Paul Walmsley
> > wrote:
> >
> > > Incidentally, just looking at drivers/platform/goldfish, that driver seems
> > > to be some sort of Google-specific RPC
+Cc: Mark Salyzyn
There is a compiler failure on arm64 platform, as follow:
zhangshaokun@ubuntu:~/linux-next$ make -j64
CALLscripts/atomic/check-atomics.sh
CC arch/arm64/kernel/asm-offsets.s
In file included from ./include/linux/sysctl.h:30:0,
from
On Wed, 23 Oct 2019, Anup Patel wrote:
> On Wed, Oct 23, 2019 at 6:37 AM Paul Walmsley
> wrote:
>
> > Incidentally, just looking at drivers/platform/goldfish, that driver seems
> > to be some sort of Google-specific RPC driver. Are you all really sure
>
> Nopes, it's not RPC driver. In fact,
701 - 795 of 795 matches
Mail list logo