On Mon, Jul 27, 2020 at 06:49:11AM -0400, Mimi Zohar wrote:
> On Fri, 2020-07-24 at 14:36 -0700, Kees Cook wrote:
> > There are a few places in the kernel where LSMs would like to have
> > visibility into the contents of a kernel buffer that has been loaded or
> > read. While
Quoting Daniel Campello (2020-07-28 08:12:53)
> @@ -368,13 +368,13 @@ static int sx9310_wait_for_sample(struct sx9310_data
> *data)
> static int sx9310_read_proximity(struct sx9310_data *data,
> const struct iio_chan_spec *chan, int *val)
> {
> - int ret =
On 4/3/20 4:59 PM, Alex Kogan wrote:
Keep track of the number of intra-node lock handoffs, and force
inter-node handoff once this number reaches a preset threshold.
The default value for the threshold can be overridden with
the new kernel boot command-line option "numa_spinlock_threshold".
On 7/28/20 8:59 AM, Sowjanya Komatineni wrote:
On 7/28/20 3:30 AM, Dmitry Osipenko wrote:
27.07.2020 23:57, Sowjanya Komatineni пишет:
+ /*
+ * TRM has incorrectly documented to wait for done status from
+ * calibration logic after CSI interface power on.
+ * As per the
Quoting Daniel Campello (2020-07-28 08:12:51)
> diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
> index 2465064971d0a7..3956fd679c6db9 100644
> --- a/drivers/iio/proximity/sx9310.c
> +++ b/drivers/iio/proximity/sx9310.c
> @@ -810,22 +810,17 @@ static int
On Mon, Jul 27, 2020 at 07:08:01PM -0400, Arvind Sankar wrote:
> Commit
> f28442497b5c ("x86/boot: Fix KASLR and memmap= collision")
> converted mem_vector type to use 64-bit on the 32-bit kernel as well,
> based on Thomas's review [0]. However:
> - the code still doesn't consistently use 64-bit
Quoting Daniel Campello (2020-07-28 08:12:50)
> diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
> index fb5c16f2aa6b1a..2465064971d0a7 100644
> --- a/drivers/iio/proximity/sx9310.c
> +++ b/drivers/iio/proximity/sx9310.c
> @@ -538,13 +540,13 @@ static void
On 4/3/20 4:59 PM, Alex Kogan wrote:
Prohibit moving certain threads (e.g., in irq and nmi contexts)
to the secondary queue. Those prioritized threads will always stay
in the primary queue, and so will have a shorter wait time for the lock.
Signed-off-by: Alex Kogan
Reviewed-by: Steve Sistare
On Mon, Jul 27, 2020 at 07:08:00PM -0400, Arvind Sankar wrote:
> The number of slots and slot areas can be unsigned int, since on 64-bit,
> the maximum amount of memory is 2^52, the minimum alignment is 2^21, so
> the slot number cannot be greater than 2^31. The slot areas are limited
> by
On 28/07/20 7:14 pm, Michael Ellerman wrote:
Hari Bathini writes:
diff --git a/arch/powerpc/kexec/file_load_64.c
b/arch/powerpc/kexec/file_load_64.c
index 2df6f4273ddd..8df085a22fd7 100644
--- a/arch/powerpc/kexec/file_load_64.c
+++ b/arch/powerpc/kexec/file_load_64.c
@@ -17,9 +17,21 @@
Quoting Daniel Campello (2020-07-28 08:12:48)
> Uses .probe_new in place of .probe. Also uses device_get_match_data()
> for whoami matching.
>
> Signed-off-by: Daniel Campello
> ---
Reviewed-by: Stephen Boyd
Compiler leaves a 4-byte hole near the end of `dev_info`, causing
amdgpu_info_ioctl() to copy uninitialized kernel stack memory to userspace
when `size` is greater than 356.
In 2015 we tried to fix this issue by doing `= {};` on `dev_info`, which
unfortunately does not initialize that 4-byte
On Mon, Jul 27, 2020 at 07:07:59PM -0400, Arvind Sankar wrote:
> Short-circuit the whole function on 32-bit.
>
> Replace the loop to determine the number of 1Gb pages with arithmetic.
>
> Fix one minor bug: if the end of the region is aligned on a 1Gb
> boundary, the current code will not use
On Mon, Jul 27, 2020 at 07:07:58PM -0400, Arvind Sankar wrote:
> Get rid of unnecessary temporary variables and redundant tests in
> __process_mem_region.
>
> Fix one minor bug: in case of an overlap, the beginning of the region
> should be used even if it is exactly image_size, not just strictly
On 28/07/20 7:16 pm, Michael Ellerman wrote:
Hari Bathini writes:
Kernel built with CONFIG_PPC_EARLY_DEBUG_OPAL enabled expects r8 & r9
to be filled with OPAL base & entry addresses respectively. Setting
these registers allows the kernel to perform OPAL calls before the
device tree is
Fix a missing __iomem tag in the init_pfn() function. This fixes a
sparse warning of the form:
sparse: sparse: incorrect type assignment(different address spaces)
Fixes: 080b47def5e5 ("MicroSemi Switchtec management interface driver")
Signed-off-by: Logan Gunthorpe
---
Fix a number of missing __iomem and __user tags in the ioctl functions of
the switchtec driver. This fixes a number of sparse warnings of the form:
sparse: sparse: incorrect type in ... (different address spaces)
Fixes: 52eabba5bcdb ("switchtec: Add IOCTLs to the Switchtec driver")
From: Alexander Usyskin
Some of the mei device heads are not generic and have
a specific purpose, we need to announce it to the user space
so it is possible to detect the correct device node via
matching attributes.
Generic heads are marked as 'mei' while special purpose heads
have their own
On Thu, Jul 23, 2020 at 03:29:58PM -0700, Ralph Campbell wrote:
> The goal for this series is to avoid device private memory TLB
> invalidations when migrating a range of addresses from system
> memory to device private memory and some of those pages have already
> been migrated. The approach
On 7/28/20 9:41 AM, Jens Axboe wrote:
> On 7/24/20 1:32 AM, Christoph Hellwig wrote:
>> Hi Jens,
>>
>> this series contains a bunch of different BDI cleanups. The biggest item
>> is to isolate block drivers from the BDI in preparation of changing the
>> lifetime of the block device BDI in a
On Thu, Jul 23, 2020 at 03:30:04PM -0700, Ralph Campbell wrote:
> When migrating the special zero page, migrate_vma_pages() calls
> mmu_notifier_invalidate_range_start() before replacing the zero page
> PFN in the CPU page tables. This is unnecessary since the range was
> invalidated in
On Tue, 28 Jul 2020 13:07:43 +0300, Codrin Ciubotariu wrote:
> This patch adds DT bindings for the new Microchip S/PDIF TX Controller
> embedded inside sama7g5 SoCs.
>
> Signed-off-by: Codrin Ciubotariu
> ---
> .../bindings/sound/mchp,spdiftx.yaml | 76 +++
> 1 file
On 23/07/2020 11:46, Lokesh Vutla wrote:
This series adds initial support for latest new SoC, J7200, from Texas
Instruments.
The J7200 SoC is a part of the K3 Multicore SoC architecture platform.
It is targeted for for automotive gateway, vehicle compute systems,
Vehicle-to-Vehicle (V2V)
On Thu, 23 Jul 2020 10:25:39 -0700
Jacob Pan wrote:
> IOMMU user APIs are responsible for processing user data. This patch
> changes the interface such that user pointers can be passed into IOMMU
> code directly. Separate kernel APIs without user pointers are introduced
> for in-kernel users of
On Thu, 23 Jul 2020 10:25:35 -0700
Jacob Pan wrote:
> IOMMU UAPI is newly introduced to support communications between guest
> virtual IOMMU and host IOMMU. There has been lots of discussions on how
> it should work with VFIO UAPI and userspace in general.
>
> This document is intended to
Hi Amelie,
On Tue, Jul 28, 2020 at 9:46 AM Amelie Delaunay wrote:
>
> If usb-role-switch is present in the device tree, it means that ID and Vbus
> signals are not connected to the OTG controller but to an external
> component (GPIOs, Type-C controller). In this configuration, usb role
> switch
On Tue, Jul 28, 2020 at 07:03:13PM +0900, Daniel Palmer wrote:
> This adds a YAML description of the pmsleep node used by
> MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++
> MAINTAINERS
On 7/28/2020 11:44 AM, Jakub Kicinski wrote:
> On Tue, 28 Jul 2020 09:47:00 -0700 Jacob Keller wrote:
>> On 7/28/2020 6:58 AM, Jiri Pirko wrote:
>>> But this is needed to maintain the existing behaviour which is different
>>> for different drivers.
>>
>> Which drivers behave differently here?
>
On 7/21/20 8:45 AM, Yu Kuai wrote:
> if of_find_device_by_node() succeed, socfpga_setup_ocram_self_refresh
> doesn't have a corresponding put_device(). Thus add a jump target to
> fix the exception handling for this function implementation.
>
> Fixes: 44fd8c7d4005 ("ARM: socfpga: support
On Thu, Jul 16, 2020 at 6:10 PM Kunihiko Hayashi
wrote:
>
> Current dma-buf heaps can handle only default CMA. This introduces
> dma_heap_add_cma() function to attach CMA heaps that belongs to a device.
>
> At first, the driver calls of_reserved_mem_device_init() to set
> memory-region property
On Tue, Jul 28, 2020 at 12:09 PM Roman Gushchin wrote:
>
> On Mon, Jul 27, 2020 at 11:06:42PM -0700, Song Liu wrote:
> > On Mon, Jul 27, 2020 at 10:58 PM Andrii Nakryiko
> > wrote:
> > >
> > > On Mon, Jul 27, 2020 at 10:47 PM Song Liu wrote:
> > > >
> > > > On Mon, Jul 27, 2020 at 12:26 PM
On Tue, 28 Jul 2020 19:03:13 +0900, Daniel Palmer wrote:
> This adds a YAML description of the pmsleep node used by
> MStar/SigmaStar Armv7 SoCs.
>
> Signed-off-by: Daniel Palmer
> ---
> .../bindings/arm/mstar/mstar,pmsleep.yaml | 43 +++
> MAINTAINERS
On 23/07/2020 11:46, Lokesh Vutla wrote:
The J7200 SoC is a part of the K3 Multicore SoC architecture platform.
It is targeted for automotive gateway, vehicle compute systems,
Vehicle-to-Vehicle (V2V) and Vehicle-to-Everything (V2X) applications.
The SoC aims to meet the complex processing
>
> On Tue, Jul 28, 2020 at 09:28:36PM +0300, Tomas Winkler wrote:
> > +/**
> > + * kind_show - display device kind
> > + *
> > + * @device: device pointer
> > + * @attr: attribute pointer
> > + * @buf: char out buffer
> > + *
> > + * Return: number of the bytes printed into buf or error
>
>
Quoting peng@nxp.com (2020-07-28 02:03:19)
> From: Peng Fan
>
> Use devm_of_clk_add_hw_provider() to simplify code.
> To i.MX8MP, also add err handling.
>
> Signed-off-by: Peng Fan
> ---
Reviewed-by: Stephen Boyd
Quoting peng@nxp.com (2020-07-28 02:03:18)
> From: Peng Fan
>
> Use devm_kzalloc() to avoid memory leak when probe fail.
>
> Signed-off-by: Peng Fan
> ---
Reviewed-by: Stephen Boyd
On Thu, Jul 23, 2020 at 03:30:01PM -0700, Ralph Campbell wrote:
> static inline int mm_has_notifiers(struct mm_struct *mm)
> @@ -513,6 +519,7 @@ static inline void mmu_notifier_range_init(struct
> mmu_notifier_range *range,
> range->start = start;
> range->end = end;
>
On 7/28/20 3:43 AM, Daniel Borkmann wrote:
On 7/27/20 11:39 PM, Yonghong Song wrote:
On 7/27/20 10:54 AM, Colin King wrote:
From: Colin Ian King
There are a couple of arguments of the boolean flag zero_size_allowed
and the char pointer buf_info when calling to function
Since some point in the current 5.8 cycle, iscsid sometimes crashes
and fails to come up after a reboot.
Here is a sample BUG:
kernel: BUG: scheduling while atomic: iscsid/763/0x0200
kernel: Call Trace:
kernel: dump_stack+0x6b/0x88
kernel: __schedule_bug.cold+0x4c/0x58
kernel:
On Mon, Jul 27, 2020 at 11:06:42PM -0700, Song Liu wrote:
> On Mon, Jul 27, 2020 at 10:58 PM Andrii Nakryiko
> wrote:
> >
> > On Mon, Jul 27, 2020 at 10:47 PM Song Liu wrote:
> > >
> > > On Mon, Jul 27, 2020 at 12:26 PM Roman Gushchin wrote:
> > > >
> > > > Remove rlimit-based accounting
On Mon, Jul 27, 2020 at 11:01 PM Randy Dunlap wrote:
>
> On 7/27/20 10:48 PM, Andrii Nakryiko wrote:
> > On Mon, Jul 27, 2020 at 11:58 AM Randy Dunlap wrote:
> >>
> >> On 7/27/20 6:23 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20200724:
> >>>
> >>
> >> on i386:
> >> when
The pull request you sent on Tue, 28 Jul 2020 14:42:19 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
> tags/asm-generic-fixes-5.8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6ba1b005ffc388c2aeaddae20da29e4810dea298
Thank you!
--
The pull request you sent on Mon, 27 Jul 2020 18:09:24 -0400:
> git://git.libc.org/linux-sh tags/sh-for-5.8-part2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4764e61e1d57c0bc3569dbc540af8bb28e18d2e6
Thank you!
--
Deet-doot-dot, I am a bot.
I am working on a response to this. I will send it soon.
Thanks.
Madhavan
On 7/28/20 12:31 PM, Andy Lutomirski wrote:
>> On Jul 28, 2020, at 6:11 AM, madve...@linux.microsoft.com wrote:
>>
>> From: "Madhavan T. Venkataraman"
>>
>> The kernel creates the trampoline mapping without any
Sebastian
On 7/28/20 1:17 PM, Sebastian Reichel wrote:
Hi,
On Tue, Jul 28, 2020 at 09:11:11AM -0500, Dan Murphy wrote:
Add the Texas Instruments BQ27561 battery monitor. The register address
map is laid out the same as compared to other devices within the file.
The battery status register
On Tue, Jul 28, 2020 at 09:52:10AM -0400, Johannes Weiner wrote:
> When an outside process lowers one of the memory limits of a cgroup
> (or uses the force_empty knob in cgroup1), direct reclaim is performed
> in the context of the write(), in order to directly enforce the new
> limit and have it
On Tue, Jul 28, 2020 at 09:28:36PM +0300, Tomas Winkler wrote:
> +/**
> + * kind_show - display device kind
> + *
> + * @device: device pointer
> + * @attr: attribute pointer
> + * @buf: char out buffer
> + *
> + * Return: number of the bytes printed into buf or error
No need for kernel doc for
On 7/28/20 12:16 PM, Andy Lutomirski wrote:
> On Tue, Jul 28, 2020 at 9:32 AM Madhavan T. Venkataraman
> wrote:
>> Thanks. See inline..
>>
>> On 7/28/20 10:13 AM, David Laight wrote:
>>> From: madve...@linux.microsoft.com
Sent: 28 July 2020 14:11
>>> ...
The kernel creates the
On Mon, Jul 27, 2020 at 07:07:57PM -0400, Arvind Sankar wrote:
> On 64-bit, the kernel must be placed below MAXMEM (64TiB with 4-level
> paging or 4PiB with 5-level paging). This is currently not enforced by
> KASLR, which thus implicitly relies on physical memory being limited to
> less than
On Mon, 2020-07-27 at 12:18 -0700, Scott Branden wrote:
> Hi Mimi/Kees,
>
> On 2020-07-27 4:16 a.m., Mimi Zohar wrote:
> > On Fri, 2020-07-24 at 14:36 -0700, Kees Cook wrote:
> >> v3:
> >> - add reviews/acks
> >> - add "IMA: Add support for file reads without contents" patch
> >> - trim CC list,
On Tue, Jul 28, 2020 at 12:27 PM Richard Guy Briggs wrote:
> On 2020-07-27 22:14, Paul Moore wrote:
> > On Mon, Jul 27, 2020 at 5:30 PM Richard Guy Briggs wrote:
> > > Issue ghak120 enabled syscall records to accompany required records when
> > > no rules are present to trigger the storage of
Hi,
On Mon, Jul 27, 2020 at 6:45 PM Tetsuo Handa
wrote:
>
> syzbot is reporting that del_timer_sync() is called from
> mwifiex_usb_cleanup_tx_aggr() from mwifiex_unregister_dev() without
> checking timer_setup() from mwifiex_usb_tx_init() was called [1].
> Since mwifiex_usb_prepare_tx_aggr_skb()
On Tue, 28 Jul 2020 09:47:00 -0700 Jacob Keller wrote:
> On 7/28/2020 6:58 AM, Jiri Pirko wrote:
> > But this is needed to maintain the existing behaviour which is different
> > for different drivers.
>
> Which drivers behave differently here?
I think Jiri refers to mlxsw vs mlx5.
mlxsw loads
Alright, I have understood now that I should not trust on
checkpatch.pl script fully but partially it is indeed helpful. Please
don't criticize this script, it was my fault instead.
Before submitting code changes I would test them all, sorry for
wasting your time please ignore this patch changes
On Tue, Jul 28, 2020 at 9:24 PM Joe Perches wrote:
> On Tue, 2020-07-28 at 21:19 +0300, Andy Shevchenko wrote:
> > On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello
> > wrote:
> > > From: Stephen Boyd
> > >
> > > Printks in the kernel have newlines at the end. Add them to the few
> >
> >
Hi Venkata,
> Setting memdump state to idle prior to setting of callback function
> pointer for command timeout to NULL,causing the issue.Now moved the
> initialisation of memdump state to qca_setup().
>
> Fixes: d841502c79e3 ("Bluetooth: hci_qca: Collect controller memory dump
> during SSR")
>
Hi,
Looks like N900 display support has broken after v5.6.
When using v5.7, or the current mainline (v5.8-rc7), the boot hangs at:
[6.269500] omapdss_dss 4805.dss: 4805.dss supply vdda_video not
found, using dummy regulator
[6.321685] DSS: OMAP DSS rev 2.0
[6.328002]
On Mon, Jul 27, 2020 at 11:11 PM Song Liu wrote:
>
>
>
> > On Jul 27, 2020, at 11:06 PM, Andrii Nakryiko
> > wrote:
> >
> > On Mon, Jul 27, 2020 at 12:25 PM Roman Gushchin wrote:
> >>
> >> As rlimit-based memory accounting is not used by bpf anymore,
> >> there are no more reasons to play with
Hi Abhishek,
> Unregister from suspend notifications and cancel suspend preparations
> before running hci_dev_do_close. Otherwise, the suspend notifier may
> race with unregister and cause cmd_timeout even after hdev has been
> freed.
>
> Below is the trace from when this panic was seen:
>
> [
From: Alexander Usyskin
Some of the mei device heads are not generic and have
a specific purpose, we need to announce it to the user space
so it is possible to detect the correct device node via
matching attributes.
Generic heads are marked as 'mei' while special purpose heads
have their own
On Tue, Jul 28, 2020 at 4:44 PM wrote:
>
> From: Tom Rix
>
> Clang static analysis reports this error
>
> gpiolib-of.c:664:9: warning: 2nd function call argument
> is an uninitialized value [core.CallAndMessage]
> ret = gpiod_hog(desc, name, lflags, dflags);
>
> name is sometimes set
On Mon, Jul 27, 2020 at 07:07:56PM -0400, Arvind Sankar wrote:
> Since commit
> 0982adc74673 ("x86/boot/KASLR: Work around firmware bugs by excluding
> EFI_BOOT_SERVICES_* and EFI_LOADER_* from KASLR's choice")
> process_efi_entries will return true if we have an EFI memmap, not just
> if it
Inside function ql_get_dump comment statement had a repition of word
"to" which I removed and checkpatch.pl ouputs zero error or warnings
now.
Signed-off-by: Dhiraj Sharma
---
drivers/staging/qlge/qlge_dbg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tuesday, July 28, 2020 4:32:22 AM CEST Francisco Jerez wrote:
>
> "Rafael J. Wysocki" writes:
>
> > On Tuesday, July 21, 2020 1:20:14 AM CEST Francisco Jerez wrote:
> >
> > [cut]
> >
> >> >
> >> > However, in the active mode the only updater of hwp_req_cached is
> >> > intel_pstate_hwp_set()
On Mon, Jul 27, 2020 at 07:07:55PM -0400, Arvind Sankar wrote:
> Drop the warning on seeing "--" in handle_mem_options. This will trigger
> whenever one of the memory options is present in the command line
> together with "--", but there's no problem if that is the case.
>
> Replace goto with
On Mon, Jul 27, 2020 at 07:07:54PM -0400, Arvind Sankar wrote:
> Handle the possibility that the command line is NULL.
>
> Replace open-coded strlen with a function call.
>
> Signed-off-by: Arvind Sankar
Reviewed-by: Kees Cook
--
Kees Cook
On Tue, Jul 28, 2020 at 11:29:35PM +0530, Dhiraj Sharma wrote:
> I ran checkpatch.pl script which reported a warning to use const keyword
> on line 370.Therefore I made this change.
>
> Signed-off-by: Dhiraj Sharma
> ---
> drivers/staging/android/ashmem.c | 2 +-
> 1 file changed, 1
On Tue, 2020-07-28 at 21:19 +0300, Andy Shevchenko wrote:
> On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
> > From: Stephen Boyd
> >
> > Printks in the kernel have newlines at the end. Add them to the few
>
> Printk()s
>
> > printks in this driver.
>
> printk()s
Random kernel
On Mon, Jul 27, 2020 at 04:02:55PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.7.11 release.
> There are 179 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Jul 27, 2020 at 04:03:15PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.54 release.
> There are 138 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Tue, Jul 28, 2020 at 05:51:19PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.135 release.
> There are 86 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Jul 27, 2020 at 04:03:39PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.190 release.
> There are 64 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Hi Doug,
On 7/28/20 5:48 PM, Doug Anderson wrote:
> Hi,
>
> On Sun, Jul 26, 2020 at 2:44 AM Stanimir Varbanov
> wrote:
>>
>> Hi Stephen,
>>
>> On 7/25/20 12:17 AM, Stephen Boyd wrote:
>>> From: Stephen Boyd
>>>
>>> The busy loop in rpmh_rsc_send_data() is written with the assumption
>>> that
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> From: Stephen Boyd
>
> Enable the main power supply (vdd) and digital IO power supply (svdd)
> during probe so that the i2c communication and device works properly on
> boards that aggressively power gate these supplies.
>
> Reviewed-by:
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> From: Stephen Boyd
>
> This struct member isn't used. Drop it.
>
> Fixes: 72ad02b15d63 ("iio: Add SEMTECH SX9310/9311 sensor driver")
> Signed-off-by: Stephen Boyd
> Reviewed-by: Douglas Anderson
> Reviewed-by: Daniel Campello
>
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> From: Stephen Boyd
>
> Printks in the kernel have newlines at the end. Add them to the few
Printk()s
> printks in this driver.
printk()s
> Reviewed-by: Daniel Campello
> Reviewed-by: Douglas Anderson
> Fixes: 72ad02b15d63 ("iio:
On Tue, Jul 28, 2020 at 6:23 AM Eric W. Biederman wrote:
>
> For exec all I care about are user space threads. So it appears the
> freezer infrastructure adds very little.
Yeah. 99% of the freezer stuff is for just adding the magic notations
for kernel threads, and for any user space threads it
Hi,
On Tue, Jul 28, 2020 at 09:11:11AM -0500, Dan Murphy wrote:
> Add the Texas Instruments BQ27561 battery monitor. The register address
> map is laid out the same as compared to other devices within the file.
> The battery status register has differing bits to determine if the
> battery is
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> Improves readability by storing >dev in a local variable.
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 30 +++---
> 1 file changed, 15 insertions(+),
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> Miscellaneous format fixes throughout the whole file.
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 28 ++--
> 1 file changed, 10 insertions(+), 18
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> Checks for non-zero return values to signal error conditions.
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 52 +-
> 1 file changed, 26
On Tue, Jul 28, 2020 at 6:15 PM Daniel Campello wrote:
>
> Simplify compensation stage by using regmap_read_poll_timeout().
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 25 ++---
> 1 file changed, 10
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> Uses for_each_set_bit() macro to loop over channel bitmaps.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 24 +---
> 1 file changed, 13 insertions(+),
On Tue, Jul 28, 2020 at 6:15 PM Daniel Campello wrote:
>
> Use __aligned(8) to ensure that the timestamp is correctly aligned
> when we call push_to_buffers
>
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
On Tue, Jul 28, 2020 at 6:15 PM Daniel Campello wrote:
>
> Uses .probe_new in place of .probe. Also uses device_get_match_data()
> for whoami matching.
Good one!
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Campello
> ---
>
> drivers/iio/proximity/sx9310.c | 37
On Tue, Jul 28, 2020 at 6:16 PM Daniel Campello wrote:
>
> Avoids unused warnings due to acpi/of table macros.
>
At the same time I would check if mod_devicetable.h is included.
> Signed-off-by: Daniel Campello
> Reported-by: kbuild test robot
--
With Best Regards,
Andy Shevchenko
> -Original Message-
> From: Greg Kroah-Hartman
> Sent: Tuesday, July 28, 2020 18:54
> To: Winkler, Tomas
> Cc: Usyskin, Alexander ; linux-
> ker...@vger.kernel.org
> Subject: Re: [char-misc-next] mei: add device type
>
> On Tue, Jul 28, 2020 at 06:25:46PM +0300, Tomas Winkler wrote:
When enable module, we find all ftrace_ops referenced it on the
ftrace_ops_list. But FTRACE_OPS_FL_DIRECT and FTRACE_OPS_FL_IPMODIFY
flag are special, and should not be set automatically. So warn and
skip ftrace_ops that have these two flags.
Also check if only one ftrace_ops references the
When module loaded and enabled, we will use __ftrace_replace_code
for module if any ftrace_ops referenced it found. But we will get
wrong ftrace_addr for module rec in ftrace_get_addr_new, because
rec->flags has not been setup correctly. It can cause the callback
function of a ftrace_ops has
On Tue, Jul 28, 2020 at 6:14 PM Daniel Campello wrote:
>
> Fixes enable/disable irq handling at various points. The driver needs to
> only enable/disable irqs if there is an actual irq handler installed.
> - enable_irq(data->client->irq);
> + if (!ret)
> +
Hi Tomasz,
On 7/27/20 3:35 PM, Tomasz Figa wrote:
> Hi Stanimir,
>
> On Fri, Jul 24, 2020 at 3:17 PM Stanimir Varbanov
> wrote:
>>
>>
>>
>> On 7/21/20 5:40 PM, Helen Koike wrote:
>>>
>>>
>>> On 7/21/20 11:30 AM, Stanimir Varbanov wrote:
Hi Helen,
On 7/21/20 4:54 PM, Helen Koike
On 7/27/2020 10:00 PM, Can Guo wrote:
Sometime dumps in IRQ handler are heavy enough to cause system stability
issues, move them to error handler.
Signed-off-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
On Tue, 2020-07-28 at 23:29 +0530, Dhiraj Sharma wrote:
> I ran checkpatch.pl script which reported a warning to use const keyword
> on line 370.Therefore I made this change.
checkpatch is a brainless script.
Not everything it suggests is appropriate.
> diff --git
On Tue, 28 Jul 2020 08:28:31 +0200
Christian Eggers wrote:
> Support for AMS AS73211 JENCOLOR(R) Digital XYZ Sensor.
>
> This driver has no built-in trigger. In order for making triggered
> measurements, an external (software) trigger driver like
> iio-trig-hrtimer or iio-trig-sysfs is
Hi Helen,
On 7/27/20 3:01 PM, Helen Koike wrote:
>
>
> On 7/24/20 10:16 AM, Stanimir Varbanov wrote:
>>
>>
>> On 7/21/20 5:40 PM, Helen Koike wrote:
>>>
>>>
>>> On 7/21/20 11:30 AM, Stanimir Varbanov wrote:
Hi Helen,
On 7/21/20 4:54 PM, Helen Koike wrote:
> Hi,
>
> On
On 7/27/2020 10:00 PM, Can Guo wrote:
The infos of the last interrupt status and its timestamp are very helpful
when debug system stability issues, e.g. IRQ starvation, so add them to
ufshcd_print_host_state. Meanwhile, UFS device infos like model name and
its FW version also come in handy
On Tue, Jul 28, 2020 at 9:32 AM Christian Eggers wrote:
>
> Support for AMS AS73211 JENCOLOR(R) Digital XYZ Sensor.
>
> This driver has no built-in trigger. In order for making triggered
> measurements, an external (software) trigger driver like
> iio-trig-hrtimer or iio-trig-sysfs is required.
>
I ran checkpatch.pl script which reported a warning to use const keyword
on line 370.Therefore I made this change.
Signed-off-by: Dhiraj Sharma
---
drivers/staging/android/ashmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/ashmem.c
On Tue, Jul 28, 2020 at 3:39 AM wrote:
>
> On Tue, Jul 28, 2020 at 12:01:31AM -0700, Xi Wang wrote:
> > The scope of select_idle_sibling idle cpu search is LLC. This
> > becomes a problem for the AMD CCX architecture, as the sd_llc is only
> > 4 cores. On a many core machine, the range of search
On Tue, 28 Jul 2020 at 16:35, Masami Hiramatsu wrote:
>
> On Tue, 28 Jul 2020 13:56:43 +0300
> Ard Biesheuvel wrote:
>
> > On Tue, 28 Jul 2020 at 11:17, Masami Hiramatsu wrote:
> > > > Masami or Peter should correct me if I am wrong, but it seems to me
> > > > that the way kprobes uses these
401 - 500 of 1424 matches
Mail list logo
