There is a NULL pointer dereference of dev_name in nfs_parse_devname()
The oops looks something like:
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:nfs_fs_mount+0x3b6/0xc20 [nfs]
...
Call Trace:
? ida_alloc_range+0x34b/0x3d0
? nfs_clone_su
The following patchset applies cleanly on linux 5.0-rc2.
It adds support for the pms405 spmi regulators and configures s3 as a
supply.
The dts modifications required to enable voltage scaling will be
posted after the currently pending cpufreq patches are merged.
Jorge Ramirez-Ortiz (3):
dt-bin
The PMS405 supports 5 SMPS and 13 LDO regulators.
Signed-off-by: Jorge Ramirez-Ortiz
---
.../bindings/regulator/qcom,spmi-regulator.txt | 24 ++
1 file changed, 24 insertions(+)
diff --git
a/Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt
b/Document
The PMS405 has 5 HFSMPS and 13 LDO regulators,
This commit adds support for one of the 5 HFSMPS regulators (s3) to
the spmi regulator driver.
The PMIC HFSMPS 430 regulators have 8 mV step size and a voltage
control scheme consisting of two 8-bit registers defining a 16-bit
voltage set point in u
The PMS405 sports 5 SMPS and 13 LDO regulators.
Signed-off-by: Jorge Ramirez-Ortiz
---
arch/arm64/boot/dts/qcom/pms405.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi
b/arch/arm64/boot/dts/qcom/pms405.dtsi
index ad2b62d..6fbdb1
On Mon, 28 Jan 2019 at 18:40, Faiz Abbas wrote:
>
> Hi,
>
> On 28/01/19 3:50 PM, Chunyan Zhang wrote:
> > On Thu, 24 Jan 2019 at 19:41, Adrian Hunter wrote:
> >>
> >> On 11/01/19 1:08 PM, Faiz Abbas wrote:
> >>> From: Chunyan Zhang
> >>>
> >>> Some standard SD host controllers can support both e
On Sat, Jan 26, 2019 at 11:23:20AM +0100, Christian Brauner wrote:
> Several users have tried to only rely on binderfs to provide binder devices
> and set CONFIG_ANDROID_BINDER_DEVICES="" empty. This is a great use-case of
> binderfs and one that was always intended to work. However, this is
> curr
On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote:
> On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn wrote:
> > spi-3wire: again, only set by MAXIM DS-1302 which always needs this
> > setting; driver could set this
> For DS1302, this is probable true.
> Some devices may support both
Hi Julien,
On 21/01/2019 15:33, Julien Thierry wrote:
> When using VHE, the host needs to clear HCR_EL2.TGE bit in order
> to interract with guest TLBs, switching from EL2&0 translation regime
(interact)
> to EL1&0.
>
> However, some non-maskable asynchronous event could happen while TGE is
>
On Mon, Jan 28, 2019 at 02:47:29PM +0300, Dan Carpenter wrote:
> On Sat, Jan 26, 2019 at 11:23:20AM +0100, Christian Brauner wrote:
> > Several users have tried to only rely on binderfs to provide binder devices
> > and set CONFIG_ANDROID_BINDER_DEVICES="" empty. This is a great use-case of
> > bin
On 28/01/2019 12:47, Mark Brown wrote:
On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote:
On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn wrote:
spi-3wire: again, only set by MAXIM DS-1302 which always needs this
setting; driver could set this
For DS1302, this is probable t
Hi Jonas,
On Mon, Jan 28, 2019 at 12:51 PM Jonas Bonn wrote:
> On 28/01/2019 12:47, Mark Brown wrote:
> > On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote:
> >> On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn wrote:
> >
> >>> spi-3wire: again, only set by MAXIM DS-1302 which always
On Mon, 2019-01-28 at 10:51 +0100, Michael Straube wrote:
> Instead of first asign 'wrqu.data.length = p - buff' use 'p - buff'
> directly in min_t() in the subsequent asignment. Clears a line over
> 80 characters checkpatch warning.
Thank you. I believe you should include Larry Finger
in the cc
On Sun, Jan 27, 2019 at 10:24:16PM +0530, Prashantha SP wrote:
> fixed coding style issue.
>
> Signed-off-by: Prashantha SP
^^
Please use your full name that you would use to sign legal documents.
> ---
> drivers/staging/media/ipu3/ipu3-css.c | 178 ++---
There is a NULL pointer dereference of devname in strspn()
The oops looks something like:
CIFS: Attempting to mount (null)
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:strspn+0x0/0x50
...
Call Trace:
? cifs_parse_mount_options+0x222/0x1710
Hi MyungJoo,
On 2019-01-28 09:05, MyungJoo Ham wrote:
>> This way devfreq core ensures that all its devices will be set to safe
>> operation points before reboot operation. There are board on which some
>> aggressive power saving operation points are behind the capabilities of
>> the bootloader to
On Mon, Jan 28, 2019 at 1:36 PM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> ... so that they can get CCed on platform patches.
>
Acked-by: Andy Shevchenko
> Signed-off-by: Borislav Petkov
> Cc: Darren Hart
> Cc: Andy Shevchenko
> Cc: x...@kernel.org
> ---
> MAINTAINERS | 9 +++
On Mon, 21 Jan 2019 15:33:39 +,
Julien Thierry wrote:
>
> Provide a higher priority to be used for pseudo-NMIs. When such an
> interrupt is received, keep interrupts fully disabled at CPU level to
> prevent receiving other pseudo-NMIs while handling the current one.
>
> Signed-off-by: Julien
Hi Vishal,
On Mon, Jan 14, 2019 at 09:47:41AM +, Vishal Sagar wrote:
> Hi Sakari,
>
> Thanks for reviewing this.
>
> > -Original Message-
> > From: Sakari Ailus [mailto:sakari.ai...@linux.intel.com]
> > Sent: Tuesday, January 08, 2019 6:35 PM
> > To: Vishal Sagar
> > Cc: Hyun Kwon
On Mon, Jan 28, 2019 at 11:49 AM Ricardo Ribalda Delgado
wrote:
>
> Add support for Texas Instruments ADS7866, ADS7867 and ADS7868
> 8/10/12 bit Single channel ADC.
>
> Datasheet: http://www.ti.com/lit/ds/symlink/ads7868.pdf
>
> Cc: Alexandru Ardelean
> Signed-off-by: Ricardo Ribalda Delgado
> -
On Fri, 25 Jan 2019 at 21:09, Paul Cercueil wrote:
>
> Drop the custom code to get the 'cd' and 'wp' GPIOs. The driver now
> calls mmc_of_parse() which will init these from devicetree or
> device properties.
>
> Also drop the custom code to get the 'power' GPIO. The MMC core
> provides us with the
Hi Shuah,
On 1/24/19 9:32 PM, Shuah Khan wrote:
> Media Device Allocator API to allows multiple drivers share a media device.
> This API solves a very common use-case for media devices where one physical
> device (an USB stick) provides both audio and video. When such media device
> exposes a stan
On Wed, 23 Jan 2019 at 13:05, Chaotian Jing wrote:
>
> to set cmd internal delay, need set PAD_TUNE register but not PAD_CMD_TUNE
> register.
>
> Signed-off-by: Chaotian Jing
Applied for fixes, adding a fixes+stable tag, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/mtk-sd.c | 2 +-
> 1
On Mon, 21 Jan 2019 15:33:40 +,
Julien Thierry wrote:
>
> Add accessors to the GIC distributor/redistributors priority registers.
>
> Signed-off-by: Julien Thierry
> Cc: Thomas Gleixner
> Cc: Jason Cooper
> Cc: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-common.c | 10 ++
> dri
On Monday, January 28, 2019 9:32:44 AM CET Daniel Lezcano wrote:
> On 28/01/2019 07:41, Amit Kucheria wrote:
> > All cpufreq drivers do similar things to register as a cooling device.
> > Provide a cpufreq driver flag so drivers can just ask the cpufreq core
> > to register the cooling device on th
On Mon, 21 Jan 2019 15:33:41 +,
Julien Thierry wrote:
>
> Implement NMI callbacks for GICv3 irqchip. Install NMI safe handlers
> when setting up interrupt line as NMI.
>
> Only SPIs and PPIs are allowed to be set up as NMI.
>
> Signed-off-by: Julien Thierry
> Cc: Thomas Gleixner
> Cc: Jas
This adds an smp_acquire__after_ctrl_dep() barrier on successful
decrease of refcounter value from 1 to 0 for refcount_dec(sub)_and_test
variants and therefore gives stronger memory ordering guarantees than
prior versions of these functions.
Co-Developed-by: Peter Zijlstra (Intel)
Signed-off-by:
Hi Myungho,
> tiocmget() and tiocmset() operations are optional and some tty drivers
> like pty miss the operations. We need NULL check before referencing
> them.
>
> Reported-by: syzbot+a950165cbb86bdd02...@syzkaller.appspotmail.com
> Signed-off-by: Myungho Jung
> ---
> drivers/bluetooth/hci_at
While debugging some crashes related to virtio-balloon deflation that
happened under the old balloon migration code, I stumbled over a possible
race I think.
What we experienced:
drivers/virtio/virtio_balloon.c:release_pages_balloon():
- WARNING: CPU: 13 PID: 6586 at lib/list_debug.c:59 __list_de
Hi Myungho,
> tty_set_termios() should be called with slave side of pty driver. So, If
> tty driver is pty master, it needs to be switched to ->link.
>
> Reported-by: syzbot+a950165cbb86bdd02...@syzkaller.appspotmail.com
> Signed-off-by: Myungho Jung
> ---
> drivers/bluetooth/hci_ldisc.c | 20 ++
On Mon, Jan 21, 2019 at 6:43 PM Robin Murphy wrote:
>
> On 17/01/2019 09:27, Vivek Gautam wrote:
> > From Robin's comment [1] about touching TCR configurations -
> >
> > "TBH if we're going to touch the TCR attributes at all then we should
> > probably correct that sloppiness first - there's an o
Hi Kai-Heng,
> Realtek bluetooth may not work after reboot:
> [ 12.446130] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e,
> hci rev 826c, hci ver 0008
>
> This is a regression introduced by commit 26503ad25de8 ("Bluetooth:
> btrtl: split the device initialization into smaller par
On Mon, 21 Jan 2019 15:33:42 +,
Julien Thierry wrote:
>
> Per definition of the daifflags, Serrors can occur during any interrupt
> context, that includes NMI contexts. Trying to nmi_enter in an nmi context
> will crash.
>
> Skip nmi_enter/nmi_exit when serror occurred during an NMI.
>
> Su
On Tue, Jan 15, 2019 at 10:05:29AM +, Yogesh Narayan Gaur wrote:
> diff --git a/drivers/spi/spi-nxp-fspi.c b/drivers/spi/spi-nxp-fspi.c
> index e23ad9ef028e..adc3c0e14f38 100644
> --- a/drivers/spi/spi-nxp-fspi.c
> +++ b/drivers/spi/spi-nxp-fspi.c
> @@ -952,8 +952,8 @@ static int nxp_fspi_prob
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses basi
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses basi
Another set of old patches, rebased and this time the commits
also updated since we merged the docs in past and also
refcount_dec_and_test() gets new acquire ordering on success
very soon, which is also reflected in commit messages.
Elena Reshetova (3):
perf: convert perf_event_context.refcount
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses basi
On Mon, Jan 28, 2019 at 12:26:31PM +, Mark Brown wrote:
> On Tue, Jan 15, 2019 at 10:05:29AM +, Yogesh Narayan Gaur wrote:
> > diff --git a/drivers/spi/spi-nxp-fspi.c b/drivers/spi/spi-nxp-fspi.c
> > index e23ad9ef028e..adc3c0e14f38 100644
> > --- a/drivers/spi/spi-nxp-fspi.c
> > +++ b/dri
On Mon, Jan 28, 2019 at 12:46:48PM +0530, Jagan Teki wrote:
> On Fri, Jan 25, 2019 at 2:10 PM Maxime Ripard
> wrote:
> >
> > On Thu, Jan 24, 2019 at 11:22:54PM +0530, Jagan Teki wrote:
> > > Amarula A64 Relic has STLM75 sensor for digital temperature
> > > and thermal watchdog.
> > >
> > > Add su
On Mon, 21 Jan 2019 15:33:43 +,
Julien Thierry wrote:
>
> Handling of an NMI should not set any TIF flags. For NMIs received from
> EL0 the current exit path is safe to use.
>
> However, an NMI received at EL1 could have interrupted some task context
> that has set the TIF_NEED_RESCHED flag.
The patch
regulator: axp20x: fix ALDO2, DLDO2 and ELDO3 definitions for AXP803
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime i
The patch
regulator: rk808: Constify regulator_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sen
The patch
regulator: lp8788-ldo: Constify lp8788_dldo_desc and lp8788_aldo_desc
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
The patch
regulator: lp873x: Constify lp873x_buck01_ops and lp873x_ldo01_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
regulator: rk808: Update module description to include RK805
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the ne
The patch
regulator: lp87565: Constify lp87565_buck_ramp_delay and lp87565_buck_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually somet
The patch
regulator: lp3972: Constify lp3972_ldo_ops and lp3972_dcdc_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: lp8755: Constify lp8755_regulators
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) an
The patch
regulator: lp3971: Constify lp3971_ldo_ops and lp3971_dcdc_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: lp872x: Constify regulator_ops and regulator_desc
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the ne
The patch
MAINTAINERS: add maintainers for the NXP FlexSPI driver
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: lp8788-buck: Constify lp8788_buck_desc
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours
The patch
spi: spi-mem: Add driver for NXP FlexSPI controller
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
regulator: mcp16502: Include linux/gpio/consumer.h to fix build error
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
The patch
regulator: da9062: Check return value of devm_regmap_field_alloc calls
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
The patch
regulator: da9063: Check return value of devm_regmap_field_alloc calls
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
On Sun, Jan 20, 2019 at 4:14 PM Vladimir Zapolskiy wrote:
> The main goal of the change is to remove .pin_config_dbg_parse_modify
> callback before a driver with its support appears. So far the in-kernel
> interface did not attract any users since its introduction 5 years ago.
>
> Originally .pin
On Mon, 21 Jan 2019 15:33:44 +,
Julien Thierry wrote:
>
> When an NMI is raised while interrupts where disabled, the IRQ tracing
> already is in the correct state (i.e. hardirqs_off) and should be left
> as such when returning to the interrupted context.
>
> Check whether PMR was masking int
On Fri, Jan 25, 2019 at 08:24:35PM -0500, Lyude Paul wrote:
> Turns out we are sending a lot more hotplug events then we need, and
> this is causing some pretty serious issues. Currently, we call
> intel_dp_mst_resume() in i915_drm_resume() well before we have any sort
> of hotplugging setup.
We c
My fault, I will fix these in v2.
On 2019年01月28日 17:30, Greg KH wrote:
On Mon, Jan 28, 2019 at 05:19:35PM +0800, Zhou Yanjie wrote:
Add support for probing the 8250_ingenic driver on the
X1000 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
---
drivers/tty/serial/8250/8250_ingenic.c | 10 +
On Mon, 21 Jan 2019 15:33:45 +,
Julien Thierry wrote:
>
> Add a build option and a command line parameter to build and enable the
> support of pseudo-NMIs.
>
> Signed-off-by: Julien Thierry
> Suggested-by: Daniel Thompson
> Cc: Catalin Marinas
> Cc: Will Deacon
> ---
> Documentation/adm
Hi Matti!
Thanks for your patch.
We are going to have a problem with the power subsystem.
These charging drivers are growing wild. This is starting to get out
of hand, we need some more framework for properly handling charging
state machines the kernel. Not specifically your problem, but
when wo
Hi Linus,
On 01/28/2019 02:36 PM, Linus Walleij wrote:
> On Sun, Jan 20, 2019 at 4:14 PM Vladimir Zapolskiy wrote:
>
>> The main goal of the change is to remove .pin_config_dbg_parse_modify
>> callback before a driver with its support appears. So far the in-kernel
>> interface did not attract an
On Sun, Jan 27, 2019 at 9:51 AM Mike Rapoport wrote:
>
> On Wed, Jan 23, 2019 at 02:00:52AM +0200, Oded Gabbay wrote:
> > This patch adds support for doing various on-the-fly reset of Goya.
> >
> > The driver supports two types of resets:
> > 1. soft-reset
> > 2. hard-reset
> >
> > Soft-reset is d
On Fri 25-01-19 10:28:08, Tejun Heo wrote:
> Hello, Michal.
>
> On Fri, Jan 25, 2019 at 06:37:13PM +0100, Michal Hocko wrote:
> > > What if a user wants to monitor any ooms in the subtree tho, which is
> > > a valid use case?
> >
> > How is that information useful without know which memcg the oom
On Mon, Jan 28, 2019 at 11:13:04AM +0100, Igor Mammedov wrote:
> On Fri, 25 Jan 2019 11:02:03 -0600
> Josh Poimboeuf wrote:
>
> > On Fri, Jan 25, 2019 at 10:36:57AM -0600, Josh Poimboeuf wrote:
> > > How about this patch? It's just a revert of 73d5e2b47264 and
> > > bc2d8d262cba, plus the 1-line
On Sun, Jan 27, 2019 at 06:33:52PM -0200, Renato Lui Geh wrote:
> + st->reg = devm_regulator_get(&spi->dev, "avdd");
> + if (IS_ERR(st->reg))
> + return PTR_ERR(st->reg);
> +
> + ret = regulator_enable(st->reg);
> + if (ret) {
> + dev_err(&spi->dev, "Failed t
Hi Matti!
Thanks for your patch!
On Fri, Jan 25, 2019 at 12:05 PM Matti Vaittinen
wrote:
> ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
> controlled by GPIO framework.
>
> IRQs are handled by regmap-irq and GPIO driver is not
> aware of the irq usage.
>
> Signed-off-by: Matti Vaittinen
Hi,
Le lun. 28 janv. 2019 à 9:02, Ulf Hansson a
écrit :
On Fri, 25 Jan 2019 at 21:09, Paul Cercueil
wrote:
Drop the custom code to get the 'cd' and 'wp' GPIOs. The driver now
calls mmc_of_parse() which will init these from devicetree or
device properties.
Also drop the custom code to g
On 28/01/2019 10:18, Joseph Lo wrote:
> Add support for the Tegra210 timer that runs at oscillator clock
> (TMR10-TMR13). We need these timers to work as clock event device and to
> replace the ARMv8 architected timer due to it can't survive across the
> power cycle of the CPU core or CPUPORESET si
Add documentation for the ADC controller on JZ47xx SoCs,
used by the ingenic-adc driver.
Signed-off-by: Artur Rojek
---
.../bindings/iio/adc/ingenic,adc.txt | 48 +++
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/ingenic,a
Add device tree bindings for the ADC controller on JZ47xx SoCs,
used by the ingenic-adc driver.
Signed-off-by: Artur Rojek
---
include/dt-bindings/iio/adc/ingenic,adc.h | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 include/dt-bindings/iio/adc/ingenic,adc.h
diff --git a/i
Add an IIO driver for the ADC hardware present on Ingenic JZ47xx SoCs.
Signed-off-by: Artur Rojek
---
drivers/iio/adc/Kconfig | 9 +
drivers/iio/adc/Makefile | 1 +
drivers/iio/adc/ingenic-adc.c | 357 ++
3 files changed, 367 insertions(+)
create m
On Mon 28-01-19 13:16:09, David Hildenbrand wrote:
[...]
> My theory:
>
> In __unmap_and_move(), we lock the old and newpage and perform the
> migration. In case of vitio-balloon, the new page will become
> movable, the old page will no longer be movable.
>
> However, after unlocking newpage, I t
+Sakari
On 1/24/19 3:53 AM, Ken Sloat wrote:
> There are a number of v4l2 subdevices in the kernel that support a
> Bt.656 bus also known as "embedded sync." Previously in older versions
> of the kernel (and in the current 4.14 LTS kernel), the standard way
> to enable this in device tree on a par
On 28.01.19 14:07, Michal Hocko wrote:
> On Mon 28-01-19 13:16:09, David Hildenbrand wrote:
> [...]
>> My theory:
>>
>> In __unmap_and_move(), we lock the old and newpage and perform the
>> migration. In case of vitio-balloon, the new page will become
>> movable, the old page will no longer be mova
On Mon, 28 Jan 2019, Peter Zijlstra wrote:
> On Sun, Jan 27, 2019 at 12:04:44PM +0100, Thomas Gleixner wrote:
> > On Mon, 21 Jan 2019, tip-bot for Kangjie Lu wrote:
> > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > > index a674c7db2f29..d4d3514c4fe9 100644
> > > --- a/kernel/sched/co
On Mon, 28 Jan 2019, Borislav Petkov wrote:
> From: Borislav Petkov
>
> ... so that they can get CCed on platform patches.
>
> Signed-off-by: Borislav Petkov
> Cc: Darren Hart
> Cc: Andy Shevchenko
> Cc: x...@kernel.org
Acked-by: Thomas Gleixner
On Thu, Jan 24, 2019 at 06:47:23PM +0100, Thomas Bogendoerfer wrote:
> #ifndef __ASSEMBLY__
> +/* Address translation entry for mapped pci32 accesses */
> +union bridge_ate {
> + u64 ent;
> + struct ate_s {
> + u64 rmf:16;
> + u64 addr:36;
> +
On 1/16/19 4:11 PM, Arnd Bergmann wrote:
> On Wed, Jan 16, 2019 at 3:10 PM Fabrice Gasnier
> wrote:
>>
>> On 1/16/19 1:14 PM, Arnd Bergmann wrote:
>>> (sorry for the late reply, I just realized that I had never sent out the
>>> mail after Lee asked me for a review last year and I had drafted
>>>
On Mon 28-01-19 14:14:28, David Hildenbrand wrote:
> On 28.01.19 14:07, Michal Hocko wrote:
> > On Mon 28-01-19 13:16:09, David Hildenbrand wrote:
> > [...]
> >> My theory:
> >>
> >> In __unmap_and_move(), we lock the old and newpage and perform the
> >> migration. In case of vitio-balloon, the new
On 28.01.19 14:21, Michal Hocko wrote:
> On Mon 28-01-19 14:14:28, David Hildenbrand wrote:
>> On 28.01.19 14:07, Michal Hocko wrote:
>>> On Mon 28-01-19 13:16:09, David Hildenbrand wrote:
>>> [...]
My theory:
In __unmap_and_move(), we lock the old and newpage and perform the
mi
Fix coccinelle warning:
./drivers/net/phy/mdio_bus.c:51:5-12: ERROR: PTR_ERR applied after
initialization to constant on line 44
./drivers/net/phy/mdio_bus.c:52:5-12: ERROR: PTR_ERR applied after
initialization to constant on line 44
fix this by using IS_ERR before PTR_ERR
Fixes: bafbdd527d56
On Mon, 28 Jan 2019 05:20:03 -0800
Christoph Hellwig wrote:
> On Thu, Jan 24, 2019 at 06:47:23PM +0100, Thomas Bogendoerfer wrote:
> > #ifndef __ASSEMBLY__
> > +/* Address translation entry for mapped pci32 accesses */
> > +union bridge_ate {
> > + u64 ent;
> > + struct ate_s {
> > +
> struct slice_data {
> unsigned long irq_enable_mask[2];
> - int level_to_irq[LEVELS_PER_SLICE];
> };
Any reaason to keep struct slice_data around at all?
> + HUB_S(hd->irq_mask_addr[0], si->irq_enable_mask[0]);
> + HUB_S(hd->irq_mask_addr[1], si->irq_enable_mask[1]);
I know
On 1/25/19 1:24 PM, Bernd Edlinger wrote:
> On 1/25/19 12:39 PM, Miguel Ojeda wrote:
>> On Fri, Jan 25, 2019 at 11:58 AM Arnd Bergmann wrote:
>>>
>>> On Fri, Jan 25, 2019 at 11:43 AM Laura Abbott wrote:
Commit bee20031772a ("disable -Wattribute-alias warning for
SYSCALL_DEFINEx()")
On Thu 24-01-19 20:19:57, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Jan Kara
>
> commit 967d1dc144b50ad005e5eecdfadfbcfb3996 upstream.
>
> __loop_release() has a single call site. Fold it there.
Dne 25.1.2019 v 19:25 Mark Brown napsal(a):
> On Fri, Jan 25, 2019 at 02:19:22PM +0100, Takashi Iwai wrote:
>> Leo Yan wrote:
>
>>> If we directly use the device node /dev/snd/ as file descriptor, even
>>> though we specify flag O_EXCL when open it, but it still is not an
>>> anon inode file descr
On Thu, Jan 24, 2019 at 06:47:27PM +0100, Thomas Bogendoerfer wrote:
> Converted bridge code to a platform driver using the PCI generic driver
> framework and use adding platform devices during xtalk scan. This allows
> easier sharing bridge drvier for other SGI platforms like IP30 (Octane) and
Ty
On Thu, Jan 17, 2019 at 04:48:28PM +0800, YueHaibing wrote:
> There are no in-tree callers.
I'd rather see the code fixed, the patch that used the function was
reverted because it was not safe to call sysfs from various contexts. I
have some wip.
Shouldnt this just use chained irqchip drivers instead?
On Sat, Jan 26, 2019 at 10:48:53AM +0800, Chao Yu wrote:
> On 2019/1/26 0:10, Gao Xiang wrote:
> > Let's add .get_acl() to read the file's acl from its xattrs
> > to make POSIX ACL usable.
> >
> > Here is the on-disk detail,
> > fullname: system.posix_acl_access
> > struct erofs_xattr_entry:
> >
On Mon, Jan 28, 2019 at 02:24:40PM +0100, Thomas Bogendoerfer wrote:
> I totally agreed. I only moved the original defintion around while cleaning
> up the header file. Right now there is no code using it. Should I remove it
> and access macros as soon there is a need for it ?
Sounds good.
On Mon 28-01-19 14:22:52, David Hildenbrand wrote:
> On 28.01.19 14:21, Michal Hocko wrote:
> > On Mon 28-01-19 14:14:28, David Hildenbrand wrote:
> >> On 28.01.19 14:07, Michal Hocko wrote:
> >>> On Mon 28-01-19 13:16:09, David Hildenbrand wrote:
> >>> [...]
> My theory:
>
> In __un
On Tue, Jan 15, 2019 at 06:38:38PM +0100, Jiri Olsa wrote:
> On Tue, Jan 15, 2019 at 04:13:16PM +, Nick Clifton wrote:
> > Hi Jiri,
> >
> > > When perf is built with annobin plugin (RHEL8 build) extra symbols
> > > are added to its binary:
> >
> > A bit of background for those wondering why
On Mon, 28 Jan 2019 06:52:52 -0600
Josh Poimboeuf wrote:
> On Mon, Jan 28, 2019 at 11:13:04AM +0100, Igor Mammedov wrote:
> > On Fri, 25 Jan 2019 11:02:03 -0600
> > Josh Poimboeuf wrote:
> >
> > > On Fri, Jan 25, 2019 at 10:36:57AM -0600, Josh Poimboeuf wrote:
> > > > How about this patch?
On 01/28, Dan Carpenter wrote:
On Sun, Jan 27, 2019 at 06:33:52PM -0200, Renato Lui Geh wrote:
+ st->reg = devm_regulator_get(&spi->dev, "avdd");
+ if (IS_ERR(st->reg))
+ return PTR_ERR(st->reg);
+
+ ret = regulator_enable(st->reg);
+ if (ret) {
+
On Tue, Jan 22, 2019 at 10:18 PM Vladimir Zapolskiy wrote:
> The main goal of the change is to remove .pin_config_dbg_parse_modify
> callback before a driver with its support appears. So far the in-kernel
> interface did not attract any users since its introduction 5 years ago.
Good riddance. Bo
On Thu, Jan 24, 2019 at 08:55:05PM +, Jason Gunthorpe wrote:
> The final ternary expression is given void * and type * as arguments, so
> the resulting type of the macro ends up being void *.
>
> container_of returns a type which maches the argument, this provides type
> safety and allows the
201 - 300 of 2154 matches
Mail list logo
