From: Daniele Alessandrelli
Add maintainers for the new Intel Movidius SoC code-named Keem Bay.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b4a43a9e7fbc..b151d0fc0588
From: Daniele Alessandrelli
Add initial device tree for Keem Bay EVM board. With this minimal device
tree the board boots fine using an initramfs image.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
MAINTAINERS | 1 +
arch/arm64/boot/dts/inte
From: Daniele Alessandrelli
Add ARCH_KEEMBAY configuration option to support Intel Movidius SoC
code-named Keem Bay.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
arch/arm64/Kconfig.platforms | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/Kconfig.platf
From: Daniele Alessandrelli
Document Intel Movidius SoC code-named Keem Bay, along with the Keem Bay
EVM board.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
.../devicetree/bindings/arm/keembay.yaml | 19 +++
1 file changed, 19 insertions(+)
create mo
From: Daniele Alessandrelli
Add clock dt-bindings for Keem Bay SoC.
Signed-off-by: Daniele Alessandrelli
---
include/dt-bindings/clock/keembay-clocks.h | 188 +
1 file changed, 188 insertions(+)
create mode 100644 include/dt-bindings/clock/keembay-clocks.h
diff --git a/in
The cpus.yaml binding documents what's in 'cpu' nodes, not 'cpus'
node. AIUI, the latter is what you want. You should do your own schema
file here.
Do you mean to change existing file name from 'cpus.yaml' to 'cpu.yaml'
and create new 'cpus.yaml' file?
I think it's better to incorporate the
This implements the mount_setattr() syscall. While the new mount api
allows to change the properties of a superblock there is currently no
way to change the mount properties of a mount or mount tree using mount
file descriptors which the new mount api is based on. In addition the
old mount api has
On Tue, Jul 14, 2020 at 06:53:26PM +0300, Alexey Budankov wrote:
>
> On 14.07.2020 18:16, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jul 14, 2020 at 09:05:10PM +0900, Namhyung Kim escreveu:
> >> Hello,
> >>
> >> On Tue, Jul 14, 2020 at 5:37 PM Alexey Budankov
> >> wrote:
> >>>
> >>>
> >>> Change
Hey everyone,
This series can be found at:
https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=mount_setattr
https://gitlab.com/brauner/linux/-/commits/mount_setattr
https://github.com/brauner/linux/tree/mount_setattr
This implements the mount_setattr() syscall which has come
Add a range of selftests for the new mount_setattr() syscall to verify
that it works as expected. This tests that:
- no invalid flags can be specified
- changing properties of a single mount works and leaves other mounts in
the mount tree unchanged
- changing a mount tre to read-only when one of
Changing mount options always ends up taking lock_mount_hash() but when
MNT_READONLY is requested and neither the mount nor the superblock are
not already MNT_READONLY we end up taking the lock, dropping it, and
retaking it to change the other mount attributes. Instead of this,
acquire the lock onc
do_reconfigure_mnt() used to take the down_write(&sb->s_umount) lock
which seems unnecessary since we're not changing the superblock. We're
only checking whether it is already read-only. Setting other mount
attributes is protected by lock_mount_hash() afaict and not by s_umount.
So I think the his
Hey everyone,
So it looks like this was a red herring. We were getting spurious
interrupts which I suspect caused the console code to get called in
some critical section. Once we fixed the spurious interrupts we no
longer see the issue. Sorry for the noise.
Thanks,
Raul
On Thu, Jul 9, 2020 at 7:2
Signed-off-by: Christian Brauner
---
man2/mount_setattr.2 | 296 +++
1 file changed, 296 insertions(+)
create mode 100644 man2/mount_setattr.2
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
new file mode 100644
index 0..aae10525e
--- /de
On Sun, Jul 12, 2020 at 11:01:13AM +0100, Jon Hunter wrote:
> This series adds support for in-band debug messaging for the BPMP and
> updates the BPMP ABI to align with the latest version.
>
> Jon Hunter (4):
> firmware: tegra: Use consistent return variable name
> firmware: tegra: Prepare for
On 7/14/2020 9:08 AM, Vinod Koul wrote:
On 13-07-20, 13:55, Dave Jiang wrote:
On 7/10/2020 2:38 AM, Serge Semin wrote:
On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote:
On Fri, Jul 10, 2020 at 01:45:44AM +0300, Serge Semin wrote:
There are DMA devices (like ours version of
Vladimir Oltean writes:
[...]
>> Acked-by: Vladimir Oltean
>>
>> Thanks,
>> -Vladimir
>
> Of course, it would be good if you sent a new version with the sha1sum
> of the Fixes: tag having the right length, otherwise people will
> complain.
Ah, thanks for reminding! I entirely forgot about it
On Tue, Jul 14, 2020 at 9:08 AM Joel Fernandes wrote:
>
> I was thinking we should not call move_page_tables() with overlapping ranges
> at all, just to keep things simple.
No, we're not breaking the existing stack movement code just to keep
things simple.
The rule is "make it as simple as possi
On Mon, Jul 13, 2020 at 11:41 PM Junxiao Bi wrote:
>
> On 7/13/20 11:17 PM, Song Liu wrote:
>
> > On Thu, Jul 9, 2020 at 4:36 PM Junxiao Bi wrote:
> >> The following deadlock was captured. The first process is holding
> >> 'kernfs_mutex'
> >> and hung by io. The io was staging in 'r1conf.pending
On Tue, Jul 14, 2020 at 10:44:49AM -0500, Gustavo A. R. Silva wrote:
> There is a regular need in the kernel to provide a way to declare
> having a dynamically sized set of trailing elements in a structure.
> Kernel code should always use “flexible array members”[1] for these
> cases. The older sty
On Mon, Jul 13, 2020 at 11:41 PM Christoph Hellwig wrote:
>
> On Thu, Jul 09, 2020 at 04:32:07PM -0700, h...@zytor.com wrote:
> > On July 9, 2020 8:17:57 AM PDT, Christoph Hellwig wrote:
> > >Hi all,
> > >
> > >this series starts to move the early init code away from requiring
> > >KERNEL_DS to b
Hi Nic,
Le 03/07/2020 à 11:38, Arnaud Ferraris a écrit :
> Hi Nic,
>
> Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
>> Hi Arnaud,
>>
>> On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
>>> The current ASRC driver hardcodes the input and output clocks used for
>>> sample rate conv
On 2020-07-14 17:03, Rafael J. Wysocki wrote:
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
If we fail to use a variable, even a 'dummy' one, then the compiler
complains that it is set but not used. We know this is fine, so we
set it to its own value here.
Which is kind of ugly in my per
On Tue, Jul 14, 2020 at 3:41 AM Thierry Reding wrote:
>
> From: Thierry Reding
>
> The current checks will interpret a '+' character as special because
> they use regular expression matching. Escape the '+' character if it
> appears in a compatible string.
Ugg, looks like c6x really liked using
On Mon, Jul 13, 2020 at 3:52 PM Richard Guy Briggs wrote:
>
> audit_log_string() was inteded to be an internal audit function and
> since there are only two internal uses, remove them. Purge all external
> uses of it by restructuring code to use an existing audit_log_format()
> or using audit_log
Pointers to ring-buffer packets sent by Hyper-V are used within the
guest VM. Hyper-V can send packets with erroneous values or modify
packet fields after they are processed by the guest. To defend
against these scenarios, return a copy of the incoming VMBus packet
after validating its length and o
On Tue, 14 Jul 2020 09:25:14 +0100
Christoph Hellwig wrote:
> On Tue, Jul 14, 2020 at 01:57:03PM +0800, Lu Baolu wrote:
> > Replace iommu_aux_at(de)tach_device() with
> > iommu_aux_at(de)tach_group(). It also saves the
> > IOMMU_DEV_FEAT_AUX-capable physcail device in the vfio_group data
> > stru
On Tue, Jul 14, 2020 at 04:39:47PM +0530, kalya...@codeaurora.org wrote:
> On 2020-07-14 06:42, Matthias Kaehlcke wrote:
> > On Thu, Jun 18, 2020 at 07:38:41PM +0530, Kalyan Thota wrote:
> > > This change adds support to scale src clk and bandwidth as
> > > per composition requirements.
> > >
> >
On Mon, 2020-07-13 at 08:46 +0100, Lee Jones wrote:
> Looks like none of the artifact from ahc_fetch_transinfo() are used
> anymore.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/scsi/aic7xxx/aic7xxx_osm.c: In function
> ‘ahc_linux_target_alloc’:
> drivers/scsi/aic7xxx/aic7x
Thx Masami,
On Tue, Jul 14, 2020 at 7:38 PM Masami Hiramatsu wrote:
>
> On Mon, 13 Jul 2020 23:39:21 +
> guo...@kernel.org wrote:
>
> > From: Guo Ren
> >
> > This patch adds support for kprobes on ftrace call sites to avoids
> > much of the overhead with regular kprobes. Try it with simple
>
Hello,
syzbot found the following crash on:
HEAD commit:f0d5ec90 kmsan: apply __no_sanitize_memory to dotraplinkag..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=10c0883b10
kernel config: https://syzkaller.appspot.co
Hello,
syzbot found the following crash on:
HEAD commit:25051b55 udc: lpc32xx: make symbol 'lpc32xx_usbddata' static
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=12e0ba0090
kernel conf
Hi Vinod,
On Mon Jul 13, 2020 at 10:38 AM Vinod Koul wrote:
> On 01-07-20, 21:06, Liam Beguin wrote:
> > From: Liam Beguin
> >
> > Start by reading the content of the VENDOR_SPECIFIC2 register and update
> > each bit field based on device properties when defined.
> >
> > The use of bit masks pr
Fix support for external PTP-aware devices such as DSA or PTP PHY:
Make sure we never time stamp tx packets when hardware time stamping
is disabled.
Check for PTP PHY being in use and then pass ioctls related to time
stamping of Ethernet packets to the PTP PHY rather than handle them
ourselves. I
On Tue, 14 Jul 2020 15:58:53 + Westergreen, Dalon wrote:
> On Tue, 2020-07-14 at 08:55 -0700, Jakub Kicinski wrote:
> > On Tue, 14 Jul 2020 14:35:16 + Ooi, Joyce wrote:
> > > > I'm no device tree expert but these look like config options rather than
> > > > HW
> > > > description. They al
On 7/14/20 9:18 AM, Song Liu wrote:
On Mon, Jul 13, 2020 at 11:41 PM Junxiao Bi wrote:
On 7/13/20 11:17 PM, Song Liu wrote:
On Thu, Jul 9, 2020 at 4:36 PM Junxiao Bi wrote:
The following deadlock was captured. The first process is holding 'kernfs_mutex'
and hung by io. The io was staging i
On Tue, Jul 14, 2020 at 09:18:16AM -0700, Dave Jiang wrote:
>
>
> On 7/14/2020 9:08 AM, Vinod Koul wrote:
> > On 13-07-20, 13:55, Dave Jiang wrote:
> > >
> > >
> > > On 7/10/2020 2:38 AM, Serge Semin wrote:
> > > > On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote:
> > > > > On Fr
From: Liam Beguin
Start by reading the content of the VENDOR_SPECIFIC2 register and update
each bit field based on device properties when defined.
The use of bit masks prevents fields from overriding each other and
enables users to clear bits which are set by default, like datapolarity
in this i
On Tue, 14 Jul 2020 13:57:01 +0800
Lu Baolu wrote:
> This adds two new aux-domain APIs for a use case like vfio/mdev where
> sub-devices derived from an aux-domain capable device are created and
> put in an iommu_group.
>
> /**
> * iommu_aux_attach_group - attach an aux-domain to an iommu_group
On Mon, Jul 13, 2020 at 5:50 PM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 13, 2020 at 1:25 PM Rob Herring wrote:
> >
> > On Mon, Jul 13, 2020 at 9:08 AM Doug Anderson wrote:
> > >
> > > Hi,
> > >
> > > On Mon, Jul 13, 2020 at 7:11 AM Rob Herring wrote:
> > > >
> > > > On Fri, Jul 10, 2020 at
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/intel_pstate.c:293: warning: Function parameter or member
> 'get_aperf_mperf_shift' not described in 'pstate_funcs'
>
> Cc: Srinivas Pandruvada
> Cc: Len Brown
> Cc: Dirk B
On Tue 14 Jul 09:04 PDT 2020, Stephan Gerhold wrote:
> Hi Bjorn,
>
> On Mon, Jun 22, 2020 at 12:59:55AM -0700, Bjorn Andersson wrote:
> > In modern Qualcomm platforms the mutex region of the TCSR is forked off
> > into its own block, all with a offset of 0 and stride of 4096, and in
> > some of t
Hello,
syzbot found the following crash on:
HEAD commit:8fb49c01 Merge branch 'Expose-port-split-attributes'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1196f38f10
kernel config: https://syzkaller.appspot.com/x/.config?x=415c682f6b7a0cbf
dashboard l
On Tue, 23 Jun 2020 20:39:15 +0900, Masahiro Yamada wrote:
> Convert the UniPhier AIO audio system binding to DT schema format.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Convert UniPhier AIO audio system to json-schema
com
On Tue, 23 Jun 2020 20:40:05 +0900, Masahiro Yamada wrote:
> Convert the UniPhier EVEA sound codec binding to DT schema format.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Convert UniPhier EVEA codec to json-schema
commit: 0
On Tue, 2020-07-14 at 11:43 +0100, Anton Ivanov wrote:
> Patch is OK with me, should not read patches before the 3rd double espresso
> next time.
>
> I will +1 it, Richard, Johannes, what do you think?
I got dropped off the list in "The Great Infradead Purge" but I see it
in patchwork ;)
Not s
On Wed, 24 Jun 2020 00:00:13 +0530, Pratyush Yadav wrote:
> This series adds support for octal DTR flashes in the spi-nor framework,
> and then adds hooks for the Cypress Semper and Mircom Xcella flashes to
> allow running them in octal DTR mode. This series assumes that the flash
> is handed to th
This version of the patch was not merged and the message above doesn't
exist in the merged patch:
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=9a3e9e6ff6d7f6b8ce7903893962d50adcbe82d2
The err log was emitted during boot as well and is innocuous sin
On Tue, Jul 14, 2020 at 8:47 AM Todd Kjos wrote:
>
> +Suren Baghdasaryan +Hridya Valsaraju who support the ashmem driver.
Thanks for looping me in.
>
>
> On Tue, Jul 14, 2020 at 7:18 AM Michal Hocko wrote:
> >
> > On Tue 14-07-20 22:08:59, Hillf Danton wrote:
> > >
> > > On Tue, 14 Jul 2020 10:
On Tue, Jul 14, 2020 at 05:04:48PM +0100, Chris Down wrote:
> Borislav Petkov writes:
> > On Tue, Jul 14, 2020 at 01:19:55PM +0100, Chris Down wrote:
> > > That is, even with pr_err_ratelimited, we still end up logging on
> > > basically
> > > every single write, even though it's from the same TGI
On 7/14/2020 9:29 AM, Serge Semin wrote:
On Tue, Jul 14, 2020 at 09:18:16AM -0700, Dave Jiang wrote:
On 7/14/2020 9:08 AM, Vinod Koul wrote:
On 13-07-20, 13:55, Dave Jiang wrote:
On 7/10/2020 2:38 AM, Serge Semin wrote:
On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote:
On Tue, Jul 14, 2020 at 6:16 PM Christian Brauner
wrote:
> Changing mount options always ends up taking lock_mount_hash() but when
> MNT_READONLY is requested and neither the mount nor the superblock are
> not already MNT_READONLY we end up taking the lock, dropping it, and
> retaking it to change
Lee,
> Yes, I spotted it. Hence my earlier comment to Hannes:
>
> "Look at the function below it (in your local copy). ;)"
>
> Do you want me to fix that up here as well?
I can fix it up.
--
Martin K. Petersen Oracle Linux Engineering
On Tue, Jul 14, 2020 at 05:04:48PM +0100, Chris Down wrote:
> Since the issue involves DPTF which is only supported via binary blobs, I
> can't say for certain what the issue is. As I understand it, when the
> throttling behaviour isn't explicitly configured by the OS kernel, the
> default policy i
Thanks for the replies and workaround suggestions!
Francesco
On Tue, Jul 14, 2020 at 09:46:12AM -0700, Luck, Tony wrote:
> Maybe we just need smarter filtering of warnings. It doesn't
> seem at all useful to warn for the same MSR 1000's of times.
> Maybe keep a count of warnings for each MSR and just stop
> all reports when reach a threshold?
No, not stop
Hello RT Folks!
I'm pleased to announce the 4.19.132-rt59 stable release.
This release is just an update to the new stable 4.19.132
version and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
On Fri, Jul 10, 2020 at 09:47:02PM +0200, Uwe Kleine-König wrote:
> On Fri, Jul 10, 2020 at 12:48:36PM +0200, H. Nikolaus Schaller wrote:
> >
> > > Am 10.07.2020 um 12:27 schrieb Uwe Kleine-König
> > > :
> > >
> > > When commit 9017dc4fbd59 ("pwm: jz4740: Enhance precision in calculation
> > > o
Luck, Tony writes:
On Tue, Jul 14, 2020 at 05:04:48PM +0100, Chris Down wrote:
Borislav Petkov writes:
> On Tue, Jul 14, 2020 at 01:19:55PM +0100, Chris Down wrote:
> > That is, even with pr_err_ratelimited, we still end up logging on basically
> > every single write, even though it's from the s
On Tue, Jul 14, 2020 at 2:40 AM Christoph Hellwig wrote:
>
> On Tue, Jun 16, 2020 at 10:23:13AM -0400, Brian Gerst wrote:
> > Christoph Hellwig uncovered an issue with how we currently handle X32
> > syscalls. Currently, we can only use COMPAT_SYS_DEFINEx() for X32
> > specific syscalls. These c
Borislav Petkov writes:
On Tue, Jul 14, 2020 at 05:04:48PM +0100, Chris Down wrote:
Since the issue involves DPTF which is only supported via binary blobs, I
can't say for certain what the issue is. As I understand it, when the
throttling behaviour isn't explicitly configured by the OS kernel, t
-static/20200714-212512
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
caaba08f8c0dbe5c8fcb497faa7e3b394c21ff39
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project
02946de3802d3bc65bc9f2eb9b8d4969b5a7add8
On Tue, Jul 14, 2020 at 8:39 AM Johannes Weiner wrote:
>
> On Fri, Jul 10, 2020 at 12:19:37PM -0700, Shakeel Butt wrote:
> > On Fri, Jul 10, 2020 at 11:42 AM Roman Gushchin wrote:
> > >
> > > On Fri, Jul 10, 2020 at 07:12:22AM -0700, Shakeel Butt wrote:
> > > > On Fri, Jul 10, 2020 at 5:29 AM Mic
On Tue, Jul 14, 2020 at 06:55:30PM +0530, Akhil P Oommen wrote:
> On targets where GMU is available, GMU takes over the ownership of GX GDSC
> during its initialization. So, take a refcount on the GX PD on behalf of
> GMU before we initialize it. This makes sure that nobody can collapse the
> GX GD
On Tue, 2020-07-14 at 10:21 -0600, Rob Herring wrote:
> On Tue, Jul 14, 2020 at 3:41 AM Thierry Reding
> wrote:
> > From: Thierry Reding
> >
> > The current checks will interpret a '+' character as special because
> > they use regular expression matching. Escape the '+' character if it
> > appe
On 7/14/20 7:11 AM, Maciej S. Szmigiero wrote:
> On 14.07.2020 16:02, Guenter Roeck wrote:
>> On 7/11/20 1:41 PM, Maciej S. Szmigiero wrote:
>>> It has been observed that Toshiba DT01ACA family drives have
>>> WRITE FPDMA QUEUED command timeouts and sometimes just freeze until
>>> power-cycled unde
On Mon, Jun 29, 2020 at 09:49:19PM -0500, Suman Anna wrote:
> The Texas Instruments K3 family of SoCs have one or more dual-core
> Arm Cortex R5F processor subsystems/clusters (R5FSS). The clusters
> can be split between multiple voltage domains as well. Add the device
> tree bindings document for
On 7/14/20 9:50 AM, Lee Jones wrote:
> Can't see them being used anywhere and the compiler doesn't complain
> that they're missing, so ...
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/amd_freq_sensitivity.c:147:32: warning:
> ‘amd_freq_sensitivity_ids’ defined but no
On Mon, Jul 13, 2020 at 11:58 PM Guenter Roeck wrote:
>
> On 7/13/20 11:05 PM, reg Kroah-Hartman wrote:
> > On Mon, Jul 13, 2020 at 01:43:00PM -0700, Badhri Jagan Sridharan wrote:
> >> "tReceiverResponse 15 ms Section 6.6.2
> >> The receiver of a Message requiring a response Shall respond
> >> wit
On Mon, Jul 13, 2020 at 03:49:23PM +0100, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/pinctrl/pinctrl-bm1880.c:40: warning: Function parameter or member
> 'pctrldev' not described in 'bm1880_pinctrl'
> drivers/pinctrl/pinctrl-bm1880.c:40: warning: Function pa
Al Viro writes:
> Conversion of ELF coredumps to regsets has not touched
> ELF_FDPIC. Right now all architectures that support FDPIC have
> regsets sufficient for switching it to regset-based coredumps. A bit
> of backstory: original ELF (and ELF_FDPIC) coredumps reused the old
> helpers
On Thu, Jul 09, 2020 at 01:31:54PM -0700, Rishabh Bhatnagar wrote:
> From: Sibi Sankar
>
> In order to land inline coredump support for mss, the dump_segment
> function would need to support granularities less than the segment
> size. This is achieved by replacing mask based tracking with size.
>
On Mon, Jul 13, 2020 at 03:49:06PM +0100, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/pinctrl/actions/pinctrl-owl.c:52: warning: Function parameter or
> member 'clk' not described in 'owl_pinctrl'
> drivers/pinctrl/actions/pinctrl-owl.c:52: warning: Function
On Mon, 13 Jul 2020 15:29:22 +0200, Alexandre Bailon wrote:
> This adds dt bindings for the APU present in the MT8183.
>
> Signed-off-by: Alexandre Bailon
> ---
> .../bindings/remoteproc/mtk,apu.yaml | 121 ++
> 1 file changed, 121 insertions(+)
> create mode 100644 Doc
isif_probe() invokes iounmap() on error handling paths, but it does not
reset the global state. So, later it can invoke iounmap() even when
ioremap() fails. This is the case also for isif_remove(). The patch
resets the global state after invoking iounmap() to avoid this.
Found by Linux Driver Veri
On Mon, Jul 13, 2020 at 03:29:22PM +0200, Alexandre Bailon wrote:
> This adds dt bindings for the APU present in the MT8183.
>
> Signed-off-by: Alexandre Bailon
> ---
> .../bindings/remoteproc/mtk,apu.yaml | 121 ++
> 1 file changed, 121 insertions(+)
> create mode 1006
On Mon, 13 Jul 2020 11:41:10 -0400, Jonathan Marek wrote:
> These two bindings are almost identical, so combine them into one. This
> will make it easier to add the sm8150 and sm8250 interconnect bindings.
>
> Signed-off-by: Jonathan Marek
> ---
> .../{qcom,sc7180.yaml => qcom,rpmh.yaml} |
At Google, we actually extended struct rseq (I will post the patches
here once they are fully deployed and we have specific
benefits/improvements to report). We did this by adding several fields
below __u32 flags (the last field currently), and correspondingly
increasing rseq_len in rseq() syscall.
Hello, Ingo!
This pull request contains the following changes:
1. Documentation updates.
https://lore.kernel.org/lkml/20200623000923.GA25047@paulmck-ThinkPad-P72
2. Miscellaneous fixes.
https://lore.kernel.org/lkml/20200623002128.GA25456@paulmck-ThinkPad-P72
3.
On Tue, 14 Jul 2020 14:57:36 +
"Ardelean, Alexandru" wrote:
> On Fri, 2020-05-22 at 13:46 +0300, Alexandru Ardelean wrote:
> > From: Lars-Peter Clausen
> >
> > All devices using a triggered buffer need to attach and detach the
> > trigger
> > to the device in order to properly work. Instead
On Mon, Jul 13, 2020 at 9:38 PM Andrii Nakryiko
wrote:
>
> On Mon, Jul 13, 2020 at 6:29 PM Peilin Ye wrote:
> >
> > Prevent __btf_resolve_helper_id() from dereferencing `btf_vmlinux`
> > as NULL. This patch fixes the following syzbot bug:
> >
> >
> > https://syzkaller.appspot.com/bug?id=5edd
On Tue, Jul 14, 2020 at 3:40 PM Jonathan Corbet wrote:
> On Tue, 14 Jul 2020 09:22:39 +0200
> Geert Uytterhoeven wrote:
> > > > - website http://openrisc.io
> > > > + website https://openrisc.io
> > > > email openr...@lists.librecores.org
> > > >
On Tue, Jul 14, 2020 at 1:45 AM Michael S. Tsirkin wrote:
>
> On Mon, Jul 13, 2020 at 08:10:14AM -0700, Alexander Duyck wrote:
> > On Sun, Jul 12, 2020 at 8:10 AM Michael S. Tsirkin wrote:
> > >
> > > On Fri, Jul 10, 2020 at 09:13:41AM -0700, Alexander Duyck wrote:
> > > > On Fri, Jul 10, 2020 at
On Mon, Jul 13, 2020 at 03:05:11PM +0200, Matteo Croce wrote:
> From: Matteo Croce
>
> Allow to load the BPF instructons from a file descriptor,
> other than a pointer.
>
> This is required by the Integrity Subsystem to validate the source of
> the instructions.
>
> In bpf_attr replace 'insns',
Hello!
This pull request contains KCSAN updates for v5.9. These have been
subjected to LKML review, most recently here:
https://lore.kernel.org/lkml/20200623004310.GA26995@paulmck-ThinkPad-P72/
All of these have also been subjected to the kbuild test robot and
-next testing. The follo
On Tue, Jul 14, 2020 at 9:41 AM Suren Baghdasaryan wrote:
>
> On Tue, Jul 14, 2020 at 8:47 AM Todd Kjos wrote:
> >
> > +Suren Baghdasaryan +Hridya Valsaraju who support the ashmem driver.
>
> Thanks for looping me in.
>
> >
> >
> > On Tue, Jul 14, 2020 at 7:18 AM Michal Hocko wrote:
> > >
> > >
From: Min Li
Add below to “Ancillary clock features” section
- Low Pass Filter (LPF) access from user space
Add below to list of “Supported hardware” section
+ Renesas (IDT) ClockMatrix™
Signed-off-by: Min Li
---
Documentation/driver-api/ptp.rst | 12
1 file changed, 12 inser
I've noticed a number of warnings like "vmstat_refresh: nr_free_cma
-5" or "vmstat_refresh: nr_zone_write_pending -11" on our production
hosts. The numbers of these warnings were relatively low and stable,
so it didn't look like we are systematically leaking the counters.
The corresponding vmstat c
(Resending as plain text)
Ack. Thanks.
Jeff
On Mon, Jul 13, 2020 at 11:30 PM Lukas Bulwahn wrote:
>
> Commit 7f52faabd2e5 ("media: dt-bindings: Add ch7322 media i2c device")
> slipped in a typo in the CHRONTEL CH7322 CEC DRIVER section.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patter
I've noticed a number of warnings like "vmstat_refresh: nr_free_cma
-5" or "vmstat_refresh: nr_zone_write_pending -11" on our production
hosts. The numbers of these warnings were relatively low and stable,
so it didn't look like we are systematically leaking the counters.
The corresponding vmstat c
This is passed to irq_domain_add_linear(), which accepts a pointer
to a const structure.
Signed-off-by: Masahiro Yamada
---
drivers/irqchip/irq-ativic32.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-ativic32.c b/drivers/irqchip/irq-ativic32.c
index 85
There is a regular need in the kernel to provide a way to declare
having a dynamically sized set of trailing elements in a structure.
Kernel code should always use “flexible array members”[1] for these
cases or, as in this particular case, replace the one-element array
with a simple value type u8 r
On Tue, Jul 14, 2020 at 11:12 AM Joe Perches wrote:
>
> On Tue, 2020-07-14 at 10:21 -0600, Rob Herring wrote:
> > On Tue, Jul 14, 2020 at 3:41 AM Thierry Reding
> > wrote:
> > > From: Thierry Reding
> > >
> > > The current checks will interpret a '+' character as special because
> > > they use
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
>
> Can't see them being used anywhere and the compiler doesn't complain
> that they're missing, so ...
Autoloading of the module too.
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/pcc-cpufreq.c:619:36: warning: ‘processo
On Tue, Jul 14, 2020 at 10:37:47AM -0700, Roman Gushchin wrote:
> I've noticed a number of warnings like "vmstat_refresh: nr_free_cma
> -5" or "vmstat_refresh: nr_zone_write_pending -11" on our production
> hosts. The numbers of these warnings were relatively low and stable,
> so it didn't look lik
Hello, Ingo!
This pull request contains Linux-Kernel Memory-Model commits for v5.9.
These have been subjected to LKML review:
https://lore.kernel.org/lkml/20200623005152.GA27459@paulmck-ThinkPad-P72/
All of these have also been subjected to the kbuild test robot and
-next testing. The
- On Jul 14, 2020, at 1:24 PM, Peter Oskolkov p...@posk.io wrote:
> At Google, we actually extended struct rseq (I will post the patches
> here once they are fully deployed and we have specific
> benefits/improvements to report). We did this by adding several fields
> below __u32 flags (the la
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
>
> If we fail to use a variable, even a 'dummy' one, then the compiler
> complains that it is set but not used. We know this is fine, so we
> set it to its own value here.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/p
On 2020-07-14 12:21, Paul Moore wrote:
> On Mon, Jul 13, 2020 at 3:52 PM Richard Guy Briggs wrote:
> >
> > audit_log_string() was inteded to be an internal audit function and
> > since there are only two internal uses, remove them. Purge all external
> > uses of it by restructuring code to use an
On Tue, Jul 14, 2020 at 4:11 AM Sedat Dilek wrote:
>
> When using Clang's Integrated Assembler (LLVM_IAS=1) we fell over
> ClangBuiltLinux (CBL) issue #1043 where Jian Cai provided a patch.
>
> With Jian's patch applied another issue raised up when CONFIG_HYPERV=m.
>
> It turned out that the conve
901 - 1000 of 1972 matches
Mail list logo
