On Fri, Nov 02, 2018 at 04:32:06PM +0100, Arnd Bergmann wrote:
> We cannot currently select ACPI_ADXL without also enabling the top-level
> ACPI option:
>
> WARNING: unmet direct dependencies detected for ACPI_ADXL
> Depends on [n]: ACPI [=n]
> Selected by [y]:
> - EDAC_SKX [=y] && EDAC [=y]
Hi,
On 01.11.2018 21:42, Song Liu wrote:
> On Sun, Oct 14, 2018 at 11:45 PM Alexey Budankov
> wrote:
>>
>> + if (verbose > 0)
>> + pr_info("nr_cblocks: %d\n", rec->opts.nr_cblocks);
>> +
>
> nit: I guess we don't really need this pr_info()?
Diagnostic aid.
Thanks,
Alexey
On Fri, 2 Nov 2018, Linus Walleij wrote:
> On Thu, Nov 1, 2018 at 4:27 PM Linus Walleij wrote:
> > On Thu, Nov 1, 2018 at 2:13 PM Muchun Song wrote:
> >
> > > gpiod_request_commit() copies the pointer to the label passed as
> > > an argument only to be used later. But there's a chance the caller
Hi,
On 01.11.2018 21:30, Song Liu wrote:
> On Sun, Oct 14, 2018 at 11:47 PM Alexey Budankov
> wrote:
>>
>>
>>
>> static int nr_cblocks_default = 1;
>>
>> static int record__aio_parse(const struct option *opt,
>> -const char *str __maybe_unused,
>> +
On Fri 02-11-18 15:48:57, Roman Gushchin wrote:
> On Fri, Nov 02, 2018 at 09:03:55AM +0100, Michal Hocko wrote:
> > On Fri 02-11-18 02:45:42, Dexuan Cui wrote:
> > [...]
> > > I totally agree. I'm now just wondering if there is any temporary
> > > workaround,
> > > even if that means we have to ru
From: Randy Dunlap
arch/sh/boards/mach-kfr2r09/setup.c does not need to #include
, and doing so causes a build warning, so drop
that header file.
In file included from ../arch/sh/boards/mach-kfr2r09/setup.c:28:
../include/linux/mtd/onenand.h:225:12: warning: 'struct mtd_oob_ops' declared
inside
Hi,
On 01.11.2018 21:47, Song Liu wrote:
> On Sun, Oct 14, 2018 at 11:44 PM Alexey Budankov
> wrote:
>>
>>
>> The map->data buffer is used to preserve map->base profiling data
>> for writing to disk. AIO map->cblock is used to queue corresponding
>> map->data buffer for asynchronous writing.
>>
>
On Fri, Nov 02, 2018 at 10:53:00AM +0100, Borislav Petkov wrote:
> On Mon, Oct 29, 2018 at 04:06:51PM -0500, Bjorn Helgaas wrote:
> > If I squint hard enough this sort of makes sense, but it also makes me
> > confused about the normal APEI firmware-first model works.
> >
> > In the NON-firmare-fir
On Fri, Nov 02, 2018 at 05:13:14PM +0100, Michal Hocko wrote:
> On Fri 02-11-18 15:48:57, Roman Gushchin wrote:
> > On Fri, Nov 02, 2018 at 09:03:55AM +0100, Michal Hocko wrote:
> > > On Fri 02-11-18 02:45:42, Dexuan Cui wrote:
> > > [...]
> > > > I totally agree. I'm now just wondering if there is
On Fri, Nov 02, 2018 at 10:17:30AM -0600, Keith Busch wrote:
> VMD acts a bit like a host-bus adapter. The firmware knows about the
> adapter, but not about anything on the bus that it attaches to.
>
> This "hybrid" approach is basically saying that the firmware knows about
> the HBA, and it wants
On Thu, Nov 01, 2018 at 04:22:55PM -0700, Andy Lutomirski wrote:
> On Thu, Nov 1, 2018 at 2:24 PM Linus Torvalds
> wrote:
> >
> > On Thu, Nov 1, 2018 at 12:31 PM Rich Felker wrote:
> > >
> > > See my other emails in this thread. You would register the *address*
> > > (in TLS) of a function pointe
On Thu, Nov 1, 2018 at 10:15 PM Dave Chinner wrote:
>
> Can you please pull update containing a rework of the VFS clone and
> dedupe file range infrastructure from the tag listed below?
I don't love the timing of this at the end of the merge window, but pulled,
Linus
Hi,
On Fri, Nov 2, 2018 at 9:19 AM Arnd Bergmann wrote:
>
> In some configurations the inlining in gcc is suboptimal, causing
> a false-positive warning:
>
> drivers/net/wireless/ath/ath10k/mac.c: In function 'ath10k_mac_init_rd':
> drivers/net/wireless/ath/ath10k/mac.c:8374:39: error: 'rd' may b
Hi Adam
On Thu, Nov 01, 2018 at 07:51:38AM -0500, Adam Ford wrote:
> This adds support for the Ampire am800480b3tmqw display,
> a 7" 24-bit RGB panel wtih 800x480 resolution.
>
> Signed-off-by: Adam Ford
>
> diff --git a/drivers/gpu/drm/panel/panel-simple.c
> b/drivers/gpu/drm/panel/panel-simp
On 2018-11-02 09:30, Sean Christopherson wrote:
... The intended convention for EENTER is to have an ENCLU at the AEX target ...
... to further enforce that the AEX target needs to be ENCLU.
Some SGX runtimes may want to use a different AEX target.
--
Jethro Beekman | Fortanix
smime.p7s
De
On Fri, Nov 02, 2018 at 05:26:23PM +0100, Borislav Petkov wrote:
> On Fri, Nov 02, 2018 at 10:17:30AM -0600, Keith Busch wrote:
> > VMD acts a bit like a host-bus adapter. The firmware knows about the
> > adapter, but not about anything on the bus that it attaches to.
> >
> > This "hybrid" approac
On Thu, Nov 1, 2018 at 7:19 PM Palmer Dabbelt wrote:
>
> RISC-V: refresh defconfig
Pulled,
Linus
Quoting Taniya Das (2018-10-28 00:35:40)
> Add support for the lpass clock controller found on SDM845 based devices.
> This would allow lpass peripheral loader drivers to control the clocks to
> bring the subsystem out of reset.
> LPASS clocks present on the global clock controller would be registe
On Fri 02-11-18 16:22:41, Roman Gushchin wrote:
> On Fri, Nov 02, 2018 at 05:13:14PM +0100, Michal Hocko wrote:
> > On Fri 02-11-18 15:48:57, Roman Gushchin wrote:
> > > On Fri, Nov 02, 2018 at 09:03:55AM +0100, Michal Hocko wrote:
> > > > On Fri 02-11-18 02:45:42, Dexuan Cui wrote:
> > > > [...]
>
The driver is for C-SKY SMP timer. It only support oneshot event
and 32bit overflow for clocksource. Per cpu core has one timer and
all timers share one clock-counter-input the same clocksource.
This use mfcr&mtcr instructions to access the regs.
Signed-off-by: Guo Ren
Cc: Daniel Lezcano
Cc: Th
Dt-bindings doc for gx6605s SOC's system timer.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/csky,gx6605s-timer.tx
Dt-bingdings doc for C-SKY SMP system setting.
Signed-off-by: Guo Ren
Reviewed-by: Rob Herring
---
Changelog:
- Drop the interrupt-parent.
---
---
.../devicetree/bindings/timer/csky,mptimer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/
The driver is for gx6605s SOC system timer and there are two
same timers in gx6605s. We use one for clkevt and another one for
clksrc.
The timer is mmio map to access, so we need give mmio address in dts.
The counter at 0x0 offset is clock event.
The counter at 0x40 offset is clock source.
Sign
On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
> On 2018-11-02 09:30, Sean Christopherson wrote:
> >... The intended convention for EENTER is to have an ENCLU at the AEX target
> >...
> >
> >... to further enforce that the AEX target needs to be ENCLU.
>
> Some SGX runtimes may w
On 2018-11-02 09:52, Sean Christopherson wrote:
On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
On 2018-11-02 09:30, Sean Christopherson wrote:
... The intended convention for EENTER is to have an ENCLU at the AEX target ...
... to further enforce that the AEX target needs to b
On 11/2/18 9:30 AM, Sean Christopherson wrote:
> What if rather than having userspace register an address for fixup, the
> kernel instead unconditionally does fixup on the ENCLU opcode?
The problem is knowing what to do for the fixup. If we have a simple
action to take that's universal, like back
On Fri, 2018-11-02 at 15:16 +0200, Amir Goldstein wrote:
> On Fri, Nov 2, 2018 at 2:44 PM Seth Forshee om> wrote:
> >
> > On Fri, Nov 02, 2018 at 12:02:45PM +0200, Amir Goldstein wrote:
> > > On Thu, Nov 1, 2018 at 11:49 PM Seth Forshee > > cal.com> wrote:
> > > >
> > > > shiftfs mounts cannot
As I'll no longer be working with Arm, add a mailmap entry so any mail
directed towards me reaches the appropriate mailbox.
Signed-off-by: Punit Agrawal
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index a76be45fef6c..28fecafa6506 100644
--- a/.mailmap
+++
On Fri, Nov 2, 2018 at 9:56 AM Jethro Beekman wrote:
>
> On 2018-11-02 09:52, Sean Christopherson wrote:
> > On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
> >> On 2018-11-02 09:30, Sean Christopherson wrote:
> >>> ... The intended convention for EENTER is to have an ENCLU at the
On Fri, Nov 02, 2018 at 01:22:42PM +, Will Deacon wrote:
> From: Linus Torvalds
>
> Commit eb66ae030829605d61fbef1909ce310e29f78821 upstream.
>
> This is a backport to stable 4.4.y.
Thanks for this, now queued up.
greg k-h
On 2018-11-02 10:01, Andy Lutomirski wrote:
On Fri, Nov 2, 2018 at 9:56 AM Jethro Beekman wrote:
On 2018-11-02 09:52, Sean Christopherson wrote:
On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
On 2018-11-02 09:30, Sean Christopherson wrote:
... The intended convention for EE
On Fri, Nov 02, 2018 at 09:56:44AM -0700, Dave Hansen wrote:
> On 11/2/18 9:30 AM, Sean Christopherson wrote:
> > What if rather than having userspace register an address for fixup, the
> > kernel instead unconditionally does fixup on the ENCLU opcode?
>
> The problem is knowing what to do for the
Instances of "less then" or "greater then" are corrected to "less than" or
"greater than", respectively.
Signed-off-by: Paul Sorensen
---
Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt | 6 +++---
Documentation/hwmon/abituguru-datasheet | 2 +-
Documentation/isdn/syn
Hello Dear
My name is Doctor smith Tracy, I am 26 years old medical doctor from
USA united state of America. presently working and living in the UK
United kingdom, my mum is from french why my father is from USA, I was
just going through the Internet search when i saw your pro
Add support for PF0100 coin cell/super capacitor charger which works as
a current limited voltage source via the LICELL pin. When VIN goes below
a certain threshold LICELL is used to provide power for VSNVS which is
usually used to hold up secure non-volatile storage and the real-time
clock on the
On Fri, Nov 02, 2018 at 04:56:36PM +, Jethro Beekman wrote:
> On 2018-11-02 09:52, Sean Christopherson wrote:
> >On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
> >>On 2018-11-02 09:30, Sean Christopherson wrote:
> >>>... The intended convention for EENTER is to have an ENCLU at
On 11/2/18 10:06 AM, Sean Christopherson wrote:
> On Fri, Nov 02, 2018 at 09:56:44AM -0700, Dave Hansen wrote:
>> On 11/2/18 9:30 AM, Sean Christopherson wrote:
>>> What if rather than having userspace register an address for fixup, the
>>> kernel instead unconditionally does fixup on the ENCLU opc
On Fri, Nov 02, 2018 at 04:57:52PM +, Punit Agrawal wrote:
> As I'll no longer be working with Arm, add a mailmap entry so any mail
> directed towards me reaches the appropriate mailbox.
>
> Signed-off-by: Punit Agrawal
> ---
> .mailmap | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Fri, Nov 2, 2018 at 10:05 AM Jethro Beekman wrote:
>
> On 2018-11-02 10:01, Andy Lutomirski wrote:
> > On Fri, Nov 2, 2018 at 9:56 AM Jethro Beekman wrote:
> >>
> >> On 2018-11-02 09:52, Sean Christopherson wrote:
> >>> On Fri, Nov 02, 2018 at 04:37:10PM +, Jethro Beekman wrote:
> On
On Fri, Nov 2, 2018 at 10:10 AM Linus Torvalds
wrote:
>
> Don't you take over the VM with "use_mm()" when you do the copies? So
> yes, it's a kernel thread, but it has a user VM, and though that
> should have the user limits.
Oooh. *Just* as I sent this, I realized that "use_mm()" doesn't update
When switching to the new iovec accessors, a negation got subtly
dropped, leading to 9p being remarkably broken (here with kvmtool):
[7.430941] VFS: Mounted root (9p filesystem) on device 0:15.
[7.432080] devtmpfs: mounted
[7.432717] Freeing unused kernel memory: 1344K
[7.433658] R
On Fri, Nov 02, 2018 at 10:09:52AM -0700, Paul Sorensen wrote:
> Instances of "less then" or "greater then" are corrected to "less than" or
> "greater than", respectively.
>
> Signed-off-by: Paul Sorensen
> ---
[...]
> diff --git a/mm/slab_common.c b/mm/slab_common.c
> index 7eb8dc136c1c..5e5aa
On Fri, Nov 02, 2018 at 08:36:19AM -0400, Yangtao Li wrote:
> This brings the kernel doc in line with the function signature.
>
> Signed-off-by: Yangtao Li
Queued for 4.20. Thanks.
--
Catalin
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privi
On Fri, Nov 02, 2018 at 05:51:47PM +0100, Michal Hocko wrote:
> On Fri 02-11-18 16:22:41, Roman Gushchin wrote:
> > On Fri, Nov 02, 2018 at 05:13:14PM +0100, Michal Hocko wrote:
> > > On Fri 02-11-18 15:48:57, Roman Gushchin wrote:
> > > > On Fri, Nov 02, 2018 at 09:03:55AM +0100, Michal Hocko wrot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d81f50bd34646d8373b989e55180c0fc9af94e0b
commit: 3c670dba864d9ab0a23612a93b7d98700734bd44 ACPI / PMIC: xpower: Block
P-Unit I2C access during read-modify-write
date: 8 days ago
config: x86_64-randconfig-s3
On Tue, Oct 30, 2018 at 12:38:50PM +0100, Anders Roxell wrote:
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping at address
On Fri, Nov 02, 2018 at 10:13:23AM -0700, Dave Hansen wrote:
> On 11/2/18 10:06 AM, Sean Christopherson wrote:
> > On Fri, Nov 02, 2018 at 09:56:44AM -0700, Dave Hansen wrote:
> >> On 11/2/18 9:30 AM, Sean Christopherson wrote:
> >>> What if rather than having userspace register an address for fixu
On Fri, Nov 02, 2018 at 10:16:02AM -0700, Andy Lutomirski wrote:
> On Fri, Nov 2, 2018 at 10:05 AM Jethro Beekman wrote:
> >
> > On 2018-11-02 10:01, Andy Lutomirski wrote:
> > > On Fri, Nov 2, 2018 at 9:56 AM Jethro Beekman wrote:
> > >>
> > >> On 2018-11-02 09:52, Sean Christopherson wrote:
> >
From: Long Li Sent: Thursday, November 1, 2018 4:52 PM
>
> --- a/kernel/irq/affinity.c
> +++ b/kernel/irq/affinity.c
> @@ -117,12 +117,13 @@ static int irq_build_affinity_masks(const struct
> irq_affinity *affd,
>*/
> if (numvecs <= nodes) {
> for_each_node_mask(n, n
On Fri, Nov 02, 2018 at 05:10:13PM +0100, Borislav Petkov wrote:
> On Fri, Nov 02, 2018 at 04:32:06PM +0100, Arnd Bergmann wrote:
> > We cannot currently select ACPI_ADXL without also enabling the top-level
> > ACPI option:
> >
> > WARNING: unmet direct dependencies detected for ACPI_ADXL
> > De
On Tue, Oct 30, 2018 at 11:10:51AM -0300, Ard Biesheuvel wrote:
> On 30 October 2018 at 08:49, Ard Biesheuvel wrote:
> >> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
> >>
> >> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and
> >> exectuable pages")
> >> has successfully identi
On Fri, Nov 2, 2018 at 1:12 PM wrote:
>
> Add support for PF0100 coin cell/super capacitor charger which works as
Cancel this. A patch for this has already been submitted by Adam Ford:
https://patchwork.kernel.org/patch/10661227/
Not sure why it didn't show up in my search.
Sven
Hello Linus,
On Thu, 1 Nov 2018 09:27:20 -0700
Linus Torvalds wrote:
> On Wed, Oct 31, 2018 at 10:35 PM Boris Brezillon
> wrote:
> >
> > Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
> > was asking if you'd agree to have this framework merged in 4.20 (I know
> > you we
On Fri 02-11-18 17:25:58, Roman Gushchin wrote:
> On Fri, Nov 02, 2018 at 05:51:47PM +0100, Michal Hocko wrote:
> > On Fri 02-11-18 16:22:41, Roman Gushchin wrote:
[...]
> > > 2) We do forget to scan the last page in the LRU list. So if we ended up
> > > with
> > > 1-page long LRU, it can stay the
On Fri, Nov 2, 2018 at 10:33 AM Sean Christopherson
wrote:
>
> On Fri, Nov 02, 2018 at 10:13:23AM -0700, Dave Hansen wrote:
> > On 11/2/18 10:06 AM, Sean Christopherson wrote:
> > > On Fri, Nov 02, 2018 at 09:56:44AM -0700, Dave Hansen wrote:
> > >> On 11/2/18 9:30 AM, Sean Christopherson wrote:
>
On Fri, Nov 02, 2018 at 04:26:07PM +0100, Arnd Bergmann wrote:
> After a good chunk of the swiotlb code has been replaced with the generic
> version, two functions are only used from inside of an #ifdef:
>
> arch/arm64/mm/dma-mapping.c:174:12: error: '__swiotlb_mmap_pfn' defined but
> not used [-
> Subject: RE: [PATCH] genirq/affinity: Spread IRQs to all available NUMA
> nodes
>
> From: Long Li Sent: Thursday, November 1, 2018
> 4:52 PM
> >
> > --- a/kernel/irq/affinity.c
> > +++ b/kernel/irq/affinity.c
> > @@ -117,12 +117,13 @@ static int irq_build_affinity_masks(const struct
> irq_affi
On Freitag, 2. November 2018 12:26:35 CET Jiri Olsa wrote:
> On Thu, Nov 01, 2018 at 11:08:18PM +0100, Milian Wolff wrote:
> > On Dienstag, 30. Oktober 2018 23:34:35 CET Milian Wolff wrote:
> > > On Mittwoch, 24. Oktober 2018 16:48:18 CET Andi Kleen wrote:
> > > > > Can someone at least confirm whe
Hi Kirill,
I noticed that booting 4.19 in qemu while injecting a FDT using the
"-dtb /path/to/blob" feature might have been broken by your change
372fddf70904 ("x86/mm: Introduce the 'no5lvl' kernel parameter").
This manifests either as FDT corruption, which causes the setup code
to fail to unpac
On Thu, Nov 01, 2018 at 04:52:00PM -0700, Kees Cook wrote:
> The actual number of bytes stored in a PRZ is smaller than the
> bytes requested by platform data, since there is a header on each
> PRZ. Additionally, if ECC is enabled, there are trailing bytes used
> as well. Normally this mismatch doe
From: Long Li
On systems with large number of NUMA nodes, there may be more NUMA nodes than
the number of MSI/MSI-X interrupts that device requests for. The current code
always picks up the NUMA nodes starting from the node 0, up to the number of
interrupts requested. This may left some later NUM
On Fri, Nov 2, 2018 at 3:37 AM Takashi Iwai wrote:
>
> A few device-specific fixes: a fix for SPDIF on old Creative PCI
> board, and two additional fixes for the recent changes in FireWire
> audio stack.
Thanks, pulled,
Linus
On Fri, Nov 2, 2018 at 6:11 AM Ayman Bagabas wrote:
>
> This patch set fixes some of the issues with Huawei laptops.
>
Thanks for the series, I'll review it later on.
> [PATCH v2 1/3]
> The first patch adds support for missing hotkeys on some models. Some hotkeys,
> like brightness keys, work ou
On Fri, Nov 2, 2018 at 6:11 AM Ayman Bagabas wrote:
>
> This patch solves bug 200501 'Only 2 of 4 speakers playing sound.'
> https://bugzilla.kernel.org/show_bug.cgi?id=200501
> It enables the front speakers on Huawei Matebook X Pro laptops.
> These laptops come with Dolby Atmos sound system and t
On Fri, Nov 2, 2018 at 6:12 AM Ayman Bagabas wrote:
>
> Some of Huawei laptops come with a LED in the mic mute key. This patch
> enables and disable this LED accordingly.
> --- a/drivers/platform/x86/huawei_wmi.c
> +++ b/drivers/platform/x86/huawei_wmi.c
> @@ -26,6 +26,7 @@
> #include
> #inclu
Hi Tetsuo,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19 next-20181102]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
On Thu, 1 Nov 2018, Linus Torvalds wrote:
> On Fri, Oct 26, 2018 at 2:36 AM James Morris wrote:
> >
> > From David: "Provide five new operations in the key_type struct that can
> > be used to provide access to asymmetric key operations. These will be
> > implemented for the asymmetric key type i
On Fri, Nov 2, 2018 at 6:11 AM Ayman Bagabas wrote:
>
> This driver adds support for missing hotkeys on some Huawei laptops.
> Currently, only Huawei Matebook X Pro is supported. The driver
> recognizes the following keys: brightness keys, micmute, wlan, and
> Huawei special key. The brightness ke
On Fri, Nov 2, 2018 at 3:57 AM Borislav Petkov wrote:
>
> here's the second part of the EDAC pile which contains the ADXL user
> and a build fix which addresses a not-so-sensical .config but fixes
> randconfig builds people do.
Pulled,
Linus
On Fri, Nov 2, 2018 at 6:24 AM Thierry Reding wrote:
>
> This series contains a number of improvements to existing drivers, such
> as LPSS. Some drivers, such as renesas-tpu and rcar get support for more
> SoC generations. To round things off this fixes an issue with the sysfs
> interface.
Pulled
On Thu, Nov 01, 2018 at 04:51:54PM -0700, Kees Cook wrote:
> The pre-allocated compression buffer used for crash dumping was also
> being used for decompression. This isn't technically safe, since it's
> possible the kernel may attempt a crashdump while pstore is populating the
> pstore filesystem
On Fri, Nov 02, 2018 at 10:48:38AM -0700, Andy Lutomirski wrote:
> On Fri, Nov 2, 2018 at 10:33 AM Sean Christopherson
> wrote:
> >
> > On Fri, Nov 02, 2018 at 10:13:23AM -0700, Dave Hansen wrote:
> > > On 11/2/18 10:06 AM, Sean Christopherson wrote:
> > > > On Fri, Nov 02, 2018 at 09:56:44AM -070
On Fri, Nov 2, 2018 at 12:29 PM Rajneesh Bhardwaj
wrote:
>
> This adds support to show the Latency Tolerance Reporting for the IPs on
> the PCH as reported by the PMC. The format shown here is raw LTR data
> payload that can further be decoded as per the PCI specification.
>
> This also fixes some
On Fri, Nov 2, 2018 at 12:29 PM Rajneesh Bhardwaj
wrote:
>
> Cannonlake PCH allows us to ignore LTR from more IPs than Sunrisepoint
> PCH so make the LTR ignore platform specific.
>
This one fine, thanks!
> Signed-off-by: Rajneesh Bhardwaj
> ---
> drivers/platform/x86/intel_pmc_core.c | 4 +++-
On Thu, Nov 1, 2018 at 11:22 PM John Johansen
wrote:
>
> Please pull these apparmor changes for v4.20.
Pulled. Although I really wish these had come in earlier (like the
other security layer pulls did)
Linus
On 2 November 2018 at 18:40, Catalin Marinas wrote:
> On Tue, Oct 30, 2018 at 11:10:51AM -0300, Ard Biesheuvel wrote:
>> On 30 October 2018 at 08:49, Ard Biesheuvel
>> wrote:
>> >> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
>> >>
>> >> Commit 1404d6f13e47 ("arm64: dump: Add checking for wri
On Fri, Nov 02, 2018 at 08:56:37PM +0530, Brajeswar Ghosh wrote:
> Remove asm/xchg.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
> ---
> arch/alpha/include/asm/cmpxchg.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/alpha/include/asm/cmpxchg.h
> b/arch/al
On Fri, 02 Nov 2018 19:12:44 +0100,
Andy Shevchenko wrote:
>
> > + if (action == HDA_FIXUP_ACT_PROBE) {
> > + if (!huawei_wmi_micmute_led_set_func)
> > + huawei_wmi_micmute_led_set_func =
> > symbol_request(huawei_wmi_micmute_led_set);
> > +
On Thu, Nov 01, 2018 at 04:51:59PM -0700, Kees Cook wrote:
> Since commit 70ad35db3321 ("pstore: Convert console write to use
> ->write_buf"), the console writer does not use the preallocated crash
> dump buffer any more, so there is no reason to perform locking around it.
Out of curiosity, what w
Sure! It needs a new QEMU driver (vhost-blk-pci), I'm preparing it to
be sent out.
On Fri, Nov 2, 2018 at 2:26 PM Michael S. Tsirkin wrote:
>
> On Fri, Nov 02, 2018 at 06:21:22PM +, Vitaly Mayatskikh wrote:
> > vhost_blk is a host-side kernel mode accelerator for virtio-blk. The
> > driver all
On Fri, Nov 2, 2018 at 12:37 PM Rajneesh Bhardwaj
wrote:
>
> The LTR values follow PCIE LTR encoding format and can be decoded as per
> https://pcisig.com/sites/default/files/specification_documents/ECN_LatencyTolnReporting_14Aug08.pdf
>
> This adds support to translate the raw LTR values as read
On Fri, Nov 2, 2018 at 8:30 PM Takashi Iwai wrote:
> On Fri, 02 Nov 2018 19:12:44 +0100,
> Andy Shevchenko wrote:
> >
> > > + if (action == HDA_FIXUP_ACT_PROBE) {
> > > + if (!huawei_wmi_micmute_led_set_func)
> > > + huawei_wmi_micmute_led_set_func =
> >
We need to enable runtime PM on this i2c controller before populating
child devices with i2c_add_adapter(). Otherwise, if a child device uses
runtime PM and stays runtime PM enabled we'll get the following warning
at boot.
Enabling runtime PM for inactive device (a98000.i2c) with active children
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 4ed591c8ab44e711e56b8e021ffaf4f407c045f5 ]
The intent of ip6_route_check_nh_onlink is to make sure the gateway
given for an onlink route is not actually on a conn
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit 649f0837a8cc2b39329f2de00fa0d04b029291c5 ]
It was reported that WoL from S5 is broken (WoL from S3 works) and the
analysis showed that during system shutdown
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
[ Upstream commit 7de414a9dd91426318df7b63da024b2b07e53df5 ]
Most callers of pskb_trim_rcsum() simply drop the skb when
it fails, however, ip_check_defrag() still continues to pass
t
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commti ece23711dd956cd5053c9cb03e9fe0668f9c8894 ]
Just like with normal GRO processing, we have to initialize
skb->next to NULL when we unlink overflow packets fro
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Hangbin Liu
[ Upstream commit 5a2de63fd1a59c30c02526d427bc014b98adf508 ]
Based on RFC 4541, 2.1.1. IGMP Forwarding Rules
The switch supporting IGMP snooping must maintain a list of
multi
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Petr Machata
[ Upstream commit ad0b9d94182be8356978d220c82f9837cffeb7a9 ]
Demands to remove FDB entries should be honored even if the FDB entry in
question was originally learned, and not adde
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit d48051c5b8376038c2b287c3b1bd55b8d391d567 ]
As shown by Dmitris, we need to use csum_block_add() instead of csum_add()
when adding the FCS contribution to skb csu
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Jakub Kicinski
[ Upstream commit 38b4f18d56372e1e21771ab7b0357b853330186c ]
gred_change_table_def() takes a pointer to TCA_GRED_DPS attribute,
and expects it will be able to interpret its cont
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Tranchetti
[ Upstream commit db4f1be3ca9b0ef7330763d07bf4ace83ad6f913 ]
Current handling of CHECKSUM_COMPLETE packets by the UDP stack is
incorrect for any packet that has an incorrect ch
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Shalom Toledo
[ Upstream commit a22712a962912faf257e857ab6857f56a93cfb34 ]
After a failed reload, the driver is still registered to devlink, its
devlink instance is still allocated and the 're
On Fri, Nov 02, 2018 at 06:21:23PM +, Vitaly Mayatskikh wrote:
> This driver accelerates host side of virtio-blk.
>
> Signed-off-by: Vitaly Mayatskikh
> ---
> drivers/vhost/Kconfig | 13 ++
> drivers/vhost/Makefile | 3 +
> drivers/vhost/blk.c| 510 +++
This is the start of the stable review cycle for the 4.19.1 release.
There are 24 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Nov 4 18:28:10 UTC 2018.
Anything receive
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Niklas Cassel
[ Upstream commit 30549aab146ccb1275230c3b4b4bc6b4181fd54e ]
When building stmmac, it is only possible to select CONFIG_DWMAC_GENERIC,
or any of the glue drivers, when CONFIG_STM
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Stefano Brivio
[ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ]
Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base
timestamp") introduces a neighbour control buf
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 2b4792eaa9f553764047d157365ed8b7787751a3 ]
Some drivers reference it via node_distance(), for example the
NVME host driver core.
ERROR: "__node_distance" [
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit ff002269a4ee9c769dbf9365acef633ebcbd6cbe ]
The idx in vhost_vring_ioctl() was controlled by userspace, hence a
potential exploitation of the Spectre variant 1 vuln
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 713358369382cebf92f6e98ce2005f94e7344931 ]
When getting pr_assocstatus and pr_streamstatus by sctp_getsockopt,
it doesn't correctly process the case when policy is s
201 - 300 of 798 matches
Mail list logo
