On Thu, Dec 13, 2018 at 04:03:58PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-12-12 22:05:19 [+0800], Boqun Feng wrote:
> > So Jiangshan and TJ, what's your opion on this one? If we call a
> > queue_work_on() at a place where that target cpu may be offlined, I
> > think we have the guarantee
On Thu, Dec 13, 2018 at 06:10:19PM +0800, Jason Wang wrote:
> Hi:
>
> This series tries to access virtqueue metadata through kernel virtual
> address instead of copy_user() friends since they had too much
> overheads like checks, spec barriers or even hardware feature
> toggling.
Userspace access
Hello,
syzbot found the following crash on:
HEAD commit:f5d582777bcb Merge branch 'for-linus' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e556fb40
kernel config: https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
da
On 12/13/2018 06:11 AM, Paul Burton wrote:
> Hi Marek,
Hi,
> On Thu, Dec 13, 2018 at 05:18:19AM +0100, Marek Vasut wrote:
> I wonder whether the issue may be the JZ4780 UART not automatically
> resetting the FIFOs when FCR[0] changes. This is a guess, but the manual
> doesn't explicit
On Mon, Dec 10, 2018 at 05:12:19PM +0800, Wesley Sheng wrote:
> Hi, Everyone,
>
> This patch series adds support for the Switchtec MRPC DMA mode.
>
> Switchtec switches supports 2 MRPC interaction modes: MRPC normal mode and
> MRPC DMA mode, a new feature in the latest firmware versions. MRPC nor
On Thu, Dec 13, 2018 at 12:59:00PM +, claudiu.bez...@microchip.com wrote:
> Hi Mark,
>
> I saw that previous version of this series was applied to your tree just
> after I've send this new one. The only difference b/w them is in the
> documentation patch where I moved the new header. No functi
On Thu, Dec 13, 2018 at 09:51:18AM -0500, Tom Talpey wrote:
> On 12/13/2018 9:18 AM, Jerome Glisse wrote:
> > On Thu, Dec 13, 2018 at 08:40:49AM -0500, Tom Talpey wrote:
> > > On 12/13/2018 7:43 AM, Jerome Glisse wrote:
> > > > On Wed, Dec 12, 2018 at 08:20:43PM -0700, Jason Gunthorpe wrote:
> > >
On Mon, Dec 10, 2018 at 05:12:24PM +0800, Wesley Sheng wrote:
> MRPC normal mode requires the host to read the MRPC command status and
> output data from BAR. This results in high latency responses from the
> Memory Read TLP and potential Completion Timeout (CTO).
>
> MRPC DMA mode implementation
On Thu, Dec 13, 2018 at 01:29:10PM +0100, Anders Roxell wrote:
> With this new config option, we can boot a allmodconfig kernel in qemu.
> Config options SERIAL_AMBA_PL011, SERIAL_AMBA_PL011_CONSOLE, UNIX needs
> to be enabled in order to get a console. Options like CPU_BIG_ENDIAN,
> CMDLINE_FORCE
On 13/12/2018 04:02, Matthew Wilcox wrote:
> On Wed, Dec 12, 2018 at 09:17:07AM +0100, Mickaël Salaün wrote:
>> The goal of this patch series is to control script interpretation. A
>> new O_MAYEXEC flag used by sys_open() is added to enable userland script
>> interpreter to delegate to the kerne
On Wed, Dec 12, 2018 at 03:58:22PM -0700, Logan Gunthorpe wrote:
> On 2018-12-12 3:52 p.m., Bjorn Helgaas wrote:
> > On Mon, Dec 10, 2018 at 05:12:24PM +0800, Wesley Sheng wrote:
> >> MRPC normal mode requires the host to read the MRPC command status and
> >> output data from BAR. This results in h
On 2018/12/13 下午10:23, Richard Weinberger wrote:
Hello zhangjun,
thanks a lot for bringing this up!
Am Mittwoch, 12. Dezember 2018, 15:13:57 CET schrieb zhangjun:
Because the PagePrivate() in UBIFS is different meanings,
alloc_cma() will fail when one dirty page cache located in
the type of
On Thu, 13 Dec 2018 at 14:12, Peter Zijlstra wrote:
>
> On Thu, Dec 13, 2018 at 12:04:20PM +0100, Vincent Guittot wrote:
> > On Thu, 13 Dec 2018 at 11:44, Peter Zijlstra wrote:
> > >
> > > On Mon, Sep 10, 2018 at 04:43:09PM +0200, Vincent Guittot wrote:
> > > > When CPUs have different capacity b
On 06. 12. 18 13:47, Naga Sureshkumar Relli wrote:
> The following patches add arm pl353 static memory controller driver and NAND
> driver for Xilinx Zynq SoC. The arm pl353 smc supports two interfaces
> i.e nand and NOR/SRAM memory interfaces. The current implementation supports
> only a single SM
On Thu, Dec 13, 2018 at 01:37:16PM +0100, Zaslonko Mikhail wrote:
>On 13.12.2018 04:46, Wei Yang wrote:
>> On Wed, Dec 12, 2018 at 06:27:12PM +0100, Mikhail Zaslonko wrote:
>>> If memory end is not aligned with the sparse memory section boundary, the
>>> mapping of such a section is only partly ini
Hello,
syzbot found the following crash on:
HEAD commit:ca40dc225d19 Add linux-next specific files for 20181213
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=126d9fd540
kernel config: https://syzkaller.appspot.com/x/.config?x=778d1d35b0e8272b
On Thu, Dec 13, 2018 at 08:37:08AM +0100, Uwe Kleine-König wrote:
> On Wed, Dec 12, 2018 at 01:14:10PM -0500, Jeremy Cline wrote:
> > Hi,
> >
> > On Wed, Dec 12, 2018 at 02:12:09PM +0100, Thierry Reding wrote:
> > > From: Thierry Reding
> > >
> > > The spdxcheck script currently falls over when
On 13/12/2018 17:03, Vignesh R wrote:
On 13-Dec-18 8:29 PM, Tero Kristo wrote:
On 09/12/2018 12:22, Vignesh R wrote:
There are 3 instances of McSPI in MCU domain and 4 instances in Main
domain.
Add DT nodes for all McSPI instances present on AM654 SoC.
Signed-off-by: Vignesh R
---
arch/a
On Fri, Nov 16, 2018 at 10:09:15PM +0530, Jagan Teki wrote:
> Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
>
> Add panel driver for it.
>
> Signed-off-by: Jagan Teki
> ---
> MAINTAINERS | 6 +
> drivers/gpu/drm/panel/Kconfig
On 2018-12-12 07:55:46 [-0800], Paul E. McKenney wrote:
> Well, what I was relying on was Thomas Gleixner's assertion that it should
> work and would be fixed if it didn't. ;-)
and there is work_on_cpu_safe() in case work needs to be performed on
CPU X and only on CPU X.
>
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/realtek/rtlwifi/rtl8821ae/trx.c: In function
> 'translate_rx_signal_stuff':
> drivers/net/wireless/realtek/rtlwifi/rtl8821ae/trx.c:309:6: warning:
> variable 'type' set but not used [-Wunused-but-set-va
On 13/12/2018 12:02, Julien Thierry wrote:
>
>
> On 13/12/2018 11:35, Ard Biesheuvel wrote:
>> On Thu, 13 Dec 2018 at 09:54, Julien Thierry wrote:
>>>
>>>
>>>
>>> On 12/12/2018 18:10, Ard Biesheuvel wrote:
On Wed, 12 Dec 2018 at 18:59, Julien Thierry
wrote:
>
>
>
>
On 2018-12-12 22:05:19 [+0800], Boqun Feng wrote:
> So Jiangshan and TJ, what's your opion on this one? If we call a
> queue_work_on() at a place where that target cpu may be offlined, I
> think we have the guarantee that the work will be eventually executed
> even if the cpu is never online again,
On 13-Dec-18 8:29 PM, Tero Kristo wrote:
> On 09/12/2018 12:22, Vignesh R wrote:
>> There are 3 instances of McSPI in MCU domain and 4 instances in Main
>> domain.
>> Add DT nodes for all McSPI instances present on AM654 SoC.
>>
>> Signed-off-by: Vignesh R
>> ---
>> arch/arm64/boot/dts/ti/k3-
Pan Bian wrote:
> entry is released via usb_put_urb just after calling usb_submit_urb.
> However, entry is used if the submission fails, resulting in a use after
> free bug. The patch fixes this.
>
> Signed-off-by: Pan Bian
> ACKed-by: Larry Finger
Patch applied to wireless-drivers-next.git,
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/broadcom/b43/phy_n.c: In function
> 'b43_nphy_op_recalc_txpower':
> drivers/net/wireless/broadcom/b43/phy_n.c:5898:7: warning:
> variable 'tx_pwr_state' set but not used [-Wunused-but-set-variable]
>
>
On Thu, 2018-12-13 at 22:37 +0800, Sunny Luo wrote:
> Hi Jerome,
>
> On 2018/12/13 17:28, Jerome Brunet wrote:
> > On Thu, 2018-12-13 at 09:55 +0100, Neil Armstrong wrote:
> > > > diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> > > > config SPI_MESON_SPICC
> > > > tristate "Amlo
On 09/12/2018 12:22, Vignesh R wrote:
There are 3 instances of McSPI in MCU domain and 4 instances in Main domain.
Add DT nodes for all McSPI instances present on AM654 SoC.
Signed-off-by: Vignesh R
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 52
arch/arm64/boot/d
Arnd Bergmann wrote:
> When CONFIG_NO_AUTO_INLINE is set, we get a false-postive warning
> for the brcmf_fw_request_nvram_done() function, after gcc figures
> out that brcmf_fw_nvram_from_efi() might not set the 'data_len'
> variable, but fails to notice that it always returns NULL:
>
> drivers/
On Wed, Dec 12, 2018 at 09:51:59AM -0500, Stephen Smalley wrote:
> On 12/11/18 4:48 PM, Vivek Goyal wrote:
> > On Thu, Dec 06, 2018 at 03:26:26PM -0500, Stephen Smalley wrote:
> > > On 12/5/18 8:43 AM, Vivek Goyal wrote:
> > > > On Tue, Dec 04, 2018 at 11:49:16AM -0500, Stephen Smalley wrote:
> > >
On 13/12/2018 06:13, Florian Weimer wrote:
> * James Morris:
>
>> On Wed, 12 Dec 2018, Florian Weimer wrote:
>>
>>> * James Morris:
>>>
If you're depending on the script interpreter to flag that the user may
execute code, this seems to be equivalent in security terms to depending
>>>
Brian Norris wrote:
> This function converts some firmware-specific parameters into cfg80211
> 'rate_info' structures. It currently assumes it's dealing only with TX
> bitrate, but the RX bitrate looks to be the same, so refactor this
> function to be reusable.
>
> Signed-off-by: Brian Norris
Le jeu. 13 déc. 2018 à 15:23, Marc Zyngier a écrit :
>
> On 04/12/2018 20:47, Rob Herring wrote:
> > On Tue, Nov 13, 2018 at 03:48:03PM +0100, Benjamin Gaignard wrote:
> >> Add hwlocks as optional property
> >>
> >> Signed-off-by: Benjamin Gaignard
> >
> > Should be linaro.org S-o-b?
>
> What is
On Thu, Dec 06, 2018 at 09:09:13AM +0800, Jianjun Wang wrote:
> MT7629 is an arm platform SoC which has the same PCIe IP with MT7622.
s/arm/ARM/
> The read value of BAR0 is 0x_, it's size will be calculated as 4GB
> in arm64 but bogus alignment values at arm32, the pcie device and devices
Brian Norris wrote:
> Currently, snippets of this file look like:
>
> rx rates (in Mbps): 0=1M 1=2M2=5.5M 3=11M 4=6M 5=9M 6=12M
> 7=18M 8=24M 9=36M 10=48M 11=54M12-27=MCS0-15(BW20) 28-43=MCS0-15(BW40)
> 44-53=MCS0-9(VHT:BW20)54-63=MCS0-9(VHT:BW40)64-73=MCS0-9(VHT:BW80)
> ...
> noise_
Pan Bian wrote:
> There are two defects: (1) passing a NULL bss to
> mwifiex_save_hidden_ssid_channels will result in NULL dereference,
> (2) using bss after dropping the reference to it via cfg80211_put_bss.
> To fix them, the patch moves the buggy code to the branch that bss is
> not NULL and p
We've failed to copy and process vhost_iotlb_msg so let userspace at
least know about it. For instance before these patch the code below runs
without any error:
int main()
{
struct vhost_msg msg;
struct iovec iov;
int fd;
fd = open("/dev/vhost-net", O_RDWR);
if (fd == -1) {
perror("
On Wed, 12 Dec 2018 at 11:57, Viresh Kumar wrote:
>
> dev_pm_genpd_set_performance_state() needs to handle performance state
> propagation going forward. Currently this routine only gets the required
> performance state of the device's genpd as an argument, but it doesn't
> know how to translate t
Arnd Bergmann wrote:
> When CONFIG_NO_AUTO_INLINE is set, we get a false-postive warning
> for the brcmf_fw_request_nvram_done() function, after gcc figures
> out that brcmf_fw_nvram_from_efi() might not set the 'data_len'
> variable, but fails to notice that it always returns NULL:
>
> drivers/
Hi Again,
Le 13/12/2018 à 13:16, Christophe Leroy a écrit :
Hi,
On 12/03/2018 09:55 PM, Jonathan Neuschäfer wrote:
Hi,
On Thu, Nov 29, 2018 at 07:00:16PM +, Christophe Leroy wrote:
This patch reworks mmu_mapin_ram() to be more generic and map as much
blocks as possible. It now supports b
On 18-12-13 15:35:27, Lucas Stach wrote:
> Am Donnerstag, den 13.12.2018, 13:17 + schrieb Abel Vesa:
> > To keep aligned with arm64, remove the unnecessary SOC_IMX8MQ and use
> > ARCH_MXC instead.
> >
> > Signed-off-by: Abel Vesa
> > ---
> > arch/arm64/Kconfig.platforms | 8 ---
On Thu, Dec 13, 2018 at 03:30:00PM +0100, Miquel Raynal wrote:
> Hi Lorenzo,
>
> > > If that's really the case, then I can see how one device and it's
> > > children are suspended and the irq for it is disabled but the providing
> > > devices (clk, regulator, bus controller, etc.) are still fully
On 12/13/2018 9:18 AM, Jerome Glisse wrote:
On Thu, Dec 13, 2018 at 08:40:49AM -0500, Tom Talpey wrote:
On 12/13/2018 7:43 AM, Jerome Glisse wrote:
On Wed, Dec 12, 2018 at 08:20:43PM -0700, Jason Gunthorpe wrote:
On Wed, Dec 12, 2018 at 07:01:09PM -0500, Jerome Glisse wrote:
On Wed, Dec 12, 2
On 12/12/2018 18:09, Jann Horn wrote:
> On Wed, Dec 12, 2018 at 9:18 AM Mickaël Salaün wrote:
>> Enable to either propagate the mount options from the underlying VFS
>> mount to prevent execution, or to propagate the file execute permission.
>> This may allow a script interpreter to check execut
On Thu, Dec 13, 2018 at 01:28:02PM +, Lee Jones wrote:
> On Thu, 13 Dec 2018, Mark Brown wrote:
> > What's going on with this patch? Will you be applying it or is this an
> > ack for it to be applied with the rest of the series?
> I don't have anything else queued for include/linux/mfd/axp20
This commit adds documentation for the device-tree bindings of the
jz4740-musb driver, which provides support for the USB gadget mode
of the JZ4740 and similar SoCs from Ingenic.
Signed-off-by: Paul Cercueil
---
.../bindings/usb/ingenic,jz4740-musb.txt | 24 ++
1 fi
Depending on MACH_INGENIC prevent us from creating a generic kernel that
works on more than one MIPS board. Instead, we just depend on MIPS being
set.
On other architectures, this driver can still be built, thanks to
COMPILE_TEST. This is used by automated tools to find bugs, for
instance.
Signed
Add support for probing the driver from devicetree.
Signed-off-by: Paul Cercueil
---
drivers/usb/musb/jz4740.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/usb/musb/jz4740.c b/drivers/usb/musb/jz4740.c
index 04d8b2bc205a..9a2cebcac260 100644
--- a/drivers/usb/musb/jz4740.c
The USB IP in the JZ4740 SoC does not support host mode, only gadget
mode.
Signed-off-by: Paul Cercueil
---
drivers/usb/musb/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index 6f5b0ed6a507..a884179bc3c0 100644
--- a/drivers/usb/mu
Add ethanol and H2 gas modifiers:
* IIO_MOD_ETHANOL
* IIO_MOD_H2
Signed-off-by: Andreas Brauchli
---
Documentation/ABI/testing/sysfs-bus-iio | 4
include/uapi/linux/iio/types.h | 2 ++
tools/iio/iio_event_monitor.c | 4
3 files changed, 10 insertions(+)
diff --git a
Support Sensirion SGP30 and SGPC3 multi-pixel I2C gas sensors
Supported Features:
* Indoor Air Quality (IAQ) concentrations for
- tVOC (in_concentration_voc_input)
- CO2eq (in_concentration_co2_input) - SGP30 only
IAQ concentrations are periodically read out by a background thread
to all
Minimal SGP30/SGPC3 driver
Changes to v2:
* Strip all calibration params to give time to determine the preferred way
of adding those to IIO. The sensor remains fully functional, just without
humidity compensation, baseline support for resuming measurements, ...
* Split DT bindings into own com
Add device tree support for Sensirion SGP30/SGPC3 gas sensors.
Signed-off-by: Andreas Brauchli
---
.../bindings/iio/chemical/sensirion,sgp30.txt | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/chemical/sensirion,sgp30.txt
dif
Enric,
On Tue, Dec 11, 2018 at 11:01 AM Enric Balletbo i Serra
wrote:
>
> There are multiple ChromeOS EC sub-drivers spread in different
> subsystems, as all of them are related to the Chrome stuff add
> Benson and myself as a maintainers for all these sub-drivers.
>
> Signed-off-by: Enric Ballet
On Thu, Dec 13, 2018 at 08:02:11AM +, Richard Zhu wrote:
> MSI_EN of iMX PCIe RC would be asserted when
> PCIEPORTBUS driver is selected.
> Thus, the MSI works fine on iMX PCIe before.
> Assert it unconditionally when MSI is supported.
> Otherwise, the MSI wouldn't be triggered although
> the E
On Thu, Dec 13, 2018 at 09:30:47PM +0900, Xin Long wrote:
> On Sat, Sep 8, 2018 at 1:57 AM Kent Overstreet
> wrote:
> >
> > All existing users have been converted to generic radix trees
> NAK, SCTP is still using flex_arrays,
> # grep flex_array net/sctp/*
>
> This patch will break the build.
sc
On Thu, Dec 13, 2018 at 4:09 AM Enric Balletbo i Serra
wrote:
>
> This patch allows reading and writing the input voltage and current
> limit through the POWER_SUPPLY_PROP_INPUT_VOLTAGE_LIMIT and
> POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT sysfs properties. This allows
> userspace to see current value
On Tue, Dec 11, 2018 at 9:40 AM Linus Torvalds
wrote:
>
> On Mon, Dec 10, 2018 at 5:23 PM Andy Lutomirski wrote:
> >
> > I'm seriously considering sending a patch to remove x32 support from
> > upstream Linux. Here are some problems with it:
>
> I talked to Arnd (I think - we were talking about
Hi Jerome,
On 2018/12/13 17:28, Jerome Brunet wrote:
On Thu, 2018-12-13 at 09:55 +0100, Neil Armstrong wrote:
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
config SPI_MESON_SPICC
tristate "Amlogic Meson SPICC controller"
- depends on ARCH_MESON || COMPILE_TEST
+
Hello,
On Thu, 13 Dec 2018 15:33:06 +0100, Miquel Raynal wrote:
> I will re-send a series without this patch. I think it does not hurt to
> keep the previous patch adding the pinmux setting in the
> Armada-37xx.dtsi file even without using it, so I will drop only this
> patch.
I tend to disagree
Add the SPDIF capture codec to the axg s400 board
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
index af2f
Enable spdif input device on the S400 and add it to the card
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-
Add the SPDIF input device of the axg audio subsystem
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
index fffd5
This patchset adds spdif input support to the axg SoC family and the
s400 reference design.
Kevin, ASoC support for this spdif input (including the binding doc) just
got merged in the ASoC tree [0]. Until the related patches hit mainline,
you may get a warning about using undocumented bindings.
[
On 2018-12-12 18:11:29 [+0100], Borislav Petkov wrote:
> > diff --git a/arch/x86/math-emu/fpu_entry.c b/arch/x86/math-emu/fpu_entry.c
> > index 9e2ba7e667f61..a873da6b46d6b 100644
> > --- a/arch/x86/math-emu/fpu_entry.c
> > +++ b/arch/x86/math-emu/fpu_entry.c
> > @@ -113,9 +113,6 @@ void math_emula
Hi Rafael,
I see that you have pulled 3 patches.
Please take also this patch, which is actually enabling the feature.
Regards,
Lukasz
On 12/5/18 12:05 PM, Lukasz Luba wrote:
> Devfreq framework supports suspend of its devices.
> Call the the devfreq interface and allow devfreq devices preserve/r
Am Donnerstag, den 13.12.2018, 13:17 + schrieb Abel Vesa:
> To keep aligned with arm64, remove the unnecessary SOC_IMX8MQ and use
> ARCH_MXC instead.
>
> Signed-off-by: Abel Vesa
> ---
> arch/arm64/Kconfig.platforms | 8
> arch/arm64/boot/dts/freescale/Makefile | 2 +-
> d
Hi,
Le jeu. 13 déc. 2018 à 10:30, Uwe Kleine-König
a écrit :
Hello,
On Wed, Dec 12, 2018 at 11:09:06PM +0100, Paul Cercueil wrote:
[...]
static int jz4740_pwm_enable(struct pwm_chip *chip, struct
pwm_device *pwm)
{
- uint32_t ctrl = jz4740_timer_get_ctrl(pwm->pwm);
+ struc
Hello,
Miquel Raynal wrote on Wed, 12 Dec 2018
11:21:40 +0100:
> Add a reset-gpios property to the PCIe node.
>
> Signed-off-by: Miquel Raynal
> ---
> arch/arm64/boot/dts/marvell/armada-3720-espressobin.dts | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/marve
On Thu, Dec 13, 2018 at 10:53:36AM +0800, Jason Wang wrote:
> Hi:
>
> This series tries to fix various issues of vhost:
>
> - Patch 1 adds a missing write barrier between used idx updating and
> logging.
> - Patch 2-3 brings back the protection of device IOTLB through vq
> mutex, this fixes p
On Wed, Dec 12, 2018 at 05:40:23PM +, Xue Chaojing wrote:
> There is no need to schedule a different tasklet for refill,
> This patch remove it.
>
> Suggested-by: Neil Horman
> Signed-off-by: Xue Chaojing
> ---
> drivers/net/ethernet/huawei/hinic/hinic_rx.c | 23 +---
> driv
On Thu, Dec 13, 2018 at 10:39:41AM +0800, Jason Wang wrote:
>
> On 2018/12/12 下午10:32, Michael S. Tsirkin wrote:
> > On Wed, Dec 12, 2018 at 06:08:19PM +0800, Jason Wang wrote:
> > > Vhost dirty page logging API is designed to sync through GPA. But we
> > > try to log GIOVA when device IOTLB is en
Hi Lorenzo,
> > If that's really the case, then I can see how one device and it's
> > children are suspended and the irq for it is disabled but the providing
> > devices (clk, regulator, bus controller, etc.) are still fully active
> > and not suspended but in fact completely usable and able to se
On Thu, Dec 13, 2018 at 10:59:31AM +0100, Petr Mladek wrote:
On Wed 2018-12-12 18:39:42, Daniel Wang wrote:
> Additionally, for dbdda842fe96f to work as expected we really
need fd5f7cde1b85d4c. Otherwise printk() can schedule under
console_sem and console_owner, which will deactivate the "load
b
--
Hallo
Groeten van Funding Trusts Finance, we zijn gevestigde en
goedgekeurde Britse leningmaatschappijen, door de jaren heen hebben we
een goed begrip ontwikkeld van uw behoeften en individuele behoeften. we
hebben ons gecommitteerd om onze klanten eerlijk te behandelen en een
servi
On Wed, Dec 12, 2018 at 10:16:58AM -0800, Darrick J. Wong wrote:
> On Tue, Dec 11, 2018 at 05:58:18AM -0800, Christoph Hellwig wrote:
> > On Sat, Dec 08, 2018 at 11:24:48AM -0800, Linus Torvalds wrote:
> > > Honestly, I really wish you simply wouldn't send me "xfs" fixes that
> > > aren't really xf
On Wed, 12 Dec 2018 11:49:23 +
Robin Murphy wrote:
> On 12/12/2018 11:42, Jonathan Cameron wrote:
> > On Tue, 11 Dec 2018 18:48:48 +
> > Robin Murphy wrote:
> >
> >> Wire up the basic support for hot-adding memory. Since memory hotplug
> >> is fairly tightly coupled to sparsemem, we t
On 12/13/18 2:40 AM, Colin King wrote:
From: Colin Ian King
There is a spelling mistake in the --gettimeleft help text, fix it.
Signed-off-by: Colin Ian King
---
tools/testing/selftests/watchdog/watchdog-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testi
Hello zhangjun,
thanks a lot for bringing this up!
Am Mittwoch, 12. Dezember 2018, 15:13:57 CET schrieb zhangjun:
> Because the PagePrivate() in UBIFS is different meanings,
> alloc_cma() will fail when one dirty page cache located in
> the type of MIGRATE_CMA
>
> If not adjust the 'extra_count'
On 04/12/2018 20:47, Rob Herring wrote:
> On Tue, Nov 13, 2018 at 03:48:03PM +0100, Benjamin Gaignard wrote:
>> Add hwlocks as optional property
>>
>> Signed-off-by: Benjamin Gaignard
>
> Should be linaro.org S-o-b?
What is the status on this? I'm not going to queue it if there is a
doubt on the
On 13/12/2018 10:47, Matthew Bobrowski wrote:
> On Wed, Dec 12, 2018 at 03:43:06PM +0100, Jan Kara wrote:
>>> When the O_MAYEXEC flag is passed, sys_open() may be subject to
>>> additional restrictions depending on a security policy implemented by an
>>> LSM through the inode_permission hook.
>>>
Hi Robert,
On 28/11/2018 14:43, Robert Richter wrote:
> This patch introduces a new interface to allow irq domain
> initialization regardless of order dependencies. This is done by
> requesting a domain and registering a callback function that is called
> as soon as a domain becomes available.
>
On Thu, Dec 13, 2018 at 08:40:49AM -0500, Tom Talpey wrote:
> On 12/13/2018 7:43 AM, Jerome Glisse wrote:
> > On Wed, Dec 12, 2018 at 08:20:43PM -0700, Jason Gunthorpe wrote:
> > > On Wed, Dec 12, 2018 at 07:01:09PM -0500, Jerome Glisse wrote:
> > > > On Wed, Dec 12, 2018 at 04:37:03PM -0700, Jason
On 2018-12-11 00:17, medadyo...@gmail.com wrote:
From: Medad
If we do NOT clear NBD_BOUND flag when NBD connection is closed,
then the original NBD device could not be used again.
Signed-off-by: Medad
Tested on Witherspoon (OpenPOWER P9 with AST2500) and verified with
this patch tha
on symbols not being static)
>
> Patch is against 4.20-rc6 (localversion-next is next-20181213)
>
> samples/livepatch/livepatch-shadow-mod.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/samples/livepatch/livepatch-shadow-mod.c
> b/samples/livepatch/live
On 13 December 2018 12:10, Enric Balletbo i Serra wrote:
> This is part of the Pixel C's thermal management strategy to effectively
> limit the
> input power to 5V 3A when the screen is on. When the screen is on, the
> display,
> the CPU, and the GPU all contribute more heat to the system than w
+++ Nadav Amit [04/12/18 17:34 -0800]:
When module memory is about to be freed, there is no apparent reason to
make it (and its data) executable, but that's exactly what is done
today. This is not efficient and not secure.
There are various theories why it was done, but none of them seem as
some
.
Patch was compile tested with: x86_64_defconfig + FTRACE=y
FUNCTION_TRACER=y, EXPERT=y, LATENCYTOP=y, SAMPLES=y, SAMPLE_LIVEPATCH=y
(with a number of unrelated sparse warnings on symbols not being static)
Patch is against 4.20-rc6 (localversion-next is next-20181213)
samples/livepatch/livepatch
symbols not being static)
Patch is against 4.20-rc6 (localversion-next is next-20181213)
samples/livepatch/livepatch-shadow-fix1.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/samples/livepatch/livepatch-shadow-fix1.c
b/samples/livepatch/livepatch-shadow-fix1.c
index 49b1355..e8f1bd6
On Tue, Dec 11, 2018 at 02:49:01PM +, Quentin Perret wrote:
> Hi Ingo,
>
> On Tuesday 11 Dec 2018 at 15:15:09 (+0100), Ingo Molnar wrote:
> >
> > * Quentin Perret wrote:
> >
> > > In its current state, Energy Aware Scheduling (EAS) starts automatically
> > > on asymmetric platforms having a
On Thu, Dec 13, 2018 at 12:13:29PM +0900, Tomasz Figa wrote:
> Putting aside the problem of memory without struct page, one thing to
> note here that what is a contiguous DMA range for device X, may not be
> mappable contiguously for device Y and it would still need something
> like a scatter list
Hi,
Le jeu. 13 déc. 2018 à 10:24, Uwe Kleine-König
a écrit :
Hello,
On Wed, Dec 12, 2018 at 11:09:10PM +0100, Paul Cercueil wrote:
The PWM in the JZ4725B works the same as in the JZ4740, except that
it
only has 6 channels available instead of 8.
this driver is probed only from device tr
LATENCYTOP=y, SAMPLES=y, SAMPLE_LIVEPATCH=y
> > (with some unrelated sparse warnings on symbols not being static)
> >
> > Patch is against 4.20-rc6 (localversion-next is next-20181213)
> >
> > samples/livepatch/livepatch-shadow-fix1.c | 3 +++
> > 1 file changed,
Hi,
Le jeu. 13 déc. 2018 à 10:18, Uwe Kleine-König
a écrit :
On Wed, Dec 12, 2018 at 11:09:07PM +0100, Paul Cercueil wrote:
The TCU channels 0 and 1 were previously reserved for system tasks,
and
thus unavailable for PWM.
The driver will now only allow a PWM channel to be requested if
m
On Tuesday 11 Dec 2018 at 07:36:40 (-0800), tip-bot for Quentin Perret wrote:
> Commit-ID: 1f74de8798c93ce14801cc4e772603e51c841c33
> Gitweb:
> https://git.kernel.org/tip/1f74de8798c93ce14801cc4e772603e51c841c33
> Author: Quentin Perret
> AuthorDate: Mon, 3 Dec 2018 09:56:22 +
> Comm
Brian Norris wrote:
> This reverts commit 5188d5453bc9380ccd4ae1086138dd485d13aef2, because it
> introduced lock recursion:
>
> BUG: spinlock recursion on CPU#2, kworker/u13:1/395
>lock: 0xffc0e28a47f0, .magic: dead4ead, .owner: kworker/u13:1/395,
> .owner_cpu: 2
> CPU: 2 PID: 395 C
This patch fixes early DEBUG messages in prom.c:
- Use %px instead of %p to see the addresses
- Use %x instead of %llx when phys_addr_t is not 64 bits.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/prom.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/
On Tue, Aug 07, 2018 at 05:56:27PM +0200, Vincent Guittot wrote:
> +static inline bool
> +asym_active_balance(enum cpu_idle_type idle, unsigned int flags, int dst,
> int src)
> {
> + if (idle != CPU_NOT_IDLE) {
>
> /*
>* ASYM_PACKING needs to force migrate task
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 14 ---
drivers/gpu/drm/virtio/virtgpu_display.c | 1 -
drivers/gpu/drm/virtio/virtgpu_drv.c | 9 +-
drivers/gpu/drm/virtio/virtgpu_fb.c | 191 ---
drivers/gpu/drm/virtio/virtgpu_
On Thu, 2018-12-13 at 10:44 +, James Morse wrote:
> The kernel should already handle this, as we don't trust the bootloader to
> clean
> up either.
>
> In arch/arm64/mm/proc.S::__cpu_setup()
> > /*
> > * __cpu_setup
> > *
> > * Initialise the processor for turning the MMU on. Return in x0
601 - 700 of 1063 matches
Mail list logo
