Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sis/init.c: In function ‘SiS_SetCRT1ModeRegs’:
drivers/video/fbdev/sis/init.c:2651:49: warning: variable ‘resindex’ set but
not used [-Wunused-but-set-variable]
drivers/video/fbdev/sis/init.c: In function ‘SiS_Generic_Convert
Neither 'sis.h' nor any of its consumers uses these tables.
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sis/init.h:144:28: warning: ‘SiS_VGA_DAC’ defined but not
used [-Wunused-const-variable=]
drivers/video/fbdev/sis/init.h:132:28: warning: ‘SiS_EGA_DAC’ defined but n
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/core/fb_notify.c:44: warning: Function parameter or member
'val' not described in 'fb_notifier_call_chain'
drivers/video/fbdev/core/fb_notify.c:44: warning: Function parameter or member
'v' not described in 'fb_notifier_call_
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sis/sis_main.c: In function ‘sisfb_post_xgi_ddr2’:
drivers/video/fbdev/sis/sis_main.c:5032:5: warning: variable ‘reg’ set but not
used [-Wunused-but-set-variable]
Cc: Thomas Winischhofer
Cc: Gerd Knorr
Cc: dri-de...@lists.f
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sis/oem310.h:213:28: warning: ‘SiS_TVDelay661_301B’
defined but not used [-Wunused-const-variable=]
drivers/video/fbdev/sis/oem310.h:203:28: warning: ‘SiS_TVDelay661_301’ defined
but not used [-Wunused-const-variable=]
Cc: T
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/nvidia/nv_setup.c: In function ‘NVWriteAttr’:
drivers/video/fbdev/nvidia/nv_setup.c:92:14: warning: variable ‘tmp’ set but
not used [-Wunused-but-set-variable]
drivers/video/fbdev/nvidia/nv_setup.c: In function ‘NVReadAttr’:
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/via/lcd.c: In function ‘viafb_lcd_set_mode’:
drivers/video/fbdev/via/lcd.c:540:29: warning: variable ‘mode_crt_table’ set
but not used [-Wunused-but-set-variable]
Cc: Florian Tobias Schandinat
Cc: linux-fb...@vger.kernel.org
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/neofb.c: In function ‘neo_init_hw’:
drivers/video/fbdev/neofb.c:1846:6: warning: variable ‘CursorMem’ set but not
used [-Wunused-but-set-variable]
Cc: Evgeny Novikov
Cc: Mike Rapoport
Cc: Oliver Kropp
Cc: "Thomas J. Moore"
Can't declare these under the same clause as their use, since
debugging is enabled manually with an '#if {0,1}', so mark them as
__maybe_unused instead to notify the compiler that this behaviour is
expected.
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/s1d13xxxfb.c: In fu
On Tue, Jan 12, 2021 at 9:56 PM Heikki Krogerus
wrote:
>
> On Wed, Jan 06, 2021 at 12:39:26AM +0800, Kyle Tso wrote:
> > PD3.0 Spec 6.8.1 describes how to handle Protocol Error. There are
> > general rules defined in Table 6-61 which regulate incoming Message
> > handling. If the incoming Message
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sis/init.c: In function ‘SiS_Generic_ConvertCRData’:
drivers/video/fbdev/sis/init.c:3543:37: warning: variable ‘cr_data2’ set but
not used [-Wunused-but-set-variable]
drivers/video/fbdev/sis/init.c:3542:39: warning: variable
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/aty/mach64_ct.c: In function ‘aty_init_pll_ct’:
drivers/video/fbdev/aty/mach64_ct.c:405:46: warning: variable ‘vga_dsp_on_off’
set but not used [-Wunused-but-set-variable]
drivers/video/fbdev/aty/mach64_ct.c:405:30: warning:
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/mx3fb.c:738: warning: Function parameter or member 'fbi'
not described in 'mx3fb_set_fix'
drivers/video/fbdev/mx3fb.c:738: warning: Excess function parameter 'info'
description in 'mx3fb_set_fix'
drivers/video/fbdev/mx3fb.c:
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/s1d13xxxfb.c:515: warning: Cannot understand *
Cc: Kristoffer Ericson
Cc: Thibaut VARENE
Cc: Ben Dooks
Cc: dri-de...@lists.freedesktop.org
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/video/fbdev/s
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/s3c-fb.c: In function ‘s3c_fb_probe_win’:
drivers/video/fbdev/s3c-fb.c:1176:28: warning: variable ‘var’ set but not used
[-Wunused-but-set-variable]
Cc: Jingoo Han
Cc: Ben Dooks
Cc: linux-fb...@vger.kernel.org
Cc: dri-de...
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/cirrusfb.c:2815: warning: Function parameter or member
'info' not described in 'cirrusfb_dbg_print_regs'
drivers/video/fbdev/cirrusfb.c:2815: warning: Function parameter or member
'regbase' not described in 'cirrusfb_dbg_prin
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/riva/riva_hw.c: In function ‘nv10CalcArbitration’:
drivers/video/fbdev/riva/riva_hw.c:845:23: warning: variable ‘vus_p’ set but
not used [-Wunused-but-set-variable]
drivers/video/fbdev/riva/riva_hw.c:845:16: warning: variable
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/s3c-fb.c:104: warning: Function parameter or member
'osd_stride' not described in 's3c_fb_variant'
drivers/video/fbdev/s3c-fb.c:174: warning: Function parameter or member
'variant' not described in 's3c_fb_win'
drivers/video
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/cirrusfb.c: In function ‘WHDR’:
drivers/video/fbdev/cirrusfb.c:2466:16: warning: variable ‘dummy’ set but not
used [-Wunused-but-set-variable]
Cc: Jeff Garzik
Cc: dri-de...@lists.freedesktop.org
Cc: linux-fb...@vger.kernel.o
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/mx3fb.c: In function ‘sdc_disable_channel’:
drivers/video/fbdev/mx3fb.c:448:11: warning: variable ‘enabled’ set but not
used [-Wunused-but-set-variable]
Cc: Sam Ravnborg
Cc: Arnd Bergmann
Cc: Software Engineering
Cc: dri-d
These are only used if SST_DEBUG_FUNC is set.
Declare them under the same clause as their use.
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/sstfb.c: In function ‘sst_detect_ics’:
drivers/video/fbdev/sstfb.c:934:26: warning: variable ‘n_clk1_b’ set but not
used [-Wunuse
'pending' is only used if FBCONDEBUG is defined.
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/core/fbcon.c: In function ‘fbcon_exit’:
drivers/video/fbdev/core/fbcon.c:3295:7: warning: variable ‘pending’ set but
not used [-Wunused-but-set-variable]
Cc: car...@compsci.br
On Wed, 2021-01-13 at 07:52 -0600, Rob Herring wrote:
> On Fri, Jan 08, 2021 at 03:34:16PM +0200, Matti Vaittinen wrote:
> > The BD71828 allows configuring the clk32kout pin mode to CMOS or
> > open-drain. Add device-tree property for specifying the preferred
> > mode.
> >
> > Signed-off-by: Mat
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/riva/riva_hw.c: In function ‘nv10CalcArbitration’:
drivers/video/fbdev/riva/riva_hw.c:849:9: warning: variable ‘pclks_2_top_fifo’
set but not used [-Wunused-but-set-variable]
drivers/video/fbdev/riva/riva_hw.c:848:43: warning
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/tdfxfb.c: In function ‘att_outb’:
drivers/video/fbdev/tdfxfb.c:209:16: warning: variable ‘tmp’ set but not used
[-Wunused-but-set-variable]
Cc: "Gustavo A. R. Silva"
Cc: Hannu Mallat
Cc: Frodo Looijaard
Cc: Philip Edelbroc
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/aty/radeon_monitor.c: In function ‘radeon_probe_screens’:
drivers/video/fbdev/aty/radeon_monitor.c:491:8: warning: variable ‘mon_types’
set but not used [-Wunused-but-set-variable]
Cc: Benjamin Herrenschmidt
Cc: linux-fb...@
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/pm2fb.c:1515: warning: Function parameter or member 'pdev'
not described in 'pm2fb_probe'
drivers/video/fbdev/pm2fb.c:1515: warning: Function parameter or member 'id'
not described in 'pm2fb_probe'
drivers/video/fbdev/pm2fb.
On Wed, 13 Jan 2021 at 15:49, Arnd Bergmann wrote:
>
> On Tue, Jan 12, 2021 at 2:46 PM Vincent Guittot
> wrote:
> > On Tue, 12 Jan 2021 at 12:25, Guillaume Tucker
> > wrote:
> > >
> > > Some details can be found here:
> > >
> > > https://kernelci.org/test/case/id/5ffb978de38e717501c94cd8/
> >
The following commit has been merged into the irq/urgent branch of tip:
Commit-ID: ce09ccc50208c04a1b03abfd530b5d6314258fd0
Gitweb:
https://git.kernel.org/tip/ce09ccc50208c04a1b03abfd530b5d6314258fd0
Author:Thomas Gleixner
AuthorDate:Wed, 13 Jan 2021 15:43:18 +01:00
Commit
'dac_type' is only used in the '#ifdef CONFIG_ATARI' clause.
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/aty/atyfb_base.c: In function ‘aty_init’:
drivers/video/fbdev/aty/atyfb_base.c:2363:6: warning: variable ‘dac_type’ set
but not used [-Wunused-but-set-variable]
Cc
Fixes the following W=1 kernel build warning(s):
drivers/video/of_videomode.c:32: warning: Function parameter or member 'np'
not described in 'of_get_videomode'
drivers/video/of_videomode.c:32: warning: Function parameter or member 'vm'
not described in 'of_get_videomode'
drivers/video/of_vid
On 13/01/21 3:57 pm, Can Guo wrote:
> User layer may access sysfs nodes when system PM ops or error handling
> is running, which can cause various problems. Rename eh_sem to host_sem
> and use it to protect PM ops and error handling from user layer intervene.
>
> Acked-by: Avri Altman
> Reviewed-
Linus,
please pull sound fixes for v5.11-rc4 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-5.11-rc4
The topmost commit is 20c7842ed8374e1c3ee750b2fe7ca8cdd071bda6
sound fixes for 5.11-rc4
Here
On 1/13/21 8:36 AM, Sean Young wrote:
> On Tue, Jan 12, 2021 at 10:51:31PM -0600, Samuel Holland wrote:
>> In preparation for adding suspend/resume hooks, factor out the hardware
>> initialization from the driver probe/remove functions.
>>
>> The timeout programmed during init is taken from the `st
On Tue, Jan 12, 2021 at 06:35:50PM -0800, Linus Torvalds wrote:
> On Tue, Jan 12, 2021 at 6:14 PM Linus Torvalds
> wrote:
> >
> > Ack. I'll assume I get this the usual ways from the arm64 tree..
>
> Oh.. Actually, while you can use my ack if you decide to go this way,
> I do wonder if it might no
Thanks Björn!
On Fri, 8 Jan 2021 at 20:07, Bjorn Andersson wrote:
>
> On Fri 08 Jan 06:04 CST 2021, Robert Foss wrote:
>
> > This driver supports multiple architecture versions of the Qualcomm ISP.
> > The CAMSS architecure which this driver is name after, and with the
> > introduction of this se
On Tue, Jan 12, 2021 at 8:20 PM Frank Rowand wrote:
>
> On 1/12/21 2:46 PM, Rob Herring wrote:
> > On Tue, Jan 12, 2021 at 2:05 PM Frank Rowand wrote:
> >>
> >> On 1/12/21 1:41 PM, Rob Herring wrote:
> >>> On Tue, Jan 12, 2021 at 1:06 PM Frank Rowand
> >>> wrote:
>
> On 1/12/21 8:04 A
On Fri, Jan 8, 2021 at 6:52 PM Benjamin Tissoires
wrote:
>
> Hi Doug,
>
> On Wed, Jan 6, 2021 at 2:35 AM Doug Anderson wrote:
> >
> > Benjamin,
> >
> > On Fri, Dec 11, 2020 at 2:24 PM Douglas Anderson
> > wrote:
> > >
> > > The goal of this series is to support the Goodix GT7375P touchscreen.
>
On 05-01-21, 10:05, Amelie Delaunay wrote:
> STM32 USBPHYC controls the USB PLL. PLL requires to be powered with 1v1 and
> 1v8
> supplies. To ensure a good behavior of the PLL, during boot, runtime and
> suspend/resume sequences, this series reworks its management to fix regulators
> issues and im
Hi Samuel,
On Wed, Jan 13, 2021 at 09:00:20AM -0600, Samuel Holland wrote:
> On 1/13/21 8:36 AM, Sean Young wrote:
> > On Tue, Jan 12, 2021 at 10:51:31PM -0600, Samuel Holland wrote:
> >> In preparation for adding suspend/resume hooks, factor out the hardware
> >> initialization from the driver pr
On Wed, Jan 13, 2021 at 11:59:20AM +0100, Mauro Carvalho Chehab wrote:
> Changeset b00aedf978aa ("doc: Convert to rcu_dereference.txt to
> rcu_dereference.rst")
> renamed: Documentation/RCU/rcu_dereference.txt
> to: Documentation/RCU/rcu_dereference.rst.
>
> Update its cross-reference accordingly
On Wed, 13 Jan 2021 18:05:43 +0530
Kirti Wankhede wrote:
> On 1/13/2021 2:50 AM, Alex Williamson wrote:
> > On Thu, 7 Jan 2021 17:28:57 +0800
> > Keqian Zhu wrote:
> >
> >> Defer checking whether vfio_dma is of fully-dirty in update_user_bitmap
> >> is easy to lose dirty log. For example, aft
defconfig
> i386 allyesconfig
> sparcallyesconfig
> sparc defconfig
> i386 tinyconfig
> i386 defconfig
>
Hi Dinghao,
On Sun, 2021-01-10 at 16:02 +0800, Dinghao Liu wrote:
> When kmalloc() fails, tmp_tfm allocated by
> crypto_alloc_shash() has not been freed, which
> leads to memleak.
>
> Fixes: d46eb3699502b ("evm: crypto hash replaced by shash")
> Signed-off-by: Dinghao Liu
This patch is now queu
Working on a battery charger and fuel gauge driver it happened to
have the need to read from VADC_LR_MUX2_BAT_ID channel. Here is
the declaration from downstream msm8916.dtsi:
chan@31 {
label = "batt_id";
reg = <0x31>;
qcom,decimation = <0>;
Working on a battery charger and fuel gauge driver it happened to
have the need to read from VADC_LR_MUX2_BAT_ID channel. Here is
the declaration from downstream msm8916.dtsi:
chan@31 {
label = "batt_id";
reg = <0x31>;
qcom,decimation = <0>;
Checking at both msm8909-pm8916.dtsi and msm8916.dtsi from downstream
it is indicated that "batt_id" channel has to be scaled with the default
function:
chan@31 {
label = "batt_id";
reg = <0x31>;
qcom,decimation = <0>;
qcom,pr
Signed-off-by: Nikolay Borisov
---
kernel/locking/rwsem.h | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 kernel/locking/rwsem.h
diff --git a/kernel/locking/rwsem.h b/kernel/locking/rwsem.h
deleted file mode 100644
index e69de29bb2d1..
--
2.25.1
On 1/7/2021 7:28 PM, Vipin Sharma wrote:
Hardware memory encryption is available on multiple generic CPUs. For
example AMD has Secure Encrypted Virtualization (SEV) and SEV -
Encrypted State (SEV-ES).
These memory encryptions are useful in creating encrypted virtual
machines (VMs) and user spa
On Fri, Jan 08, 2021 at 04:04:57PM +, Richard Fitzgerald wrote:
> The audio-graph-card driver has properties for configuring the clocking
> for DAIs within a component, but is missing properties for setting
> up the PLLs and sysclks of the component.
>
> This patch adds the two new properties
On Fri, 08 Jan 2021 17:30:04 +0100, Jonathan Neuschäfer wrote:
> The NPCM750 Timer/Watchdog Controller has multiple interrupt lines,
> connected to multiple timers. The driver uses timer 0 for timer
> interrupts, so the interrupt line corresponding to timer 0 should be
> specified in DT.
>
> I rem
Hi Greg,
On Wed, Jan 06, 2021 at 10:44:13AM -0800, Hemant Kumar wrote:
> This patch series adds support for UCI driver. UCI driver enables userspace
> clients to communicate to external MHI devices like modem. UCI driver probe
> creates standard character device file nodes for userspace clients to
On 13/01/2021 11:11, Marc Zyngier wrote:
> On 2021-01-07 20:05, Greg Kroah-Hartman wrote:
>> On Thu, Dec 17, 2020 at 07:16:58PM -0800, Saravana Kannan wrote:
>>> As discussed in LPC 2020, cyclic dependencies in firmware that couldn't
>>> be broken using logic was one of the last remaining reasons
On Wed, 13 Jan 2021 02:11:23 +0800, Kai-Heng Feng wrote:
> Instead of queueing jackpoll_work, runtime resume the codec to let it
> use different jack detection methods based on jackpoll_interval.
>
> This partially matches SOF driver's behavior with commit a6e7d0a4bdb0
> ("ALSA: hda: fix jack dete
On 2021-01-13 13:59, Nicolas Saenz Julienne wrote:
Hi All,
On Tue, 2021-01-12 at 16:03 -0800, Florian Fainelli wrote:
On 1/5/21 7:41 PM, Claire Chang wrote:
Add the initialization function to create restricted DMA pools from
matching reserved-memory nodes in the device tree.
Signed-off-by: Cl
On Wed, 13 Jan 2021 12:15:43 +0100, Mauro Carvalho Chehab wrote:
> Changeset 81437cc3b0d9 ("Merge series "dt-bindings: stm32: convert audio
> dfsdm to json-schema" from Olivier Moysan :")
> removed bindings/sound/st,stm32-adfsdm.txt, as stm32-* audio
> bindings are now under: bindings/iio/adc/st,s
Rob Herring 於 2021年1月12日 週二 下午10:49寫道：
>
> On Thu, 07 Jan 2021 11:11:11 +0800, Yongqiang Niu wrote:
> > rdma fifo size may be different even in same SOC, add this
> > property to the corresponding rdma
Applied to mediatek-drm-next [1], thanks.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git
On Sat, 5 Dec 2020 01:40:56 +0100, Linus Walleij wrote:
> The struct ab8500_regulator_platform_data was a leftover
> since the days before we probed all regulators from the
> device tree. The ab8500-ext regulator was the only used,
> defining platform data and register intialization that
> was neve
On Fri, 4 Dec 2020 15:03:41 +0100, Linus Walleij wrote:
> The struct ab8500_regulator_platform_data was a leftover
> since the days before we probed all regulators from the
> device tree. The ab8500-ext regulator was the only used,
> defining platform data and register intialization that
> was neve
Hi Anshuman,
The driver looks overall good to me. Please find some minor comments below
On 1/13/21 4:18 AM, Anshuman Khandual wrote:
Trace Buffer Extension (TRBE) implements a trace buffer per CPU which is
accessible via the system registers. The TRBE supports different addressing
modes includi
On Mon, 11 Jan 2021 16:13:01 -0800, Stephen Boyd wrote:
> We don't need to force this to be trigger high here, as the firmware
> properly configures the irq flags already. Drop it to save a line.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1
On Sat, 12 Dec 2020 21:29:48 -0800, Stephen Boyd wrote:
> We don't need to force this to be trigger high here, as the firmware
> properly configures the irq flags already. Drop it to save a line.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1
On Wed, Jan 13, 2021 at 01:39:18PM +0200, Heikki Krogerus wrote:
> On Wed, Jan 13, 2021 at 12:40:03AM +, Daniel Scally wrote:
> > On 11/01/2021 14:10, Heikki Krogerus wrote:
...
> > > +/**
> > > + * device_remove_software_node - Remove device's software node
> > > + * @dev: The device with th
On Fri, 08 Jan 2021 17:23:31 -0800, Philip Chen wrote:
> In Chrome OS, the keyboard matrix can be split to two groups:
>
> The keymap for the top row keys can be customized based on OEM
> preference, while the keymap for the other keys is generic/fixed
> across boards.
>
> This patch creates marc
On Tue, 24 Nov 2020 12:18:35 +0800, Ramuthevar, Vadivel MuruganX wrote:
> Add QSPI controller support for Intel LGM SoC.
>
> Patches to move move bindings over to
> "Documentation/devicetree/bindings/spi/" directory and also added compatible
> Support for Intel platform.
>
> dt-bindings: spi: cad
On Fri, 08 Jan 2021 23:50:02 +0100, Adrien Grassein wrote:
> nxp,phase-shift is an enum so use enum format to describe it.
> Minimum and maximum values are also wrong.
>
> Signed-off-by: Adrien Grassein
> ---
> .../bindings/regulator/nxp,pf8x00-regulator.yaml | 14 ++
> 1 file chan
Hi,
If I remember well, the removed lines have to do with the VGA/accelerator
mode of the chip. The current driver always runs the chip in accelerator
mode. Suppose you would want to support high resolution hardware text
modes with the driver (fbdev bpp=0), then you would need to switch the
c
Acked-by: Oleg Nesterov
On 01/13, Marcus Huewe wrote:
>
> In case of a PTRACE_SEIZE request, the PT_SEIZED flag is always set
> at the beginning of ptrace_attach. Hence, there is no need to set
> it again (neither "flags" nor "seize" are modified in between/after
> the initial assignment).
>
>
On Wed, Jan 13, 2021 at 01:56:45PM +0100, David Hildenbrand wrote:
> On 11.01.21 20:40, Mike Rapoport wrote:
> > From: Mike Rapoport
> >
> > The first 4Kb of memory is a BIOS owned area and to avoid its allocation
> > for the kernel it was not listed in e820 tables as memory. As the result,
> > p
On 05/01/2021 16:41, Lukasz Luba wrote:
Devfreq framework supports 2 modes for monitoring devices.
Use delayed timer as default instead of deferrable timer
in order to monitor the GPU status regardless of CPU idle.
Signed-off-by: Lukasz Luba
Looks reasonable to me.
Reviewed-by: Steven Price
Hi Shameer,
On 1/8/21 6:05 PM, Shameerali Kolothum Thodi wrote:
> Hi Eric,
>
>> -Original Message-
>> From: Eric Auger [mailto:eric.au...@redhat.com]
>> Sent: 18 November 2020 11:22
>> To: eric.auger@gmail.com; eric.au...@redhat.com;
>> io...@lists.linux-foundation.org; linux-kernel@v
On 01/13, Chao Yu wrote:
> On 2021/1/13 6:36, Jaegeuk Kim wrote:
> > On 01/12, Chao Yu wrote:
> > > On 2021/1/12 10:04, Jaegeuk Kim wrote:
> > > > On 01/12, Chao Yu wrote:
> > > > > On 2021/1/11 19:45, Chao Yu wrote:
> > > > > > On 2021/1/11 18:31, Chao Yu wrote:
> > > > > > > On 2021/1/11 17:48, J
On Wed, Dec 16, 2020 at 08:28:43PM +0800, Yanan Wang wrote:
> In dirty-logging, or dirty-logging-stopped time, even normal running
> time of a guest configed with huge mappings and numbers of vCPUs,
> translation faults by different vCPUs on the same GPA could occur
> successively almost at the sam
On Wed, 13 Jan 2021, Daniël Mantione wrote:
> Hi,
>
> If I remember well, the removed lines have to do with the VGA/accelerator
> mode of the chip. The current driver always runs the chip in accelerator
> mode. Suppose you would want to support high resolution hardware text modes
> with the drive
On Wed, 13 Jan 2021 09:48:18 +0530, Anshuman Khandual wrote:
> From: Suzuki K Poulose
>
> Document the device tree bindings for Trace Buffer Extension (TRBE).
>
> Cc: Anshuman Khandual
> Cc: Mathieu Poirier
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Suzuki K Poulose
On Wed, 13 Jan 2021 07:08:45 +, Troy Lee wrote:
> We add binding for supporting a new AST2600 PWM/Fan hwmon driver.
>
> Changes since v1:
> - dt binding with DT schema format
>
> Signed-off-by: Troy Lee
> ---
> .../hwmon/aspeed,ast2600-pwm-tachometer.yaml | 137 ++
> 1 file
On Tue, 12 Jan 2021 17:21:42 -0800, Minchan Kim wrote:
> From: Hyesoo Yu
>
> Document devicetree binding for chunk cma heap on dma heap framework.
>
> The DMA chunk heap supports the bulk allocation of higher order pages.
>
> Signed-off-by: Hyesoo Yu
> Signed-off-by: Minchan Kim
> Signed-off-
On 1/13/21 3:35 PM, Steven Price wrote:
On 05/01/2021 16:41, Lukasz Luba wrote:
Devfreq framework supports 2 modes for monitoring devices.
Use delayed timer as default instead of deferrable timer
in order to monitor the GPU status regardless of CPU idle.
Signed-off-by: Lukasz Luba
Looks r
On Wed, Jan 13, 2021 at 8:23 AM Vaittinen, Matti
wrote:
>
>
> On Wed, 2021-01-13 at 07:53 -0600, Rob Herring wrote:
> > On Tue, Jan 12, 2021 at 08:10:14AM +0200, Matti Vaittinen wrote:
> > > On Mon, 2021-01-11 at 13:09 -0600, Rob Herring wrote:
> > > > On Fri, Jan 08, 2021 at 03:36:38PM +0200, Mat
On Wed, Dec 16, 2020 at 08:28:44PM +0800, Yanan Wang wrote:
> We now mark the page dirty and set the bitmap before calling fault handlers
> in user_mem_abort(), and we might end up having spurious dirty pages if
> update of permissions or mapping has failed.
> So, mark the page dirty only if the fa
On Wed, Jan 13, 2021 at 02:23:47PM +, Lee Jones wrote:
> Clear-up any confusion surrounding the Fixes: tag with regards to the
> need to Cc: the stable mailing list when submitting stable patch
> candidates.
>
> Cc: Greg Kroah-Hartman
> Cc: Jonathan Corbet
> Cc: linux-...@vger.kernel.org
> S
On Wed, Jan 13, 2021 at 09:00:19AM +0900, Kuninori Morimoto wrote:
> Ahh, sorry for my unclear comment.
> I think "PLL settings" is very board/platform specific,
> so, adding such code to common driver will be issue in the future.
> This is the reason why I don't want add it to audio-graph-card.
On Wed, Jan 13, 2021 at 8:52 AM Matti Vaittinen
wrote:
>
>
> On Wed, 2021-01-13 at 07:52 -0600, Rob Herring wrote:
> > On Fri, Jan 08, 2021 at 03:34:16PM +0200, Matti Vaittinen wrote:
> > > The BD71828 allows configuring the clk32kout pin mode to CMOS or
> > > open-drain. Add device-tree property
On Wed, 13 Jan 2021 11:59:19 +0100
Mauro Carvalho Chehab wrote:
> Changeset 6ced946a4bba ("dt-bindings:iio:dac:microchip,mcp4725 yaml
> conversion")
> renamed: Documentation/devicetree/bindings/iio/dac/mcp4725.txt
> to: Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml.
>
> Updat
On Wed, 13 Jan 2021 11:59:24 +0100
Mauro Carvalho Chehab wrote:
> Changeset b70d154d6558 ("dt-bindings:iio:adc: convert adc.txt to yaml")
> renamed: Documentation/devicetree/bindings/iio/adc/adc.txt
> to: Documentation/devicetree/bindings/iio/adc/adc.yaml.
>
> Update its cross-reference accordin
On Tue, Jan 12, 2021 at 09:20:10PM -0800, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit c318840fb2a42ce25febc95c4c19357acf1ae5ca
> Author: Alan Stern
> Date: Wed Dec 30 16:20:44 2020 +
>
> USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
>
> bisection l
On Wed, Jan 13, 2021 at 12:40:03AM +, Daniel Scally wrote:
> On 11/01/2021 14:10, Heikki Krogerus wrote:
...
> > +/**
> > + * device_remove_software_node - Remove device's software node
> > + * @dev: The device with the software node.
> > + *
> > + * This function will unregister the software
On Wed, Jan 13, 2021 at 05:55:04PM +0200, Andy Shevchenko wrote:
> On Wed, Jan 13, 2021 at 12:40:03AM +, Daniel Scally wrote:
> > On 11/01/2021 14:10, Heikki Krogerus wrote:
>
> ...
>
> > > +/**
> > > + * device_remove_software_node - Remove device's software node
> > > + * @dev: The device w
On Wed, Jan 13, 2021 at 03:43:09PM +0100, Geert Uytterhoeven wrote:
> In general, device drivers should not be enabled by default.
>
> Fixes: 657bc1d10bfc23ac ("r8153_ecm: avoid to be prior to r8152 driver")
> Signed-off-by: Geert Uytterhoeven
> ---
> drivers/net/usb/Kconfig | 1 -
> 1 file chan
On Wed, Jan 13, 2021 at 13:49:12 +0100, Rolf Eike Beer wrote:
> Otherwise build fails if the headers are not in the default location. While at
> it also ask pkg-config for the libs, with fallback to the existing value.
>
> Signed-off-by: Rolf Eike Beer
Reviewed-by: Ben Boeckel
> Cc: sta...@vge
On Wed, Jan 13, 2021 at 10:57:58 -0500, Ben Boeckel wrote:
> > Cc: sta...@vger.kernel.org # 5.6.x
>
> Note that keyutils is not in the kernel, so I don't know how useful this
> is.
Scratch that; I remember a similar patch for keyutils; this is for the
kernel.
--Ben
Qualcomm QCA639x is a family of WiFi + Bluetooth chips, with BT part
being controlled through the UART and WiFi being present on PCIe
bus. Both blocks share common power sources wich should be turned on
before either of devices can be probed. Declare common 'qca639x' driver
providing a power domain
Qualcomm QCA6390/1 is a family of WiFi + Bluetooth SoCs, with BT part
being controlled through the UART and WiFi being present on PCIe bus.
Both blocks share common power sources. Add binding to describe power
sequencing required to power up this device.
Signed-off-by: Dmitry Baryshkov
---
.../b
Qualcomm QCA639x is a family of WiFi + Bluetooth SoCs, with BT part
being controlled through the UART and WiFi being present on PCIe
bus. Both blocks share common power sources. Add device driver handling
power sequencing of QCA6390/1.
Signed-off-by: Dmitry Baryshkov
---
drivers/misc/Kconfig
Andrey Konovalov (2):
kasan, mm: fix conflicts with init_on_alloc/free
kasan, arm64: fix pointer tags in KASAN reports
arch/arm64/mm/fault.c | 2 ++
mm/slub.c | 7 ---
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.30.0.284.gd98b1dd5eaa7-goog
As of the "arm64: expose FAR_EL1 tag bits in siginfo" patch, the address
that is passed to report_tag_fault has pointer tags in the format of 0x0X,
while KASAN uses 0xFX format (note the difference in the top 4 bits).
Fix up the pointer tag before calling kasan_report.
Link:
https://linux-review
A few places where SLUB accesses object's data or metadata were missed in
a previous patch. This leads to false positives with hardware tag-based
KASAN when bulk allocations are used with init_on_alloc/free.
Fix the false-positives by resetting pointer tags during these accesses.
Link:
https://l
On 1/12/21 9:38 PM, Gilad Reti wrote:
Add a test to check that the verifier is able to recognize spilling of
PTR_TO_MEM registers, by reserving a ringbuf buffer, forcing the spill
of a pointer holding the buffer address to the stack, filling it back
in from the stack and writing to the memory
On 1/12/21 10:21 AM, Faiyaz Mohammed wrote:
> Reading the sys slab alloc_calls, free_calls returns the available object
> owners, but the size of this file is limited to PAGE_SIZE
> because of the limitation of sysfs attributes, it is returning the
> partial owner info, which is not sufficient to d
Hi,
On Wed, Jan 13, 2021 at 7:09 AM Benjamin Tissoires
wrote:
>
> > I wanted to apply the series yesterday, but for these kinds of changes
> > I like giving it a spin on actual hardware. Turns out that my XPS-13
> > can not boot to v5.11-rc2, which makes testing the new branch slightly
> > more d
501 - 600 of 1327 matches
Mail list logo
