On Tue, Jul 07, 2020 at 06:43:35PM +0100, Marc Zyngier wrote:
> On 2020-07-07 18:36, Catalin Marinas wrote:
> > On Mon, Jun 01, 2020 at 10:47:13PM +0800, Zhenyu Ye wrote:
> > > @@ -59,6 +69,47 @@
> > > __ta; \
> > > })
> > >
> > > +/*
> > > +
On Mon, Jul 06, 2020 at 09:27:04AM +0530, Anshuman Khandual wrote:
> On 07/02/2020 05:41 PM, Catalin Marinas wrote:
> > On Mon, Jun 15, 2020 at 06:45:17PM +0530, Anshuman Khandual wrote:
> >> --- a/arch/arm64/include/asm/pgtable.h
> >> +++ b/arch/arm64/include/asm/pgtable.h
> >> @@ -353,15 +353,92
On 2020-07-07 18:36, Catalin Marinas wrote:
On Mon, Jun 01, 2020 at 10:47:13PM +0800, Zhenyu Ye wrote:
@@ -59,6 +69,47 @@
__ta; \
})
+/*
+ * __TG defines translation granule of the system, which is decided
by
+ * PAGE_SHIFT.
On Thu, Jul 02, 2020 at 11:18:03AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky
>
> Over the years, the main.c file grew above all imagination and was >8K
> LOC of the code. This caused to a huge burden while I started to work on
> ib_flow allocation patches.
>
> This series implements
Hi, Pratyush,
On 6/23/20 9:30 PM, Pratyush Yadav wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Double Transfer Rate (DTR) is SPI protocol in which data is transferred
> on each clock edge as opposed to on each clock cycle. Make
>
charge_slab_page() and uncharge_slab_page() are not related anymore
to memcg charging and uncharging. In order to make their names
less confusing, let's rename them to account_slab_page() and
unaccount_slab_page() respectively.
Signed-off-by: Roman Gushchin
---
mm/slab.c | 4 ++--
mm/slab.h | 8
charge_slab_page() is not using the gfp argument anymore,
remove it.
Signed-off-by: Roman Gushchin
---
mm/slab.c | 2 +-
mm/slab.h | 3 +--
mm/slub.c | 2 +-
3 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index 2850fe3c5fb8..fafd46877504 100644
---
Currently memcg_kmem_enabled() is optimized for the kernel memory
accounting being off. It was so for a long time, and arguably the
reason behind was that the kernel memory accounting was initially an
opt-in feature. However, now it's on by default on both cgroup v1
and cgroup v2, and it's on for
On 7/7/20 10:33 AM, Eric Dumazet wrote:
>
>
> What happens after this monitoring is started, then the admin does :
>
> rmmod ifb
>
I meant : rmmod dummy
On Mon, Jun 01, 2020 at 10:47:13PM +0800, Zhenyu Ye wrote:
> @@ -59,6 +69,47 @@
> __ta; \
> })
>
> +/*
> + * __TG defines translation granule of the system, which is decided by
> + * PAGE_SHIFT. Used by TTL.
> + * - 4KB: 1
> + *
On Mon, Jul 06, 2020 at 02:06:45PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 02, 2020 at 10:19:08PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2020-07-02 09:48:26 [-0700], Paul E. McKenney wrote:
> > > On Thu, Jul 02, 2020 at 04:12:16PM +0200, Sebastian Andrzej Siewior wrote:
> > > > On
On Sat, Apr 25, 2020 at 07:26:41PM -0700, Jonathan Bakker wrote:
> From: Tomasz Figa
>
> On FIMC variants which don't have writeback channel, there is no need to
> access system registers. This patch makes the driver request sysreg
> regmap conditionally depending on whether writeback is
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On 7/7/20 10:15 AM, izabela.bakoll...@gmail.com wrote:
> From: Izabela Bakollari
>
> Dropwatch is a utility that monitors dropped frames by having userspace
> record them over the dropwatch protocol over a file. This augument
> allows live monitoring of dropped frames using tools like
On Sat, Apr 25, 2020 at 07:26:40PM -0700, Jonathan Bakker wrote:
> The S5PV210 platform only supports device tree based booting
> where the FIMC variant data is parsed directly from
> the device tree, hence the now unused static data can be removed.
>
> Signed-off-by: Jonathan Bakker
> ---
>
On Tue, Jul 07, 2020 at 01:29:30PM -0400, Sasha Levin wrote:
> On Tue, Jul 07, 2020 at 01:20:51PM -0400, Sasha Levin wrote:
> > On Tue, Jul 07, 2020 at 11:31:22AM -0400, J. Bruce Fields wrote:
> > > NACK.
> > >
> > > (How did this one even end up headed for stable? It wasn't cc'd to
> >
> > It
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On Tue, 7 Jul 2020 10:17:25 -0700 Nick Desaulniers wrote:
> On Tue, Jul 7, 2020 at 9:56 AM Jakub Kicinski wrote:
> >
> > > On Tue, Jul 07, 2020 at 08:51:07AM -0700, Sami Tolvanen wrote:
> > > > After spending some time debugging this with Nick, it looks like the
> > > > error is caused by a
Hi Akshu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on linus/master v5.8-rc4 next-20200707]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented
On Tue, Jul 07, 2020 at 01:20:51PM -0400, Sasha Levin wrote:
On Tue, Jul 07, 2020 at 11:31:22AM -0400, J. Bruce Fields wrote:
NACK.
(How did this one even end up headed for stable? It wasn't cc'd to
It came in when I was looking at the later nfs patches in this series
and figured it is a
Udev rules that depend on the power/wakeup attribute don't get triggered
correctly if device_set_wakeup_capable is called after the device is
created. This can happen for several reasons (driver sets wakeup after
device is created, wakeup is changed on parent device, etc) and it seems
reasonable
Hi linux-pm,
ChromeOS has a udev rule to chown the `power/wakeup` attribute so that
the power manager can modify it during runtime.
(https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/platform2/power_manager/udev/99-powerd-permissions.rules)
In our automated tests, we
On Tue, Jul 07, 2020 at 02:35:59PM +0300, Maxim Levitsky wrote:
> On Tue, 2020-07-07 at 01:14 -0700, Sean Christopherson wrote:
> > Aren't you supposed to be on vacation? :-)
> >
> > On Tue, Jul 07, 2020 at 10:04:22AM +0200, Paolo Bonzini wrote:
> > > On 07/07/20 08:11, Sean Christopherson wrote:
On Mon, Jul 6, 2020 at 6:17 PM Qian Cai wrote:
>
> On Mon, Jul 06, 2020 at 05:48:21PM -0500, Uriel Guajardo wrote:
> > On Mon, Jul 6, 2020 at 4:39 PM Qian Cai wrote:
> > >
> > > On Mon, Jul 06, 2020 at 09:13:09PM +, Uriel Guajardo wrote:
> > > > From: Uriel Guajardo
> > > >
> > > >
On 07/07/20 13:30, Maxim Levitsky wrote:
>> Somehwat crazy idea inbound... rather than calculating the valid bits in
>> software, what if we throw the value at the CPU and see if it fails? At
>> least that way the host and guest are subject to the same rules. E.g.
>>
>> ---
On 07/07/20 13:35, Maxim Levitsky wrote:
> After thinking about this, I am thinking that we should apply similiar logic
> as done with the 'cpu-pm' related features.
> This way the user can choose between passing through the IA32_SPEC_CTRL,
> (and in this case, we can since the user choose it,
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On Tue, Jul 07, 2020 at 11:31:22AM -0400, J. Bruce Fields wrote:
NACK.
(How did this one even end up headed for stable? It wasn't cc'd to
It came in when I was looking at the later nfs patches in this series
and figured it is a fix on its own.
stable, it's not a bugfix, and it's not a
On 07.07.2020 17:55, Alexey Budankov wrote:
>
> On 07.07.2020 17:23, Jiri Olsa wrote:
>> On Tue, Jul 07, 2020 at 04:24:28PM +0300, Alexey Budankov wrote:
>>>
>>> On 07.07.2020 16:14, Jiri Olsa wrote:
On Tue, Jul 07, 2020 at 04:07:42PM +0300, Alexey Budankov wrote:
>
> On 06.07.2020
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On Tue, Jul 7, 2020 at 10:39 AM Florian Fainelli wrote:
>
>
>
> On 7/7/2020 7:54 AM, Maxime Ripard wrote:
> > Hi Andrew,
> >
> > On Tue, Jul 07, 2020 at 04:19:18PM +0200, Andrew Lunn wrote:
> >> On Mon, Jul 06, 2020 at 08:13:31PM +0200, Maxime Ripard wrote:
> >>> I came across an issue today on
If we have a per CE (Copy Engine) IRQ then we have no summary
register. Right now the code generates a summary register by
iterating over all copy engines and seeing if they have an interrupt
pending.
This has a problem. Specifically if _none_ if the Copy Engines have
an interrupt pending then
Sounds good to me. Patch v5 incoming after compile-test.
Thanks
Abhishek
On Tue, Jul 7, 2020 at 10:16 AM Rafael J. Wysocki wrote:
>
> On Tue, Jul 7, 2020 at 6:48 PM Abhishek Pandit-Subedi
> wrote:
> >
> > Hi Rafael,
> >
> > (resent in plain text)
> >
> > On Tue, Jul 7, 2020 at 9:28 AM Rafael
On Tue, Jul 7, 2020 at 9:56 AM Jakub Kicinski wrote:
>
> > On Tue, Jul 07, 2020 at 08:51:07AM -0700, Sami Tolvanen wrote:
> > > After spending some time debugging this with Nick, it looks like the
> > > error is caused by a recent optimization change in LLVM, which together
> > > with the
On Tue, Jul 7, 2020 at 6:48 PM Abhishek Pandit-Subedi
wrote:
>
> Hi Rafael,
>
> (resent in plain text)
>
> On Tue, Jul 7, 2020 at 9:28 AM Rafael J. Wysocki wrote:
> >
> > On Tue, Jul 7, 2020 at 6:24 PM Abhishek Pandit-Subedi
> > wrote:
> > >
> > > Udev rules that depend on the power/wakeup
On 07.07.20 18:32, Mike Rapoport wrote:
> From: Mike Rapoport
>
> 'addr' is set to 'start' and then a few lines afterwards 'start' is
> set to 'addr'.
> Remove the second asignment.
>
> Fixes: 2ba3e6947aed ("mm/vmalloc: track which page-table levels were
> modified")
> Signed-off-by: Mike
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
Add the s390 idle functions so they don't show up in top when
using software sampling.
Signed-off-by: Sven Schnelle
---
tools/perf/util/symbol.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
index 5ddf84dcbae7..d33d24c61d24 100644
---
Testing:
echo 16250 > temp2_offset
cat temp2_offset
16250
echo 17500 > temp3_offset
cat temp3_offset
17500
cat temp4_offset
0
cat temp2_offset
17500
echo 0 > temp2_offset
cat temp2_offset
0
cat temp3_offset
17500
echo -0 > temp2_offset
cat temp2_offset
0
echo -10 > temp2_offset
cat
From: Izabela Bakollari
Dropwatch is a utility that monitors dropped frames by having userspace
record them over the dropwatch protocol over a file. This augument
allows live monitoring of dropped frames using tools like tcpdump.
With this feature, dropwatch allows two additional commands
On the embedded world, the complexity of the SoC leads to an
increasing number of hotspots which need to be monitored and mitigated
as a whole in order to prevent the temperature to go above the
normative and legally stated 'skin temperature'.
Another aspect is to sustain the performance for a
On Sat, Jun 27, 2020 at 11:08:39PM -0700, Eric Biggers wrote:
> This series fixes all syzbot bugs in the minix filesystem:
>
> KASAN: null-ptr-deref Write in get_block
> KASAN: use-after-free Write in get_block
> KASAN: use-after-free Read in get_block
> WARNING in
Christian Brauner writes:
> On Fri, Jul 03, 2020 at 04:37:47PM -0500, Eric W. Biederman wrote:
>> Alexei Starovoitov writes:
>>
>> > On Thu, Jul 02, 2020 at 11:41:37AM -0500, Eric W. Biederman wrote:
>> >> Create an independent helper thread_group_exited report return true
>> >> when all
Hi Kees,
You and others are certainly more experts in the filesystem and security
infrastructure of the kernel.
What I am trying to accomplish is a simple operation:
request part of a file into a buffer rather than the whole file.
If someone could add such support I would be more than happy to
On 2020-07-06 10:47, Mathieu Poirier wrote:
On Mon, Jun 29, 2020 at 01:02:12PM -0700, Rishabh Bhatnagar wrote:
The current coredump implementation uses vmalloc area to copy
all the segments. But this might put strain on low memory targets
as the firmware size sometimes is in tens of MBs. The
On Tue, Jul 07, 2020 at 08:09:07PM +0300, Sergey Organov wrote:
> Vladimir Oltean writes:
>
> > On Tue, Jul 07, 2020 at 07:07:08PM +0300, Sergey Organov wrote:
> >> Vladimir Oltean writes:
> >> >
> >> > What do you mean 'no ticking', and what do you mean by 'non-initialized
> >> > clock'
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On 7/7/20 1:08 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200706:
>
on i386:
when CONFIG_ACPI is not set/enabled:
../drivers/scsi/lpfc/lpfc_init.c:1265:15: error: implicit declaration of
function 'get_cpu_idle_time'; did you mean 'get_cpu_device'?
Vladimir Oltean writes:
> On Tue, Jul 07, 2020 at 07:07:08PM +0300, Sergey Organov wrote:
>> Vladimir Oltean writes:
>> >
>> > What do you mean 'no ticking', and what do you mean by 'non-initialized
>> > clock' exactly? I don't know if the fec driver is special in any way, do
>> > you mean that
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On Tue, Jul 7, 2020 at 5:14 AM Michal Hocko wrote:
>
> On Fri 03-07-20 07:23:14, Shakeel Butt wrote:
> > On Thu, Jul 2, 2020 at 11:35 PM Michal Hocko wrote:
> > >
> > > On Thu 02-07-20 08:22:22, Shakeel Butt wrote:
> > > [...]
> > > > Interface options:
> > > > --
> > > >
> > > >
On 7/7/2020 8:00 AM, Colin King wrote:
From: Colin Ian King
Fix smatch warning:
drivers/scsi/lpfc/lpfc_sli.c:15156 lpfc_cq_poll_hdler() warn: inconsistent
indenting
Signed-off-by: Colin Ian King
---
drivers/scsi/lpfc/lpfc_sli.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Hello,
this is v7 of a series adding support for tty triggers. See patch 3 for
how to use it. The first two patches provide the necessary
infrastructure in the tty subsystem to make the trigger possible.
Changes compared to v6 sent with Message-Id:
20200213091600.554-1-...@kleine-koenig.org on
Usage is as follows:
myled=ledname
tty=ttyS0
echo tty > /sys/class/leds/$myled/trigger
echo $tty > /sys/class/leds/$myled/ttyname
. When this new trigger is active it periodically checks the tty's
statistics and when it changed since the last check the led is
For a given struct tty_struct this yields the corresponding statistics
about sent and received characters (and some more) which is needed to
implement an LED trigger for tty devices.
The new function is then used to simplify tty_tiocgicount().
Signed-off-by: Uwe Kleine-König
---
Introduce a new function tty_kopen_shared() that yields a struct
tty_struct. The semantic difference to tty_kopen() is that the tty is
expected to be used already. So rename tty_kopen() to
tty_kopen_exclusive() for clearness, adapt the single user and put the
common code in a new static helper
On Tue, 7 Jul 2020 09:05:28 -0700 Sami Tolvanen wrote:
> On Tue, Jul 07, 2020 at 08:51:07AM -0700, Sami Tolvanen wrote:
> > After spending some time debugging this with Nick, it looks like the
> > error is caused by a recent optimization change in LLVM, which together
> > with the inlining of
Hi!
> @@ -234,6 +234,7 @@ static const char * const pm_tests[__TEST_AFTER_LAST] = {
> [TEST_PLATFORM] = "platform",
> [TEST_DEVICES] = "devices",
> [TEST_FREEZER] = "freezer",
> + [TEST_MEM_QUIET] = "mem-quiet",
> };
>
This adds field to sysfs interface, right? I guess we
On Tue, Jul 7, 2020 at 3:34 AM Christoph Hellwig wrote:
>
> On Thu, Jul 02, 2020 at 04:25:41PM -0700, Song Liu wrote:
> > Hi Christoph,
> >
> > On Mon, Jun 15, 2020 at 5:53 AM Christoph Hellwig wrote:
> > >
> > > The only caller of the bstat function becomes cleaner and simpler when
> > > open
On Tue, Jul 7, 2020 at 3:26 AM Maxime Ripard wrote:
>
> If the DSI driver is the last to probe, component_add will try to run all
> the bind callbacks straight away and return the error code.
>
> However, since we depend on a power domain, we're pretty much guaranteed to
> be in that case on the
Hi Rafael,
(resent in plain text)
On Tue, Jul 7, 2020 at 9:28 AM Rafael J. Wysocki wrote:
>
> On Tue, Jul 7, 2020 at 6:24 PM Abhishek Pandit-Subedi
> wrote:
> >
> > Udev rules that depend on the power/wakeup attribute don't get triggered
> > correctly if device_set_wakeup_capable is called
On 07.07.2020 19:05, Jiri Olsa wrote:
> On Tue, Jul 07, 2020 at 05:55:14PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> process_evlist() now looks suboptimal since record mode code directly calls
>> evlist__ctlfd_process()
>> and then handles returned command specifically to the mode. So in
On Mon, Jul 06, 2020 at 11:13:16AM +0800, Neal Liu wrote:
> Control Flow Integrity(CFI) is a security mechanism that disallows
> changes to the original control flow graph of a compiled binary,
> making it significantly harder to perform such attacks.
>
> init_state_node() assign same function
On Tue, Jul 07, 2020 at 07:07:08PM +0300, Sergey Organov wrote:
> Vladimir Oltean writes:
> >
> > What do you mean 'no ticking', and what do you mean by 'non-initialized
> > clock' exactly? I don't know if the fec driver is special in any way, do
> > you mean that multiple runs of $(phc_ctl
On 2020-07-07 1:19 a.m., Kees Cook wrote:
FIRMWARE_PREALLOC_BUFFER is a "how", not a "what", and confuses the LSMs
that are interested in filtering between types of things. The "how"
should be an internal detail made uninteresting to the LSMs.
Fixes: a098ecd2fa7d ("firmware: support loading
Am Di., 7. Juli 2020 um 17:32 Uhr schrieb Nick Terrell :
>
>
>
> > On Jul 7, 2020, at 3:19 AM, Norbert Lange wrote:
> >
> > Thanks for the respin.
> >
> > Am Di., 7. Juli 2020 um 05:51 Uhr schrieb Nick Terrell
> > :
> >>
> >> From: Nick Terrell
> >>
> >> * Adds the zstd cmd to
On 7/7/2020 7:54 AM, Maxime Ripard wrote:
> Hi Andrew,
>
> On Tue, Jul 07, 2020 at 04:19:18PM +0200, Andrew Lunn wrote:
>> On Mon, Jul 06, 2020 at 08:13:31PM +0200, Maxime Ripard wrote:
>>> I came across an issue today on an Allwinner board, but I believe it's a
>>> core issue.
>>>
>>> That
use flags set by asm-dais directly!
This will be useful gapless case where write needs a special flag to indicate
that last buffer.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Add length to write command packet token so that we can track exactly
how many bytes are consumed by DSP in the command reply.
This is useful in some use-cases where the end of the file/stream
is not aligned with period size.
Signed-off-by: Srinivas Kandagatla
---
This patch adds support to metadata required to do a gapless playback.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/sound/soc/qcom/qdsp6/q6asm-dai.c b/sound/soc/qcom/qdsp6/q6asm-dai.c
index
Add support to gapless playback by implementing metadata,
next_track, drain and partial drain support.
Gapless on Q6ASM is implemented by opening 2 streams in a single asm stream
and toggling them on next track.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 212
During gapless playback, its possible for previous track to
end at unaligned boundary, starting next track on the same
boundary can lead to unaligned address exception in dsp.
So implement copy callback for finer control on the buffer offsets.
Signed-off-by: Srinivas Kandagatla
---
This patch adds support to gapless flag to q6asm_open_write().
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 4 ++--
sound/soc/qcom/qdsp6/q6asm.c | 4 +++-
sound/soc/qcom/qdsp6/q6asm.h | 2 +-
3 files changed, 6 insertions(+), 4 deletions(-)
diff --git
Change logging of warnings to drm_warn() form dev_warn().
Signed-off-by: Suraj Upadhyay
---
drivers/gpu/drm/drm_edid.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 31496b6cfc56..ad7a1f9817ed 100644
---
Change logging information from dev_info() to drm_info().
Signed-off-by: Suraj Upadhyay
---
drivers/gpu/drm/drm_fb_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
index 5609e164805f..88146f7245c5
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm-dai.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/sound/soc/qcom/qdsp6/q6asm-dai.c b/sound/soc/qcom/qdsp6/q6asm-dai.c
index c0e1e84267bf..c4b4684b7824 100644
---
This patchset adds gapless compressed audio support on q6asm.
Gapless on q6asm is implemented using 2 streams in a single asm session.
First few patches are enhacements done to q6asm interface to allow
stream id per each command, gapless flags and silence meta data.
Along with this there are few
Each q6asm session can have multiple streams, mixing usage of these
names in variable are bit misleading to reader, so rename them accordingly.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
This patch adds support to ASM_DATA_CMD_REMOVE_INITIAL_SILENCE
and ASM_DATA_CMD_REMOVE_TRAILING_SILENCE asm command to support
compressed metadata for gapless playback.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm.c | 53
Make the error reporting more useful by adding opcode to it.
Without this its almost impossible to say which command actually
timed out.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/qdsp6/q6asm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Each ASM session can have multiple streams attached to it,
current design was to allow only one static stream id 1 per each session.
However for use-case like gapless, we would need 2 streams to open per session.
This patch converts all the asm apis to take stream id as argument
to allow multiple
Convert logging of errors once from dev_err_once() to drm_err_once().
Signed-off-by: Suraj Upadhyay
---
drivers/gpu/drm/drm_mipi_dbi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_mipi_dbi.c b/drivers/gpu/drm/drm_mipi_dbi.c
index
On Mon, Jul 6, 2020 at 7:21 PM Cathy Zhang wrote:
>
> This instruction gives software a way to force the processor to complete
> all modifications to flags, registers and memory from previous instructions
> and drain all buffered writes to memory before the next instruction is
> fetched and
Commit f566e1fbadb6 ("kbuild: make multiple directory targets work")
broke single target builds for external modules. Fix this.
Fixes: f566e1fbadb6 ("kbuild: make multiple directory targets work")
Reported-by: Bjørn Mork
Signed-off-by: Masahiro Yamada
---
Makefile | 2 +-
1 file changed, 1
This patchset converts logging to drm_* functions in drm core.
The following functions have been converted to their respective
DRM alternatives :
dev_info() --> drm_info()
dev_err() --> drm_err()
dev_warn() --> drm_warn()
dev_err_once() --> drm_err_once().
Suraj Upadhyay (4):
On 7/7/20 9:44 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> There is a well-defined standard migration target callback. Use it
> directly.
>
> Signed-off-by: Joonsoo Kim
Acked-by: Vlastimil Babka
> ---
> mm/memory-failure.c | 18 ++
> 1 file changed, 6 insertions(+),
On 7/7/20 9:44 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> To calculate the correct node to migrate the page for hotplug, we need
> to check node id of the page. Wrapper for alloc_migration_target() exists
> for this purpose.
>
> However, Vlastimil informs that all migration source
On 7/7/20 9:44 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> There are some similar functions for migration target allocation. Since
> there is no fundamental difference, it's better to keep just one rather
> than keeping all variants. This patch implements base migration target
>
On 7/7/20 1:48 PM, Michal Hocko wrote:
> On Tue 07-07-20 16:44:48, Joonsoo Kim wrote:
>> From: Joonsoo Kim
>>
>> There is a well-defined standard migration target callback. Use it
>> directly.
>>
>> Signed-off-by: Joonsoo Kim
>> ---
>> mm/memory-failure.c | 18 ++
>> 1 file
From: Mike Rapoport
'addr' is set to 'start' and then a few lines afterwards 'start' is
set to 'addr'.
Remove the second asignment.
Fixes: 2ba3e6947aed ("mm/vmalloc: track which page-table levels were modified")
Signed-off-by: Mike Rapoport
---
mm/vmalloc.c | 1 -
1 file changed, 1
On Tue, Jul 7, 2020 at 4:08 PM Joakim Tjernlund
wrote:
>
> Maintainer ping ?
Whoops. Applied for fixes.
--
Thanks,
//richard
Convert logging errors from dev_err() to drm_err().
Signed-off-by: Suraj Upadhyay
---
drivers/gpu/drm/drm_mipi_dsi.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_dsi.c
index
On Tue, Jul 7, 2020 at 6:24 PM Abhishek Pandit-Subedi
wrote:
>
> Udev rules that depend on the power/wakeup attribute don't get triggered
> correctly if device_set_wakeup_capable is called after the device is
> created. This can happen for several reasons (driver sets wakeup after
> device is
Built and tested on Chromebook w/ 5.4 kernel.
Sorry about the churn -- will start building with warnings = errors
before I send patches upstream.
Thanks
Abhishek
On Tue, Jul 7, 2020 at 9:24 AM Abhishek Pandit-Subedi
wrote:
>
> Udev rules that depend on the power/wakeup attribute don't get
On Tue, Jul 07, 2020 at 05:51:48PM +0200, Dmitry Vyukov wrote:
> On Sat, Jul 4, 2020 at 8:34 PM Dmitry Vyukov wrote:
> >
> > On Sat, Jul 4, 2020 at 6:45 PM Paul E. McKenney wrote:
> > >
> > > On Fri, Jul 03, 2020 at 04:31:22PM -0700, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot found the
Em Sat, Jun 27, 2020 at 09:36:44PM +0800, Changbin Du escreveu:
> We will reuse this function later.
>
> Signed-off-by: Changbin Du
> ---
> tools/perf/builtin-ftrace.c | 17 -
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/builtin-ftrace.c
Hi linux-pm,
ChromeOS has a udev rule to chown the `power/wakeup` attribute so that
the power manager can modify it during runtime.
(https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/platform2/power_manager/udev/99-powerd-permissions.rules)
In our automated tests, we
Udev rules that depend on the power/wakeup attribute don't get triggered
correctly if device_set_wakeup_capable is called after the device is
created. This can happen for several reasons (driver sets wakeup after
device is created, wakeup is changed on parent device, etc) and it seems
reasonable
From: Marian-Cristian Rotariu
Document bindings for the RZ/G2H (aka R8A774E1) SYSC block.
Signed-off-by: Marian-Cristian Rotariu
Signed-off-by: Lad Prabhakar
---
Documentation/devicetree/bindings/power/renesas,rcar-sysc.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Marian-Cristian Rotariu
This patch adds board HiHope RZ/G2H (the main board, powered by the
R8A774E1) and board HiHope RZ/G2 EX (the expansion board that sits on top
of the HiHope RZ/G2H). Both boards are made by Jiangsu HopeRun Software
Co., Ltd. (a.k.a. HopeRun).
Signed-off-by:
601 - 700 of 1789 matches
Mail list logo
