On Sat, Apr 27, 2019 at 02:17:42AM -0400, Sven Van Asbroeck wrote:
> Hello Nicholas, thank you for your contribution, I really appreciate it !
> See inline comments below.
>
> On Sat, Apr 27, 2019 at 12:32 AM Nicholas Mc Guire wrote:
> >
> > wait_for_completion_timeout() returns unsigned long (0
On Sat, Apr 27, 2019 at 3:01 AM Nicholas Mc Guire wrote:
> > > (some unrelated sparse warnings (cast to restricted __be16))
> >
> > That sounds interesting too. Could you provide more details?
>
> make C=1
> drivers/staging/fieldbus/anybuss/host.c:1350:25: warning: cast to restricted
> __be16
> d
Dear Sir/Madam,
This email must come to you as a surprise, but I believe that it takes just a
day for people to meet and become great friends and business partners. This is
a personal and private letter directed to you and I request that it be treated
as such.
Please you need firstly signify y
The variable type and the type field is inconsistent.
Signed-off-by: Hao Lee
---
drivers/tty/serial/8250/8250_pnp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_pnp.c
b/drivers/tty/serial/8250/8250_pnp.c
index 431e69a5a6a0..9dea11baf479 10
On Sat, Apr 27, 2019 at 04:00:15PM +0800, Hao Lee wrote:
> The variable type and the type field is inconsistent.
In what way? Please be very specific when you resend this.
thanks,
greg k-h
(Note at bottom on reasons for 'To' list 'Cc' list)
Hi,
kobject_init_and_add() seems to be routinely misused. A failed call to this
function requires a call to kobject_put() otherwise we leak memory.
Examples memleaks can be seen in:
mm/slub.c
fs/btrfs/sysfs.c
fs/xfs/xf
On Tue, Apr 23, 2019 at 06:30:10AM -0700, Paul E. McKenney wrote:
> On Tue, Apr 23, 2019 at 02:32:09PM +0200, Peter Zijlstra wrote:
> > On Sat, Apr 20, 2019 at 01:54:40AM -0700, Paul E. McKenney wrote:
> > > And atomic_set(): set_preempt_state(). This fails
> > > on x86, s390, and TSO friends,
On 24-03-19, 10:20, Bjorn Andersson wrote:
> Add a node describing the Turing Clock Controller of the QCS404. Given
> the default access restriction the node is left disabled.
Reviewed-by: Vinod Koul
>
> Signed-off-by: Bjorn Andersson
> ---
> arch/arm64/boot/dts/qcom/qcs404.dtsi | 12
On 24-03-19, 10:20, Bjorn Andersson wrote:
It would have been great to explain the change and why we are moving the
node :)
> Signed-off-by: Bjorn Andersson
> ---
> arch/arm64/boot/dts/qcom/qcs404.dtsi | 88 ++--
> 1 file changed, 57 insertions(+), 31 deletions(-)
>
> d
On Sat, Apr 27, 2019 at 08:19:35AM +0200, Christoph Hellwig wrote:
> None of these is used in modular code, and we should probably try to
> keep it that way. They can be added back if we really get a legitimate
> modular user.
You're going to love this:
87df26175e67 ("x86/mm: Unbreak modules tha
On Sat, Apr 27, 2019 at 10:17:38AM +0200, Andrea Parri wrote:
> On Tue, Apr 23, 2019 at 06:30:10AM -0700, Paul E. McKenney wrote:
> > On Tue, Apr 23, 2019 at 02:32:09PM +0200, Peter Zijlstra wrote:
> > > On Sat, Apr 20, 2019 at 01:54:40AM -0700, Paul E. McKenney wrote:
> > > > And atomic_se
On Sat, 27 Apr 2019 at 16:09, Greg KH wrote:
>
> On Sat, Apr 27, 2019 at 04:00:15PM +0800, Hao Lee wrote:
> > The variable type and the type field is inconsistent.
>
> In what way? Please be very specific when you resend this.
The main problem is the dev_dbg statement should print the value of
u
* Andy Lutomirski wrote:
> > On Apr 26, 2019, at 2:58 AM, Ingo Molnar wrote:
> >
> >
> > * Ingo Molnar wrote:
> >
> >> I really don't like it where this is going. In a couple of years I
> >> really want to be able to think of PTI as a bad dream that is mostly
> >> over fortunately.
> >>
> >>
On Fri, Apr 26, 2019 at 11:18:48AM +0800, Zhao, Yakui wrote:
> It seems that it is seldom used in kernel although the explicit register
> variable is supported by GCC and makes the code look simpler. And it seems
> that the explicit register variable is not suppoorted by CLAG.
The more reason not
Andy Shevchenko writes:
> On Fri, Apr 26, 2019 at 06:54:05PM +0200, Esben Haabendal wrote:
>> Andy Shevchenko writes:
>> > On Fri, Apr 26, 2019 at 10:40:37AM +0200, Esben Haabendal wrote:
>> >> With serial8250_register_8250_port() forcing UPF_BOOT_AUTOCONF bit on, it
>> >> is not possible to reg
On Sat, Apr 27, 2019 at 04:41:44PM +0800, Hao Lee wrote:
> On Sat, 27 Apr 2019 at 16:09, Greg KH wrote:
> >
> > On Sat, Apr 27, 2019 at 04:00:15PM +0800, Hao Lee wrote:
> > > The variable type and the type field is inconsistent.
> >
> > In what way? Please be very specific when you resend this.
>
* Mel Gorman wrote:
> On Fri, Apr 26, 2019 at 11:45:45AM +0200, Ingo Molnar wrote:
> >
> > * Mel Gorman wrote:
> >
> > > > > I can show a comparison with equal levels of parallelisation but with
> > > > > HT off, it is a completely broken configuration and I do not think a
> > > > > compar
* Aubrey Li wrote:
> I have the same environment setup above, for nosmt cases, I used
> /sys interface Thomas mentioned, below is the result:
>
> NA/AVX baseline(std%) coresched(std%) +/- nosmt(std%) +/-
> 1/1 1.987( 1.97%) 2.043( 1.76%) -2.84% 1.985( 1.70%) 0.12%
> NA/AVX basel
On Thu, Apr 25, 2019 at 08:42:22PM +0200, Janusz Krzysztofik wrote:
> Hi Ladislav,
>
> On Thursday, April 25, 2019 12:14:28 AM CEST Ladislav Michl wrote:
> > Hi Janusz,
> >
> > On Wed, Apr 24, 2019 at 08:02:12PM +0200, Janusz Krzysztofik wrote:
> > > After recent modifications, only a hardcoded p
The dev_dbg statement should print the value of uart.port.mapbase instead
of its address. Besides that, uart.port.irq and uart.port.iotype are all
unsigned types, so using %u is more appropriate.
Signed-off-by: Hao Lee
---
drivers/tty/serial/8250/8250_pnp.c | 4 ++--
1 file changed, 2 insertions
weit_for_completion_interruptible returns in (0 on completion and
-ERESTARTSYS on interruption) - so use an int not long for API conformance
and simplify the logic here a bit: need not check explicitly for == 0 as
this is either -ERESTARTSYS or 0.
Signed-off-by: Nicholas Mc Guire
---
Problem lo
Eric Wong wrote:
> Omar Kilani wrote:
> > Hi there,
> >
> > I’m still trying to piece together a reproducible test that triggers
> > this, but I wanted to post in case someone goes “hmmm... change X
> > might have done this”.
>
> Maybe Davidlohr knows, since he's responsible for most of the
> e
On 27-04-19 02:44, Stephen Boyd wrote:
> Quoting Mike Looijmans (2019-04-25 23:51:15)
>> On 26-04-19 01:04, Stephen Boyd wrote:
>>> Quoting Mike Looijmans (2019-04-24 02:02:16)
Adds the devicetree bindings for the si5341 driver that supports the
Si5341 and Si5340 chips.
Signed-o
27.04.2019 в 00:46:53 +0200 Lukasz Majewski написал:
> Hi Arnd,
>
> > As Stepan Golosunov points out, we made a small mistake in the
> > get_timespec64() function in the kernel. It was originally added under
> > the assumption that CONFIG_64BIT_TIME would get enabled on all 32-bit
> > and 64-bit a
With an upcoming patch improving x86' ftrace_int3_handler() not to simply
skip over the insn being updated, ftrace_ops_list_func() will have to get
referenced from arch/x86 code. Drop its 'static' qualifier.
Signed-off-by: Nicolai Stange
---
kernel/trace/ftrace.c | 8
1 file changed, 4
Before actually rewriting an insn, x86' DYNAMIC_FTRACE implementation
places an int3 breakpoint on it. Currently, ftrace_int3_handler() simply
treats the insn in question as nop and advances %rip past it. An upcoming
patch will improve this by making the int3 trap handler emulate the call
insn. To
Hi,
this series is the result of the discussion to the RFC patch found at [1].
The goal is to make x86' ftrace_int3_handler() not to simply skip over
the trapping instruction as this is problematic in the context of
the live patching consistency model. For details, c.f. the commit message
of [3/4
With dynamic ftrace, ftrace patches call sites on x86 in a three steps:
1. Put a breakpoint at the to be patched location,
2. update call site and
3. finally remove the breakpoint again.
Note that the breakpoint ftrace_int3_handler() simply makes execution to
skip over the to be patched instructio
There had been an issue with interactions between tracing and live patching
due to how x86' CONFIG_DYNAMIC_FTRACE used to handle the breakpoints at the
updated instructions from its ftrace_int3_handler().
More specifically, starting to trace a live patched function caused a short
period in time wh
Assalamualaikum My Dear Friend,
Before I introduce myself, I wish to inform you that this letter is
not a hoax mail and I urge you to treat it serious. This letter must
come to you as a big surprise, but I believe it is only a day that
people meet and become great friends and business partners. Pl
* nadav.a...@gmail.com wrote:
> From: Nadav Amit
>
> *
> * This version fixes failed boots on 32-bit that were reported by 0day.
> * Patch 5 is added to initialize uprobes during fork initialization.
> * Patch 7 (which was 6 in the previous version) is updated - the code is
> * moved to commo
Hi Bjorn,
On Fri, Apr 26, 2019 at 10:30:34PM -0700, Bjorn Andersson wrote:
> On Tue 05 Mar 16:53 PST 2019, Brian Masney wrote:
>
> > Here are some patches that fix gpio hogging for all boards that use
> > spmi-gpio and ssbi-gpio. These depend on the following two patches
> > that were merged in 4
On Fri, Apr 26, 2019 at 08:20:52PM -0400, Prarit Bhargava wrote:
> Heiko and Jessica,
>
> The issue doesn't appear to be with my patch AFAICT. The s390_trng fails to
> load and then the kernel occasionally hangs (as Heiko mentioned) calling
> synchronize_rcu().
>
> The call sequence is
>
> modu
On Sat, Apr 27, 2019 at 12:06:38PM +0200, Nicolai Stange wrote:
> ftrace_int3_handler()'s context is different from the interrupted call
> instruction's one, obviously. In order to be able to emulate the call
> within the original context, make ftrace_int3_handler() set its iret
> frame's ->ip to s
On Fri, Apr 26, 2019 at 04:22:39PM -0700, nadav.a...@gmail.com wrote:
> From: Nadav Amit
>
> *
> * This version fixes failed boots on 32-bit that were reported by 0day.
> * Patch 5 is added to initialize uprobes during fork initialization.
> * Patch 7 (which was 6 in the previous version) is upda
On 4/27/19 6:24 AM, Heiko Carstens wrote:
> On Fri, Apr 26, 2019 at 08:20:52PM -0400, Prarit Bhargava wrote:
>> Heiko and Jessica,
>>
>> The issue doesn't appear to be with my patch AFAICT. The s390_trng fails to
>> load and then the kernel occasionally hangs (as Heiko mentioned) calling
>> syn
On 4/27/19 6:24 AM, Heiko Carstens wrote:
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 410eeb7e4f1d..48748cfec991 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3585,6 +3585,7 @@ again:
> finished_loading(mod->name));
>
* Ingo Molnar wrote:
> * Andy Lutomirski wrote:
>
> > > And no, I'm not arguing for Java or C#, but I am arguing for a saner
> > > version of C.
> >
> > IMO three are three credible choices:
> >
> > 1. C with fairly strong CFI protection. Grsecurity has this (supposedly
> > — there’s a dis
The Hygon Dhyana CPU has the SMBus device with PCI device ID 0x790b,
which is the same as AMD CZ SMBus device. So add Hygon Dhyana support
to the i2c-piix4 driver by using the code path of AMD.
Signed-off-by: Pu Wen
---
v1->v2:
- Remove the revision number checking for Hygon SMBus device.
- D
On Sat, Apr 27, 2019 at 03:20:54AM -0400, Sven Van Asbroeck wrote:
> On Sat, Apr 27, 2019 at 3:01 AM Nicholas Mc Guire wrote:
> > > > (some unrelated sparse warnings (cast to restricted __be16))
> > >
> > > That sounds interesting too. Could you provide more details?
> >
> > make C=1
> > drivers/s
On 27.04.19 10:58, Esben Haabendal wrote:
Hi folks,
> That said, the purpose of UPF_BOOT_AUTOCONF (for 8250 driver) is to> request
> and map the register memory. So when that is already done by>
the parent MFD driver, I think it is silly to workaround problems
caused> by UPF_BOOT_AUTOCONF being
On Fri, 26 Apr 2019 14:33:09 -0500
Rob Herring wrote:
> On Mon, Apr 22, 2019 at 08:07:48PM +0530, Manish Narani wrote:
> > Xilinx AMS have several ADC channels that can be used for measurement of
> > different voltages and temperatures. Document the same in the bindings.
> >
> > Signed-off-by: M
On Tue, 23 Apr 2019 15:50:03 +0800
Kefeng Wang wrote:
> Using dev_get_drvdata directly.
>
> Cc: Ludovic Desroches
> Cc: Jonathan Cameron
> Cc: linux-...@vger.kernel.org
> Signed-off-by: Kefeng Wang
A sensible cleanup, thanks.
Applied to the togreg branch of iio.git and pushed out as testing
On Tue, 23 Apr 2019 16:06:56 +0200
Alexandre wrote:
> Hi Peter,
>
> On 4/23/19 13:33, Peter Meerwald-Stadler wrote:
> >
> > how is this thing different from a mouse device?
>
> I developed this driver to detect the board movement which can't be
> detected by accelerometer (very slow motion).
On Wed, 2019-03-27 at 23:47 +, David Howells wrote:
> Convert the ceph filesystem to the new internal mount API as the old
> one will be obsoleted and removed. This allows greater flexibility in
> communication of mount parameters between userspace, the VFS and the
> filesystem.
>
> See Docum
I'm announcing the release of the 3.18.139 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Documentation/arm/kernel_mode_neon.txt
b/Documentation/arm/kernel_mode_neon.txt
index 525452726d31..b9e060c5b61e 100644
--- a/Documentation/arm/kernel_mode_neon.txt
+++ b/Documentation/arm/kernel_mode_neon.txt
@@ -6,7 +6,7 @@ TL;DR summary
* Use only NEON instructions, or VFP instruc
I'm announcing the release of the 4.4.179 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 966069dab768..dbdef749e1c8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 170
+SUBLEVEL = 171
EXTRAVERSION =
NAME = Roaring Lionus
@@ -655,8 +655,7 @@ KBUILD_CFLAGS += $(call cc-option,-fdata-sections,)
I'm announcing the release of the 4.14.114 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser
I'm announcing the release of the 4.9.171 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 5.0.10 kernel.
All users of the 5.0 kernel series must upgrade.
The updated 5.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.0.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.19.37 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index ef192ca04330..b282c4143b21 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 0
-SUBLEVEL = 9
+SUBLEVEL = 10
EXTRAVERSION =
NAME = Shy Crocodile
@@ -678,8 +678,7 @@ KBUILD_CFLAGS += $(c
On Tue, 23 Apr 2019 13:33:13 +0200 (CEST)
Peter Meerwald-Stadler wrote:
> some comments below...
> a link to the datasheet would be nice
>
> > This adds support for PixArt Imaging’s miniature low power
> > optical navigation chip using LASER light source
> > enabling digital surface tracking.
>
On Thu, 25 Apr 2019 09:35:07 +0800
Matt Ranostay wrote:
> On Wed, Apr 24, 2019 at 5:42 AM Daniel Gomez wrote:
> >
> > Add missing table for SPI driver relying on SPI
> > device match since compatible is in a DT binding or in a DTS.
> >
> > Before this patch:
> > modinfo drivers/iio/temperature/
checkpatch complaints:
WARNING: printk() should include KERN_ facility level
#698: FILE: drivers/tty/serial/sb1250-duart.c:698:
+ printk(err);
WARNING: printk() should include KERN_ facility level
#706: FILE: drivers/tty/serial/sb1250-duart.c:706:
+
Using dev_err() instead of printk() for more consistent output.
(prints device name, etc).
Signed-off-by: Enrico Weigelt
---
drivers/tty/serial/dz.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/serial/dz.c b/drivers/tty/serial/dz.c
index 7b57e84..96e35a
Fixing checkpatch warning:
WARNING: Use #include instead of
#25: FILE: drivers/tty/serial/cpm_uart/cpm_uart_cpm2.c:25:
+#include
WARNING: Use #include instead of
+#include
WARNING: Use #include instead of
+#include
Signed-off-by: Enrico Weigelt
---
drivers
Fix checkpatch warnings:
WARNING: line over 80 characters
#283: FILE: drivers/tty/serial/uartlite.c:283:
+ ret = request_irq(port->irq, ulite_isr, IRQF_SHARED |
IRQF_TRIGGER_RISING,
WARNING: Missing a blank line after declarations
#577: FILE: drivers/tty/serial/uartlite.c:5
On Tue, 23 Apr 2019 23:40:59 +0200
Daniel Gomez wrote:
> Add missing table for SPI driver relying on SPI
> device match since compatible is in a DT binding or in a DTS.
>
> Before this patch:
> modinfo drivers/iio/accel/kxsd9-spi.ko | grep alias
> alias: spi:kxsd9
>
> After this patc
Fill the struct uart_port->mapsize field and use it, insteaf of
hardcoded values in many places. This makes the code layout a bit
more consistent and easily allows using generic helpers for the
io memory handling.
Candidates for such helpers could be eg. the request+ioremap and
iounmap+release com
Fix checkpatch warning:
WARNING: Use #include instead of
#41: FILE: drivers/tty/serial/sb1250-duart.c:41:
+#include
Signed-off-by: Enrico Weigelt
---
drivers/tty/serial/sb1250-duart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/sb1250-du
On Tue, 23 Apr 2019 23:41:37 +0200
Daniel Gomez wrote:
> Add missing table for SPI driver relying on SPI
> device match since compatible is in a DT binding or in a DTS.
>
> Before this patch:
> modinfo drivers/iio/accel/adxl372_spi.ko | grep alias
>
> After this patch:
> modinfo drivers/iio/ac
Fix checkpatch warning:
ERROR: Macros with complex values should be enclosed in parentheses
#911: FILE: drivers/tty/serial/sb1250-duart.c:911:
+#define SERIAL_SB1250_DUART_CONSOLE&sbd_console
Signed-off-by: Enrico Weigelt
---
drivers/tty/serial/sb1250-duart.c | 2 +-
1 file
Fill the struct uart_port->mapsize field and use it, insteaf of
hardcoded values in many places. This makes the code layout a bit
more consistent and easily allows using generic helpers for the
io memory handling.
Candidates for such helpers could be eg. the request+ioremap and
iounmap+release com
On Tue, 23 Apr 2019 23:41:58 +0200
Daniel Gomez wrote:
> Add missing table for SPI driver relying on SPI
> device match since compatible is in a DT binding or in a DTS.
>
> Before this patch:
> modinfo drivers/iio/dac/ad5758.ko | grep alias
> alias: spi:ad5758
>
> After this patch:
>
On Fri, Apr 26, 2019 at 10:41:20AM +0100, Ian Abbott wrote:
> On 25/04/2019 18:13, Greg Kroah-Hartman wrote:
> > On Thu, Apr 25, 2019 at 05:26:44PM +0100, Ian Abbott wrote:
> > > The "comedi_isadma" module calls `dma_alloc_coherent()` and
> > > `dma_free_coherent()` with a NULL device pointer which
On Thu, 25 Apr 2019 19:03:14 -0400
Brian Masney wrote:
> Convert the tsl2583 device tree bindings to the new YAML format.
>
> Signed-off-by: Brian Masney
> Reviewed-by: Rob Herring
Applied to the togreg branch of iio.git and pushed out as
testing for the autobuilders to play with it.
Thanks,
On Fri, 26 Apr 2019 08:20:34 -0500
Rob Herring wrote:
> On Thu, Apr 25, 2019 at 6:03 PM Brian Masney wrote:
> >
> > Convert the tsl2772 device tree bindings to the new YAML format.
> >
> > Signed-off-by: Brian Masney
> > ---
> > Changes since v2:
> > - Remove allof from led-max-microamp. Split
On Wed, 24 Apr 2019 14:55:09 +0200
Fabrice Gasnier wrote:
> On 4/24/19 2:51 PM, Fabien Dessenne wrote:
> > During probe, check the "get_irq" error value.
> >
> > Signed-off-by: Fabien Dessenne
> > ---
>
> Hi Fabien,
>
> Acked-by: Fabrice Gasnier
Applied to the togreg branch of iio.git and
On Wed, 24 Apr 2019 14:55:28 +0200
Fabrice Gasnier wrote:
> On 4/24/19 2:51 PM, Fabien Dessenne wrote:
> > During probe, check the devm_ioremap_resource() error value.
> > Also return the devm_clk_get() error value instead of -EINVAL.
> >
> > Signed-off-by: Fabien Dessenne
> > ---
>
>
> Hi
On Fri, 26 Apr 2019 13:39:16 +0200
Fabien Lahoudere wrote:
> From: Gwendal Grignou
>
> This new sysfs entry is used to interpret ring buffer information,
> mainly by Android sensor HAL.
> It expand to all sensors, the documentation about 'id' we can found
> in Documentation/ABI/testing/sysfs-bu
On Sat, 27 Apr 2019 00:40:06 +0800
Yue Haibing wrote:
> From: YueHaibing
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/iio/dac/ad5758.c: In function ad5758_write_powerdown:
> drivers/iio/dac/ad5758.c:585:15: warning: variable dc_dc_mode set but not
> used [-Wunused-but-set-va
On Wed, 24 Apr 2019 17:29:32 -0700
Gwendal Grignou wrote:
> Add a IIO driver that reports the angle between the lid and the base for
> ChromeOS convertible device.
>
> Tested on eve with ToT EC firmware.
> Check driver is loaded and lid angle is correct.
>
> Signed-off-by: Gwendal Grignou
I am
Hi friend I am a banker in ADB BANK. I want to transfer an abandoned
$10.2Million to your Bank account. 40/percent will be your share.
For more details contanct me urgently. Yours Mr Ghazi Ahmed
Hi friend I am a banker in ADB BANK. I want to transfer an abandoned
$10.2Million to your Bank account. 40/percent will be your share.
For more details contanct me urgently. Yours Mr Ghazi Ahmed
On Sat, 27 Apr 2019 14:21:12 +0100
Jonathan Cameron wrote:
> On Wed, 24 Apr 2019 17:29:32 -0700
> Gwendal Grignou wrote:
>
> > Add a IIO driver that reports the angle between the lid and the base for
> > ChromeOS convertible device.
> >
> > Tested on eve with ToT EC firmware.
> > Check driver
On Fri, Apr 26, 2019 at 02:37:27PM +0300, Mika Westerberg wrote:
> Hi Greg,
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kerne
On Fri, Apr 26, 2019 at 06:34:22AM -0700, Nathan Chancellor wrote:
> On Fri, Apr 26, 2019 at 01:23:17PM +, Rantala, Tommi T. (Nokia -
> FI/Espoo) wrote:
> > On Fri, 2019-04-26 at 05:48 -0700, Nathan Chancellor wrote:
> > > On Fri, Apr 26, 2019 at 11:41:30AM +, Rantala, Tommi T. (Nokia -
>
> On Apr 26, 2019, at 11:02 AM, Theodore Ts'o wrote:
>
>> On Fri, Apr 26, 2019 at 10:44:20AM -0700, Eric Biggers wrote:
>> Would it be possibly to call ChaCha20 through the actual crypto API so that
>> SIMD
>> instructions (e.g. AVX-2) could be used? That would make it *much* faster.
>> Also
On Sat, Apr 27, 2019 at 5:17 PM Ingo Molnar wrote:
>
>
> * Aubrey Li wrote:
>
> > I have the same environment setup above, for nosmt cases, I used
> > /sys interface Thomas mentioned, below is the result:
> >
> > NA/AVX baseline(std%) coresched(std%) +/- nosmt(std%) +/-
> > 1/1 1.987(
On Sat, Apr 27, 2019 at 7:18 AM Nicholas Mc Guire wrote:
>
> so the issue is simply that the endiannes anotatoin is missing even
> though the conversion is being done - with other words there is no code
> lvel funcitonal bug here but rather sparse needs the anotation to verify
> correctness and th
* Aubrey Li wrote:
> On Sat, Apr 27, 2019 at 5:17 PM Ingo Molnar wrote:
> >
> >
> > * Aubrey Li wrote:
> >
> > > I have the same environment setup above, for nosmt cases, I used
> > > /sys interface Thomas mentioned, below is the result:
> > >
> > > NA/AVX baseline(std%) coresched(std%) +/-
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 82c99f7a81f28f8c1be5f701c8377d14c4075b10 perf/x86/intel: Update KBL
Package C-state events to also include PC8/PC9/PC10 counters
A c
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: a860fa7b96e1a1c974556327aa1aee852d434c21 sched/numa: Fix a possible
divide-by-zero
Fix a division by zero bug that can trigger in
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 0d02113b31b2017dd349ec9df2314e798a90fa6e x86/mm: Fix a crash with
kmemleak_scan()
Two fixes:
- Fix an early boot crash in the RSDP p
Hi Stepan,
> 27.04.2019 в 00:46:53 +0200 Lukasz Majewski написал:
> > Hi Arnd,
> >
> > > As Stepan Golosunov points out, we made a small mistake in the
> > > get_timespec64() function in the kernel. It was originally added
> > > under the assumption that CONFIG_64BIT_TIME would get enabled on
>
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Darrick J. Wong"
commit 29b00e609960ae0fcff382f4c7079dd0874a5311 upstream.
When we made the shmem_reserve_inode call in shmem_link conditional, we
forgot to update the declaration for ret so
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jose Abreu
commit 8a7493e58ad688eb23b81e45461c5d314f4402f1 upstream.
We are saving the status of EEE even before we try to enable it. This
leads to a race with XMIT function that tries to arm
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 492855939bdb59c6f947b0b5b44af9ad82b7e38c upstream.
Memory backed DMA mappings are accounted against a user's locked
memory limit, including multiple mappings of the same
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 4aa68e07d845562561f5e73c04aa521376e95252 upstream.
When checking for permission to view keys whilst reading from
/proc/keys, we should use the credentials with which the /p
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 1524f4e47f90b27a3ac84efbdd94c63172246a6f upstream.
The "chip->dsp_spos_instance" can be NULL on some of the ealier error
paths in snd_cs46xx_create().
Reported-by: "Yavuz
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 10628e3ecf544fa2e4e24f8e112d95c37884dc98 upstream.
This function is supposed to return zero on success or negative error
codes on error. Unfortunately, there is a bug so
The blackfin architecture has been removed a while ago, so there is
no more need to declare uclinux_ram_map as a global structure.
Signed-off-by: Thomas Huth
---
drivers/mtd/maps/uclinux.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/mtd/maps/uclinux.c b/dri
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Nathan Sullivan
commit d2fd719bcb0e83cb39cfee22ee800f98a56eceb3 upstream.
Very rarely, the KSZ9031 will appear to complete autonegotiation, but
will drop all traffic afterwards. When this hap
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
commit 6454368a804c4955ccd116236037536f81e5b1f1 upstream.
In case of mapping error the DMA addresses are invalid and continuing
will screw system memory or potentially somethin
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
commit 4f2ab5e1d13d6aa77c55f4914659784efd776eb4 upstream.
It is normal user behaviour to start, stop, then start a stream
again without closing it. Currently this works for comp
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit e4dc894b61776733629b24507031dd46f5ba5efc upstream.
Use the more generic functions get_signal() signal_setup_done()
for signal delivery.
Signed-off-by: Richard Weinbe
3.16.66-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit b8e9dc1c75714ceb53615743e1036f76e00f5a17 upstream.
Taehee Yoo reported following bug:
iptables-compat -I OUTPUT -m cpu --cpu 0
iptables-compat -F
lsmod |gre
1 - 100 of 416 matches
Mail list logo
