In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Notice that in this particular case I replaced "Fall" with a proper
"fall through" comment, which is what GCC is expecting to find.
Signed-off-by: Gustavo A. R. Silva
---
drivers/watchdo
> -Original Message-
> From: alexander.le...@verizon.com [mailto:alexander.le...@verizon.com]
> Sent: Thursday, November 16, 2017 4:56 PM
> To: Schmauss, Erik
> Cc: Moore, Robert ; linux-kernel@vger.kernel.org;
> sta...@vger.kernel.org; Wysocki, Rafael J
> Subject: RE: [PATCH AUTOSEL fo
On 11/20/2017 05:27 AM, Dou Liyang wrote:
> There are two consumers of apic=: the APIC debug level and the low
> level generic architecture code, but Linux just documented the first
> one.
>
> Append the second description.
>
> Signed-off-by: Dou Liyang
> ---
> Documentation/admin-guide/kernel-
On Fri, 10 Nov 2017, Dave Hansen wrote:
> diff -puN arch/x86/entry/entry_64.S~kaiser-base arch/x86/entry/entry_64.S
> --- a/arch/x86/entry/entry_64.S~kaiser-base 2017-11-10 11:22:09.007244950
> -0800
> +++ b/arch/x86/entry/entry_64.S 2017-11-10 11:22:09.031244950 -0800
> @@ -145,6 +145,16
On Sat, Nov 18, 2017 at 12:09:10PM -0800, Linus Torvalds wrote:
> On Sat, Nov 18, 2017 at 10:37 AM, Linus Torvalds
> wrote:
> >
> > So I note that you seem to use the same summary script that Darren used.
>
> .. oh, and I note a *much* worse issue.
>
> You add new drivers and then default them t
On Fri, 17 Nov 2017 16:13:45 -0500
Tony Krowiak wrote:
> On 11/16/2017 11:47 AM, Cornelia Huck wrote:
> > [Also, is IOMMU_API only needed to satisfy dependencies?]
> Yes, VFIO is dependent upon it.
Ah, my question was more whether we just need to make sure the api is
there, but do not need to
On Mon, Nov 20, 2017 at 11:09:47AM -0600, Jeremy Linton wrote:
> Hi,
>
> On 11/20/2017 11:06 AM, Sudeep Holla wrote:
> >On Thu, Nov 09, 2017 at 03:03:05PM -0600, Jeremy Linton wrote:
> >>Its helpful to be able to lookup the acpi_processor_id
> >>associated with a logical cpu. Provide an arm64
> >>
On Fri, 17 Nov 2017 15:28:16 -0500
Tony Krowiak wrote:
> On 11/17/2017 05:07 AM, Cornelia Huck wrote:
> > On Fri, 17 Nov 2017 08:07:15 +0100
> > Pierre Morel wrote:
> >
> >> On 17/11/2017 00:35, Tony Krowiak wrote:
> >>> On 11/16/2017 03:25 PM, Pierre Morel wrote:
> On 16/11/2017 18:0
This sets up stack switching, including for SYSCALL. I think it's
in decent shape.
Known issues:
- KASAN is likely to be busted. This could be fixed either by teaching
KASAN that cpu_entry_area contains valid stacks (I have no clue how
to go about doing this) or by rigging up the IST entr
- On Nov 17, 2017, at 3:22 PM, Thomas Gleixner t...@linutronix.de wrote:
> On Fri, 17 Nov 2017, Mathieu Desnoyers wrote:
>> - On Nov 17, 2017, at 5:09 AM, Thomas Gleixner t...@linutronix.de wrote:
>> 7) Allow libraries with multi-part algorithms to work on same per-cpu
>>data without a
get_stack_info() doesn't currently know about the SYSENTER stack, so
unwinding will fail if we entered the kernel on the SYSENTER stack
and haven't fully switched off. Teach get_stack_info() about the
SYSENTER stack.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/stacktrace.h | 3 +++
We currently have CPU 0's GDT at the top of the GDT range and
higher-numbered CPUs at lower addreses. This happens because the
fixmap is upside down (index 0 is the top of the fixmap).
Flip it so that GDTs are in ascending order by virtual address.
This will simplify a future patch that will gene
This will simplify future changes that want scratch variables early in
the SYSENTER handler -- they'll be able to spill registers to the
stack. It also lets us get rid of a SWAPGS_UNSAFE_STACK user.
This does not depend on CONFIG_IA32_EMULATION because we'll want the
stack space even without IA32
I'm going to move SYSENTER_stack to the beginning of cpu_tss to help
detect overflow. Before this can happen, I need to fix several code
paths that hardcode assumptions about the old layout.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/desc.h | 2 +-
arch/x86/include/asm/proces
Currently, the GDT is an ad-hoc array of pages, one per CPU, in the
fixmap. Generalize it to be an array of a new struct cpu_entry_area
so that we can cleanly add new things to it.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/desc.h | 9 +
arch/x86/include/asm/fixmap.h | 3
I want SYSENTER_stack to have reliable overflow detection, which
means that it needs to be at the bottom of a page, not the top.
Move it to the beginning of struct tss_struct and page-align it.
Also add an assertion to make sure that the fixed hardware TSS
doesn't cross a page boundary.
Signed-of
We currently special-case stack overflow on the task stack. We're
going to start putting special stacks in the fixmap with a custom
layout, so they'll have guard pages, too. Teach the unwinder to be
able to unwind an overflow of any of the stacks.
Signed-off-by: Andy Lutomirski
---
arch/x86/ke
On 64-bit kernels, we used to assume that TSS.sp0 was the current
top of stack. With the addition of an entry trampoline, this will
no longer be the case. Store the current top of stack in TSS.sp1,
which is otherwise unused but shares the same cacheline.
Signed-off-by: Andy Lutomirski
---
arch
By itself, this is useless. It gives us the ability to run some final
code before exit that cannnot run on the kernel stack. This could
include a CR3 switch a la KAISER or some kernel stack erasing, for
example. (Or even weird things like *changing* which kernel stack
gets used as an ASLR-streng
Hi,
On 11/20/2017 11:06 AM, Sudeep Holla wrote:
On Thu, Nov 09, 2017 at 03:03:05PM -0600, Jeremy Linton wrote:
Its helpful to be able to lookup the acpi_processor_id
associated with a logical cpu. Provide an arm64
helper to do this.
Signed-off-by: Jeremy Linton
---
arch/arm64/include/asm/ac
Historically, IDT entries from usermode have always gone directly
to the running task's kernel stack. Rearrange it so that we enter on
a percpu trampoline stack and then manually switch to the task's stack.
This touches a couple of extra cachelines, but it gives us a chance
to run some code before
I've just updated a linux source tree to the latest version
(probably from Linus's public tree) and then tried to compile
it (for x86_64) using gcc 4.7.3 and binutils 2.32.2 on a
system running Ubuntu 13.10.
While not the newest gcc, it isn't that old.
The linker is reporting that some of the com
That race has been fixed and code cleaned up for a while now.
---
arch/x86/kernel/irq.c | 12
1 file changed, 12 deletions(-)
diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
index 49cfd9fe7589..68e1867cca80 100644
--- a/arch/x86/kernel/irq.c
+++ b/arch/x86/kernel/irq.c
@@
The IST stacks are needed when an IST exception occurs and are
accessed before any kernel code at all runs. Move them into
cpu_entry_area.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/fixmap.h | 10 ++
arch/x86/kernel/cpu/common.c | 40 +--
Handling SYSCALL is tricky: the SYSCALL handler is entered with every
single register (except FLAGS), including RSP, live. It somehow needs
to set RSP to point to a valid stack, which means it needs to save the
user RSP somewhere and find its own stack pointer. The canonical way
to do this is wit
In case something goes wrong with unwind (not unlikely in case of
overflow), print the offending IP where we detected the overflow.
---
arch/x86/kernel/irq_64.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/irq_64.c b/arch/x86/kernel/irq_64.c
index 020efbf
Hi Geert,
Le 20/11/2017 à 09:49, Geert Uytterhoeven a écrit :
> Hi Cyrille,
>
> On Fri, Nov 17, 2017 at 6:36 PM, Cyrille Pitchen
> wrote:
>> sorry but I won't apply this patch.
>>
>> New values for the 'compatible' DT properties should only be added for
>> memory parts not supporting the JEDEC R
When we start using an entry trampoline, a #GP from userspace will
be delivered on the entry stack, not on the task stack. Fix the
espfix64 #DF fixup to set up #GP according to TSS.SP0, rather than
assuming that pt_regs + 1 == SP0. This won't change anything
without an entry stack, but it will ma
This has a secondary purpose: it puts the entry stack into a region
with a well-controlled layout. A subsequent patch will take
advantage of this to streamline the SYSCALL entry code to be able to
find it more easily.
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_32.S | 6 --
"Michael Kerrisk (man-pages)" writes:
> On 08/16/2017 07:14 PM, Eric W. Biederman wrote:
>> Aleksa Sarai writes:
>>
A couple of things to note on the bigger picture.
The glibc library on all distributions has been changed to not have a
setuid binary pt_chown, that uses ptsna
On Thu, Nov 09, 2017 at 03:03:05PM -0600, Jeremy Linton wrote:
> Its helpful to be able to lookup the acpi_processor_id
> associated with a logical cpu. Provide an arm64
> helper to do this.
>
> Signed-off-by: Jeremy Linton
> ---
> arch/arm64/include/asm/acpi.h | 4
> 1 file changed, 4 inse
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Notice that in this particular case I replaced "Fall" with a proper
"fall through" comment, which is what GCC is expecting to find.
Signed-off-by: Gustavo A. R. Silva
---
drivers/watchdo
Hi Yan Zi,
thanks for the feedback. Yes, it looks definitely less redundant :)
Regards,
Andrea
On Mon, Nov 20, 2017 at 11:33:06AM -0500, Zi Yan wrote:
> Hi Andrea,
>
> Thanks for pointing this out.
>
> I think the problem is that we should not prep_transhuge_page(new_page)
> unless new_page is
On Mon, 20 Nov 2017 17:54:27 +0100,
Hans Peter Möller wrote:
>
> Hi, since for Kernel 4.14 the source was changed for the timer issue, I
> need to resend the patches to apply over 4.14 or it's no need for that?
Don't worry, your change was already in Linus tree, included in
4.15-rc1.
Takashi
>
Hi!
On Monday 20 November 2017 16:08:41 Oleksandr Natalenko wrote:
> Hi.
>
> I've got Dell Vostro 3360 with extra multimedia keys as shown here [1], but
> have no luck to get them working.
>
> I've modified dell_wmi_smbios_list structure in drivers/platform/x86/dell-
> wmi.c adding new entry:
>
> I am aware that Edison could run with a modified 4.4 kernel, I just
> don't know where the firmware is. I don't see anything for Merrifield in
> /lib/firmware/intel?
https://downloadmirror.intel.com/25028/eng/edison-image-from-src-package-ww25.5-15.zip
I have no idea why it never made it in
Vitaly Kuznetsov writes:
> But adding such complexity to the code would require a good
> justification, of course.
Sorry for necroposting, I got distracted :-(
I think I was able to reproduce the reported regression. The reproducer
is dead simple, just several threads doing malloc(128Mb)/free()
merged into cifs-2.6.git for-next
On Sun, Nov 5, 2017 at 12:43 AM, Long Li wrote:
> From: Long Li
>
> The upper layer calls this function to connect to peer through SMB Direct.
> Each SMB Direct connection is based on a RDMA RC Queue Pair.
>
> Signed-off-by: Long Li
> ---
> fs/cifs/smbdirect.c
merged into cifs-2.6.git for-next after cleaning up a couple checkpatch warnings
On Mon, Nov 20, 2017 at 1:37 AM, Leif Sahlberg wrote:
> Acked-by: Ronnie Sahlberg
>
>
> - Original Message -
> From: "Long Li"
> To: "Steve French" , linux-c...@vger.kernel.org,
> samba-techni...@lists.sam
Al, thanks for the detailed feedback. I didn't know about these rules
(are they written down somewhere?). I'll rework this and post a
compliant v3.
On Fri, Nov 17, 2017 at 11:31 AM, Al Viro wrote:
> On Thu, Nov 16, 2017 at 09:56:50AM -0800, Todd Kjos wrote:
>
>> +static struct files_struct *binde
On Thu, Nov 09, 2017 at 03:03:07PM -0600, Jeremy Linton wrote:
> The /sys cache entries should support ACPI/PPTT generated cache
> topology information. Lets detect ACPI systems and call
> an arch specific cache_setup_acpi() routine to update the hardware
> probed cache topology.
>
> For arm64, if
On Sun, Nov 19, 2017 at 11:11 AM, Marek Vasut wrote:
> On 11/19/2017 06:38 PM, Gabriele Mazzotta wrote:
>> 2017-11-19 18:03 GMT+01:00 Jonathan Cameron :
>>> On Wed, 15 Nov 2017 20:27:54 -0700
>>> Kiernan Hager wrote:
>>>
This makes acpi-als properly enable the light sensor on the Zenbook
>>
Quoting Mimi Zohar (zo...@linux.vnet.ibm.com):
> On Mon, 2017-11-20 at 10:40 +0100, Roberto Sassu wrote:
> > On 11/19/2017 12:23 AM, Mimi Zohar wrote:
> > > Hi Serge,
> > >
> > > On Fri, 2017-11-17 at 22:20 -0600, Serge E. Hallyn wrote:
> > >> On Tue, Nov 07, 2017 at 11:37:01AM +0100, Roberto Sass
On 20/11/17 16:26, Konrad Rzeszutek Wilk wrote:
On Mon, Nov 20, 2017 at 08:17:14AM +, Eric Yang wrote:
Hi all,
Hi!
During debug a device only support 32bits DMA(Qualcomm Atheros AP) in our LS1043A 64bits ARM SOC, we
found that the invoke of dma_unmap_single --> swiotlb_tbl_unmap_singl
On Mon, Nov 20, 2017 at 8:29 AM, Russell King - ARM Linux
wrote:
> On Mon, Nov 20, 2017 at 09:56:21PM +0530, Arvind Yadav wrote:
>> The platform_get_irq() function returns negative if an error occurs.
>> zero or positive number on success. platform_get_irq() error checking
>> for zero is not corre
> On Nov 20, 2017, at 10:10 AM, Cyril Hrubis wrote:
>
> Hi!
>> So why didn???t we report these? As mentioned we???ve been tossing out dodgy
>> test cases to get to a clean baseline. We don???t need or want noise.
>>
>> For LTS, I want the system when it detects a failure to enable a quick
>>
On Sun, Jun 18, 2017 at 5:36 PM, NeilBrown wrote:
> On Sun, Jun 18 2017, Jens Axboe wrote:
>
>> On Sun, Jun 18 2017, NeilBrown wrote:
>>> This is a resend of my series of patches working
>>> towards removing the bioset work queues.
>>>
>>> This set is based on for-4.13/block.
>>>
>>> It incorporat
On 11/17, Yonghong Song wrote:
>
> On 11/17/17 9:25 AM, Oleg Nesterov wrote:
> >On 11/15, Yonghong Song wrote:
> >>
> >>v3 -> v4:
> >> . Revert most of v3 change as 32bit emulation is not really working
> >> on x86_64 platform as among other issues, function emulate_push_stack()
> >> need
On Mon, 20 Nov 2017 17:29:53 +0100
Romain Perier wrote:
> So even if the correspondong syscall are disabled and the
> corresponding clocks too, you should return an -ENOSYS from the
> do_adjtimex helper, in case that another component tries to use it in
> the kernel, right ?
Probably - but you n
Ulf,
On 11/20/17 06:44, Mark Rutland wrote:
> On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote:
>> adding devicetree list, devicetree maintainers
>>
>> On 11/18/17 12:59, Ulf Samuelsson wrote:
>>> I noticed when checking out the OpenWRT support for the board that they
>>> have a metho
On 11/19/2017 03:00 AM, SF Markus Elfring wrote:
From: Markus Elfring
Date: Sun, 19 Nov 2017 09:53:56 +0100
* Add a jump target so that a specific error message is stored only once
at the end of this function implementation.
* Replace two calls of the function "dev_err" by goto statements
On Fri, Nov 17, 2017 at 07:27:46PM +0800, Boqun Feng wrote:
> On Wed, Nov 15, 2017 at 08:37:49AM -0800, Paul E. McKenney wrote:
> > On Tue, Nov 14, 2017 at 09:15:05AM -0800, Paul E. McKenney wrote:
> > > On Tue, Nov 14, 2017 at 10:19:21AM -0500, Alan Stern wrote:
> > > > On Tue, 14 Nov 2017, Peter
On 11/20/2017 11:07 AM, Christian König wrote:
> Am 20.11.2017 um 16:51 schrieb Boris Ostrovsky:
>>
>> (and then it breaks differently as a Xen guest --- we hung on the last
>> pci_read_config_dword(), I haven't looked at this at all yet)
>
> Hui? How does this fix applies to a Xen guest in the fir
Hi Andrea,
Thanks for pointing this out.
I think the problem is that we should not prep_transhuge_page(new_page)
unless new_page is allocated and PageTransHuge(). And several lines above,
the allocation flags and the order is changed to make new_page a THP
only if thp_migration_supported() is tru
On Mon, Nov 20, 2017 at 2:21 PM, Takashi Iwai wrote:
> On Mon, 20 Nov 2017 13:47:28 +0100,
> Dmitry Vyukov wrote:
>>
>> On Wed, Nov 1, 2017 at 8:49 PM, Takashi Iwai wrote:
>> > On Wed, 01 Nov 2017 19:39:46 +0100,
>> > Dmitry Vyukov wrote:
>> >>
>> >> On Wed, Nov 1, 2017 at 9:38 PM, syzbot
>> >>
On Sun, Nov 19, 2017 at 03:32:08PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.100 release.
> There are 59 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
Hi Steve,
A quick perusal of 4.11.12-rt16 shows that it has an
entirely new version of migrate_disable which to me appears
correct.
In that new implementation, migrate_enable() recalculates
p->nr_cpus_allowed when it switches the task back to
using p->cpus_mask. This brings the two back into sync
So even if the correspondong syscall are disabled and the
corresponding clocks too, you should return an -ENOSYS from the
do_adjtimex helper, in case that another component tries to use it in
the kernel, right ?
Regards,
Romain
2017-11-20 17:08 GMT+01:00 Alan Cox :
> On Mon, 20 Nov 2017 16:22:06
On Mon, Nov 20, 2017 at 09:56:21PM +0530, Arvind Yadav wrote:
> The platform_get_irq() function returns negative if an error occurs.
> zero or positive number on success. platform_get_irq() error checking
> for zero is not correct.
>
> Signed-off-by: Arvind Yadav
> ---
> changes in v2 :
>
The email to Herbert is returned, resent it.
Yang
On 11/17/17 3:02 PM, Yang Shi wrote:
Preempt counter APIs have been split out, currently, hardirq.h just
includes irq_enter/exit APIs which are not used by crypto at all.
So, remove the unused hardirq.h.
Signed-off-by: Yang Shi
Cc: Herbert X
On Mon, Nov 20, 2017 at 08:17:14AM +, Eric Yang wrote:
> Hi all,
Hi!
>
> During debug a device only support 32bits DMA(Qualcomm Atheros AP) in our
> LS1043A 64bits ARM SOC, we found that the invoke of dma_unmap_single -->
> swiotlb_tbl_unmap_single will unmap the passed "size" anyway eve
On 11/18/2017 11:08 AM, Andy Shevchenko wrote:
On Fri, 2017-11-17 at 18:02 -0600, Pierre-Louis Bossart wrote:
Make sure all the configs are aligned
Also add the missing dependencies on SOC_ACPI stuff used to fix
DAI names based on HID.
FIXME: not sure why X86_INTEL_LPSS is needed in a machine
From: Yazen Ghannam
The McaIntrCfg register at MSRC000_0410, previously known as CU_DEFER_ERR,
is used on SMCA systems to set the LVT offset for the Threshold and
Deferred error interrupts.
This register was used on non-SMCA systems to also set the Deferred
interrupt type in bits 2:1. However, t
The platform_get_irq() function returns negative if an error occurs.
zero or positive number on success. platform_get_irq() error checking
for zero is not correct.
Signed-off-by: Arvind Yadav
---
changes in v2 :
Return keypad->irq insted of -ENXIO.
changes in v3 :
Add
Johan Hovold wrote:
> Fix child-node lookup during probe, which ended up searching the whole
> device tree depth-first starting at the parent rather than just matching
> on its children.
>
> To make things worse, the parent mmio node was also prematurely freed.
>
> Fixes: fd52bdae9ab0 ("wcn36xx
Hi Dmitry,
On Sunday 19 November 2017 12:00 AM, Dmitry Torokhov wrote:
On Sat, Nov 18, 2017 at 04:25:08PM +0530, Arvind Yadav wrote:
The platform_get_irq() function returns negative if an error occurs.
zero or positive number on success. platform_get_irq() error checking
for zero is not correct
On Mon, Nov 20, 2017 at 03:48:18PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Nov 20, 2017 at 06:06:57AM -0800, Guenter Roeck wrote:
> > On 11/19/2017 06:29 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.18.83 release.
> > > There are 38 patches in this s
On 11/18/2017 10:53 AM, Andy Shevchenko wrote:
On Fri, 2017-11-17 at 18:01 -0600, Pierre-Louis Bossart wrote:
PCI/ACPI selections should not happen in Kconfig for machine drivers,
move to SOC selections.
Add distinction between PCI and ACPI HiFi2 platforms.
The PCI-based
platforms may be
> On Nov 19, 2017, at 5:20 AM, Greg Kroah-Hartman
> wrote:
>
> On Thu, Nov 16, 2017 at 10:50:23PM -0600, Tom Gall wrote:
>> At Linaro we’ve been putting effort into regularly running kernel tests over
>> arm, arm64 and x86_64 targets. On those targets we’re running mainline,
>> -next,
>> 4.4
2017-11-17 2:01 GMT+09:00 Knut Omang :
> Add interpretation of a new environment variable P={1,2} in spirit of the
> C= option, but executing checkpatch instead of sparse.
>
> Signed-off-by: Knut Omang
> Reviewed-by: Håkon Bugge
> Acked-by: Åsmund Østvold
> ---
> Makefile | 20 +++
new_page_nodemask in linux/migrate.h should not call prep_transhuge_page
if thp_migration_support is false.
Fixes commit 8135d8926c08 ("mm: memory_hotplug: memory hotremove supports
thp migration")
Signed-off-by: Andrea Reale
---
include/linux/migrate.h | 2 +-
1 file changed, 1 insertion(+), 1
On 11/18/2017 10:49 AM, Takashi Iwai wrote:
On Sat, 18 Nov 2017 01:01:56 +0100,
Pierre-Louis Bossart wrote:
+if SND_SOC_INTEL_BAYTRAIL
config SND_SOC_INTEL_BYT_MAX98090_MACH
tristate "ASoC Audio driver for Intel Baytrail with MAX98090 codec"
+ default n
default=n is superf
Hi all,
While working on a second round of patches to introduce memory hotplug /
hot remove to arm64 (original attempt at [1]), and trying to rebase them
on 4.14, I stumbled in some problematic behaviour during page migration
when offlining for hot remove, whereas target pages for migration where
The cros_ec_dev module is responsible for registering the MFD devices
attached to the ChromeOS EC. This patch moves this module to drivers/mfd
so calls to mfd_add_devices() are not done from outside the MFD subtree
anymore.
Signed-off-by: Thierry Escande
---
drivers/mfd/Kconfig
This patch splits the cros_ec_devs module in two parts with a
cros_ec_dev module responsible for handling MFD devices registration and
a cros_ec_ctl module responsible for handling the various user-space
interfaces.
For consistency purpose, the driver name for the cros_ec_dev module is
now cros-ec
Hi,
In order to remove calls to mfd_add_devices() from outside the MFD
subtree, this patchset splits the cros_ec_devs modules in 2 parts. The
cros_ec_dev module, responsible for registering mfd devices, will be
moved to the MFD subtree (drivers/mfd/) and the user-space interfaces,
named cros_ec_ct
> -Original Message-
> From: Javier Martinez Canillas [mailto:javi...@redhat.com]
> Sent: Monday, November 20, 2017 1:26 AM
> To: Jason Gunthorpe
> Cc: Roberts, William C ; linux-
> ker...@vger.kernel.org; Jarkko Sakkinen ;
> Peter Huewe ; Tricca, Philip B
> ; linux-integr...@vger.kernel
- On Nov 16, 2017, at 6:26 PM, Thomas Gleixner t...@linutronix.de wrote:
> On Tue, 14 Nov 2017, Mathieu Desnoyers wrote:
>> +#ifdef __KERNEL__
>> +# include
>> +#else /* #ifdef __KERNEL__ */
>
> Sigh.
fixed.
>
>> +# include
>> +#endif /* #else #ifdef __KERNEL_
From: Colin Ian King
The assignment of dst_local to itself is redundant and can be removed.
Signed-off-by: Colin Ian King
---
drivers/misc/mic/scif/scif_dma.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/misc/mic/scif/scif_dma.c b/drivers/misc/mic/scif/scif_dma.c
index 63d6246d6d
Hi!
> So why didn???t we report these? As mentioned we???ve been tossing out dodgy
> test cases to get to a clean baseline. We don???t need or want noise.
>
> For LTS, I want the system when it detects a failure to enable a quick
> bisect involving the affected test bucket. Given the nature of k
On Thu, Nov 16, 2017 at 01:44:00PM -0700, Jason Gunthorpe wrote:
> As was discussed in September and October, add Jason along with
> Doug to have a team maintainership model for the RDMA subystem.
>
> Mellanox Technologies will be funding Jason's independent work on
> the maintainership.
>
> Signed
On Mon, 20 Nov 2017 16:22:06 +0100
peter enderborg wrote:
> On 11/20/2017 04:00 PM, Romain Perier wrote:
> > Hi,
> >
> > 2017-11-20 15:10 GMT+01:00 peter enderborg :
> >> I think it should return a error code at least.
> > In which case ? The idea was to don't change the behaviour of these
>
Am 20.11.2017 um 16:51 schrieb Boris Ostrovsky:
On 10/18/2017 09:58 AM, Christian König wrote:
From: Christian König
Most BIOS don't enable this because of compatibility reasons.
Manually enable a 64bit BAR of 64GB size so that we have
enough room for PCI devices.
v2: style cleanups, increas
On Mon, Nov 20, 2017 at 4:47 PM, John Johansen
wrote:
> On 11/20/2017 06:00 AM, Arnd Bergmann wrote:
>> On Mon, Sep 25, 2017 at 4:29 PM, John Johansen
>> wrote:
>>> On 09/15/2017 03:55 PM, Arnd Bergmann wrote:
gcc-4.4 points out suspicious code in compute_mnt_perms, where
the aa_perms s
On Mon 20-11-17 14:24:44, Will Deacon wrote:
> On Thu, Nov 16, 2017 at 10:20:42AM +0100, Michal Hocko wrote:
> > On Wed 15-11-17 17:33:32, Will Deacon wrote:
[...]
> > > > diff --git a/arch/arm64/include/asm/tlb.h b/arch/arm64/include/asm/tlb.h
> > > > index ffdaea7954bb..7adde19b2bcc 100644
> > >
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, November 17, 2017 2:39 PM
> To: Limonciello, Mario
> Cc: Andy Shevchenko ; LKML ker...@vger.kernel.org>; platform-driver-...@vger.kernel.org
> Subject: Re: [PATCH v2] platform/x86: dell-smbios-wmi: Disa
"Michael Kerrisk (man-pages)" writes:
> Hi Serge,
>
> At the moment man-pages lacks documentation of the namespaced file
> capability feature that you added with commit
> 8db6c34f1dbc8e06aa016a9b829b06902c3e1340. Would you be able to send a
> patch describing the feature?
>
> Presumably, the patc
> > Yes it is.
> >
> > It's for the complete sampling period because it is computed
> > over the delta from the last sample to the previous sample.
> >
> > There isn't really a metric at a point, it is always over a interval.
>
> agreed, it's the count we meassured from the last sample.. but the
Hi,
On Monday 20 November 2017 07:07 PM, Alexandre Belloni wrote:
On 19/11/2017 at 09:45:00 +0530, Arvind Yadav wrote:
The platform_get_irq() function returns negative if an error occurs.
zero or positive number on success. platform_get_irq() error checking
for zero is not correct.
Signed-off-
On Fri, Nov 10, 2017 at 8:30 PM, Dave Hansen
wrote:
> Thanks, everyone for all the reviews thus far. I hope I managed to
> address all the feedback given so far, except for the TODOs of
> course. This is a pretty minor update compared to v1->v2.
>
> These patches are all on top of Andy's entry c
On Wed, 15 Nov 2017, Miroslav Benes wrote:
> If a task sleeps in a set of patched functions uninterruptedly, it could
> block the whole transition indefinitely. Thus it may be useful to clear
> its TIF_PATCH_PENDING to allow the process to finish.
>
> Admin can do that now by writing to force sy
Hi,
Sorry for the late reply.
On Tue, Nov 07, 2017 at 08:50:53PM +0800, Huang Rui wrote:
> On Fri, Nov 03, 2017 at 11:33:56AM +, Mark Rutland wrote:
> > As a heads-up, I believe that arch/x86/events/amd/power.c is currently
> > missing initialisation of pmu::module, which could result in prob
2017-11-20 7:27 GMT+09:00 Pavel Machek :
> Hi!
>
> I'm getting quite a lot of perl warnings in v4.15-rc0.
>
> Any ideas what is going on there?
Sorry, I have no idea.
What I can tell is, the Kbuild pull requests in this MW
did not touch any perl scripts.
>
>
On Mon, Nov 20, 2017 at 07:35:05AM -0800, Andi Kleen wrote:
> On Mon, Nov 20, 2017 at 10:04:19AM +0100, Jiri Olsa wrote:
> > On Fri, Nov 17, 2017 at 01:43:00PM -0800, Andi Kleen wrote:
> >
> > SNIP
> >
> > > ---
> > > tools/perf/Documentation/perf-script.txt | 10 +++-
> > > tools/perf/builtin-s
On 10/18/2017 09:58 AM, Christian König wrote:
> From: Christian König
>
> Most BIOS don't enable this because of compatibility reasons.
>
> Manually enable a 64bit BAR of 64GB size so that we have
> enough room for PCI devices.
>
> v2: style cleanups, increase size, add resource name, set correct
> > Hi Jiri,
> >
> > This patch set is based on the latest perf/core branch.
> >
> > I pull the branch right now and try the build again, the building is OK.
> >
> > Could you tell me which branch you are testing on?
>
> ugh.. I was over Andi's changes.. I'll recheck
Yes the two patch kits con
Hi Linus,
2017-11-20 3:02 GMT+09:00 Linus Torvalds :
> On Sun, Nov 19, 2017 at 2:40 AM, Masahiro Yamada
> wrote:
>>>
>>> FWIW, I still think we should probably make the compiler versions etc
>>> available to the configuration management rather than necessarily
>>> cache them.
>>
>> Do you mean s
This macro `task_css_set` verifies that the caller is
inside proper critical section if the kernel set CONFIG_PROVE_RCU=y.
Signed-off-by: Wang Long
---
kernel/cgroup/debug.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/cgroup/debug.c b/kernel/cgroup/debug.c
inde
On 11/20/2017 06:00 AM, Arnd Bergmann wrote:
> On Mon, Sep 25, 2017 at 4:29 PM, John Johansen
> wrote:
>> On 09/15/2017 03:55 PM, Arnd Bergmann wrote:
>>> gcc-4.4 points out suspicious code in compute_mnt_perms, where
>>> the aa_perms structure is only partially initialized before getting
>>> retu
On Mon, Nov 20, 2017 at 04:30:13PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 20 Nov 2017 15:55:25 +0100
>
> Duplicate error messages were used so far in this function implementation.
> Make them unique instead.
>
> This issue was detected by using the Coccinelle softwar
501 - 600 of 892 matches
Mail list logo
