The patch
ASoC: rt5651: Enable jack detection on JD* pins
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
ASoC: pfuze100: Remove leading zero from '@08' notation
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: rt5651: Enable jack detection on JD* pins
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
On Thu, 2017-10-26 at 15:42 +0800, joeyli wrote:
> Hi Mimi,
>
> Thank you for reviewing.
>
> On Mon, Oct 23, 2017 at 11:54:43AM -0400, Mimi Zohar wrote:
> > On Thu, 2017-10-19 at 15:51 +0100, David Howells wrote:
> > > From: Chun-Yi Lee
> > >
> > > When KEXEC_VERIFY_SIG is not enabled, kernel s
The patch
ASoC: intel: byt: Add headset jack
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus duri
On Thu 26-10-17 01:41:26, Du, Fan wrote:
>
>
> >-Original Message-
> >From: Michal Hocko [mailto:mho...@kernel.org]
> >Sent: Wednesday, October 25, 2017 5:29 PM
> >To: Du, Fan
> >Cc: a...@linux-foundation.org; h...@lst.de; Williams, Dan J
> >; Hansen, Dave ;
> >linux-kernel@vger.kernel.o
On Thu, Oct 26, 2017 at 12:17 PM, Mark Brown wrote:
> The patch
>
>ASoC: pfuze100: Remove leading zero from '@08' notation
This should be 'regulator: pfuze100' instead.
Hi
On 10/25/2017 09:50 PM, Shikhar Dogra wrote:
The values are already configurable from ACPI.
This patch makes the high count (HCNT) and low count (LCNT)
register values configurable through device tree.
Cc: xe-linux-exter...@cisco.com
Signed-off-by: Shikhar Dogra
---
Documentation/devicet
On Thu, Oct 26, 2017 at 3:45 PM, Paolo Bonzini wrote:
> On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region
> taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86)
> or KVM_GET/SET_ONE_REG (ARM/s390). Without whitelisting the area,
> KVM is completely broken on those archit
f2fs_balance_fs only actives once in the commit_inmem_pages, but there
are more than one page to commit, so all the other pages will miss the
check. This will lead to out-of-free problem when commit a very large
file. To fix it, we should do f2fs_balance_fs for each inmem page.
Signed-off-by: Yunl
On Mon, Oct 23, 2017 at 04:55:19PM -0500, Brijesh Singh wrote:
> The SEV_PEK_GEN command is used to generate a new Platform Endorsement
> Key (PEK). The command is defined in SEV spec section 5.6.
>
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Borislav Petkov
> Cc: Herbert Xu
> Cc: Gary Hook
Hi tglx,
Forgot to mention, we are using kernel stable version 3.18
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/kernel/time/timekeeping.c?h=v3.18.77
wall time is being set to a value close to epoch
but less than epoch + current uptime.
Looks like
https://git.ke
On 10/26/2017 07:16 AM, Michal Hocko wrote:
>> The original motivation was for DAX. They have parallel large page
>> infrastructure separate from hugetlbfs and THP. Their constraints about
>> when they can use large pages differ from the normal mm cases, so it is
>> hard to tell when large pages
From: Markus Elfring
Date: Thu, 26 Oct 2017 16:10:46 +0200
Adjust jump targets so that a call of the function "mutex_unlock" is stored
at the end of this function implementation.
Replace three calls by goto statements.
This issue was detected by using the Coccinelle software.
Signed-off-by: Mar
On 10/25/2017 12:18 PM, Kees Cook wrote:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Herbert Xu
Cc: Jesper Nilsson
Cc: Lars Persson
Cc: Nikla
On Thu, Oct 26, 2017 at 3:49 PM, Adrian Hunter wrote:
> On 26/10/17 16:32, Linus Walleij wrote:
>> My patch series switches the stack around to make it possible
>> to do this. But it doesn't go the whole way to complete the requests
>> from interrupt context.
>>
>> Since we have to send commands
On Sun, Oct 22, 2017 at 05:24:51PM -0700, David Rientjes wrote:
> On Thu, 19 Oct 2017, Johannes Weiner wrote:
>
> > David would have really liked for this patchset to include knobs to
> > influence how the algorithm picks cgroup victims. The rest of us
> > agreed that this is beyond the scope of t
On 10/26/2017 07:19 AM, Michal Hocko wrote:
>> Current vm_normal_page implementation doesn't pick up page with DEVMAP pfn.
>> The second patch fix this and export DAX mappings into counters introduced
>> in the
>> first patch.
>>
>> IMO, the user care more about how much persistent memory they use
On Thu, Oct 26, 2017 at 07:13:32AM -0700, Dave Hansen wrote:
> I kinda appreciate the verbosity. When I see a jump to such a label, I
Sorry but this and other labels' names are just ridiculously long.
swapgs_restore_regs_return or swapgs_restore or somesuch are perfectly
fine.
--
Regards/Gruss,
On 10/26, Yunlong Song wrote:
> f2fs_balance_fs only actives once in the commit_inmem_pages, but there
> are more than one page to commit, so all the other pages will miss the
> check. This will lead to out-of-free problem when commit a very large
> file. To fix it, we should do f2fs_balance_fs for
On Thu 26-10-17 07:24:14, Dave Hansen wrote:
> On 10/26/2017 07:16 AM, Michal Hocko wrote:
> >> The original motivation was for DAX. They have parallel large page
> >> infrastructure separate from hugetlbfs and THP. Their constraints about
> >> when they can use large pages differ from the normal
On Wed, Oct 25, 2017 at 03:49:21PM -0700, Greg Thelen wrote:
> Johannes Weiner wrote:
>
> > On Wed, Oct 25, 2017 at 09:00:57PM +0200, Michal Hocko wrote:
> >> On Wed 25-10-17 14:11:06, Johannes Weiner wrote:
> >> > "Safe" is a vague term, and it doesn't make much sense to me in this
> >> > situat
> I can reproduce this problem on CentOS now. It seems better to leave this
> problem to drivers, not the user process.
> Do you think we should examine serial drivers of ARM, like pl011?
Can you reproduce it on real hardware - I ask because the driver has been
around for years without reports an
Hello,
On Wed, Oct 25, 2017 at 02:54:23PM -0700, Matthias Kaehlcke wrote:
> From your earlier comment I understand that there is no problem in
> this case because we know that cgroup_root->cgrp will always be
> empty.
>
> However in other instances the warning could point out actual errors
> in t
On some integrations of the Intel(R) Trace Hub (for a reference and
overview see Documentation/trace/intel_th.txt) the reported size of
one of its resources (RTIT_BAR) doesn't match its actual size, which
leads to overlaps with other devices' resources.
On a Denverton platform it overlaps with XHC
On Thu, Oct 26 2017 at 3:45:46 pm BST, Paolo Bonzini
wrote:
> On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region
> taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86)
> or KVM_GET/SET_ONE_REG (ARM/s390). Without whitelisting the area,
> KVM is completely broken on thos
Hi Ludovic,
On 25/10/17 18:10, Ludovic Barre wrote:
From: Ludovic Barre
-Prepare to manage multi-bank of external interrupts
(N banks of 32 inputs).
-Prepare to manage registers offsets by compatible
(registers offsets could be different follow per stm32 platform).
Signed-off-by: Ludovic Barr
On Thu, Oct 26, 2017 at 11:00:49AM +0200, Egil Hjelmeland wrote:
> When CPU transmit directly to port using tag, the LAN9303 does not
> learn MAC addresses received on the CPU port into the ALR.
> ALR learning is performed only when transmitting using ALR lookup.
>
> Solution:
> If the two externa
On Thu, Oct 26, 2017 at 08:28:59PM +0900, Tetsuo Handa wrote:
> [...] it is possible to trigger OOM lockup and/or soft lockups when
> many threads concurrently called warn_alloc() (in order to warn
> about memory allocation stalls) due to current implementation of
> printk(), and it is difficult to
Hello, Waiman.
On Wed, Oct 25, 2017 at 11:50:34AM -0400, Waiman Long wrote:
> Ping! Any comment on this patch?
Sorry about the lack of response. Here are my two thoughts.
1. I'm not really sure about the memory part. Mostly because of the
way it's configured and enforced is completely out o
On Thu, 26 Oct 2017 20:11:25 +0800
Zhou Chengming wrote:
> Old code use check_kprobe_rereg() to check if the kprobe has been
> registered already, but check_kprobe_rereg() will release the
> kprobe_mutex then, so maybe two paths will pass the check and
> register the same kprobe. This patch put t
On Thu, Oct 26, 2017 at 09:37:52AM +0200, Ingo Molnar wrote:
>
> * Kirill A. Shutemov wrote:
>
> > On Tue, Oct 24, 2017 at 02:47:41PM +0200, Ingo Molnar wrote:
> > > > > > > > > Making a variable that 'looks' like a constant macro dynamic
> > > > > > > > > in a rare Kconfig
> > > > > > > > > s
* Jeffy Chen [171026 06:31]:
> Add pci-of.c to handle the PCIe WAKE# interrupt.
>
> Also use the dedicated wakeirq infrastructure to simplify it.
>
> Signed-off-by: Jeffy Chen
Thanks for doing this, looks good to me from wakeirq point of view:
Acked-by: Tony Lindgren
On 10/26, Chao Yu wrote:
> On 2017/10/26 17:07, Jaegeuk Kim wrote:
> > On 10/26, Chao Yu wrote:
> >> From: Yunlong Song
> >>
> >> It supports to extend reserved_blocks sysfs interface to be soft
> >> threshold, which allows user configure it exceeding current available
> >> user space.
> >
> > So
Hi Jose,
> -Original Message-
> From: Jose Abreu [mailto:jose.ab...@synopsys.com]
> Sent: Thursday, October 26, 2017 5:19 PM
> To: Bhadram Varka ; net...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Cc: Joao Pinto ; David S. Miller
> ; Giuseppe Cavallaro ;
> Alexandre Torgue
> Subjec
On Thu, 2017-10-26 at 20:37 +1100, Tobin C. Harding wrote:
> On Thu, Oct 26, 2017 at 01:05:39AM -0700, Joe Perches wrote:
> > On Thu, 2017-10-26 at 17:27 +1100, Tobin C. Harding wrote:
> > > Hi Joe,
> > >
> > > thanks for your review.
> > >
> > > On Wed, Oct 25, 2017 at 09:57:23PM -0700, Joe Perc
On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
> Hi all,
>
> I am failed to reproduce it on target kernel with the reproducer file
> or replaying the target syzkaller description log file, do I made
> something wrong or there exists more subjects then the line in
> repro.txt:
>
> #{Threaded:
On 26/10/2017 at 17:07:43 +0300, Dan Carpenter wrote:
> On Thu, Oct 26, 2017 at 03:48:52PM +0200, Alexandre Belloni wrote:
> > On 26/10/2017 at 14:17:30 +0200, SF Markus Elfring wrote:
> > > From: Markus Elfring
> > > Date: Thu, 26 Oct 2017 14:06:49 +0200
> > >
> > > * Add jump targets so that tw
The new bindings (dsa2.c) and the old bindings (legacy.c) share two
helpers dsa_cpu_dsa_setup and dsa_cpu_dsa_destroy, used to register or
deregister a fixed PHY if a given port has a corresponding device node.
Unclutter the code by moving them into two new port.c helpers,
dsa_port_fixed_link_regi
On 10/26/2017 07:31 AM, Michal Hocko wrote:
> On Thu 26-10-17 07:24:14, Dave Hansen wrote:
>> Actually, I don't remember whether it was tooling or just confused
>> humans. I *think* Dan was trying to write test cases for huge page DAX
>> support and couldn't figure out whether or not it was using
On Thu, Oct 26, 2017 at 4:04 PM, Bart Van Assche wrote:
> On Thu, 2017-10-26 at 10:24 +0200, Kees Cook wrote:
>> On Wed, Oct 25, 2017 at 5:03 PM, Bart Van Assche
>> wrote:
>> > On Wed, 2017-10-25 at 16:10 +0200, Kees Cook wrote:
>> > > However, maintainers: sorry to send this one -- it can't be
Mimi Zohar wrote:
> The patch title and description needs to be updated to refer to
> lockdown, not securelevel.
Fixed, thanks.
> An additional patch could force these rules to be added to the custom
> policy, if lockdown is enabled.
I'll have a look at your patch, though at this point I'm lea
On 10/26/2017 03:45 PM, Paolo Bonzini wrote:
> On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region
> taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86)
> or KVM_GET/SET_ONE_REG (ARM/s390). Without whitelisting the area,
> KVM is completely broken on those architectures
On Thu 26-10-17 06:49:00, Yang Shi wrote:
> Per the discussion with David [1], it looks more reasonable to just dump
Please try to avoid external references in the changelog as much as
possible.
> the single excessive slab cache instead of dumping all slab caches when
> oom.
You meant to say
"to
The introduction of {map/swizzle}_irq() hooks in the
struct pci_host_bridge allowed to replace the pci_fixup_irqs()
PCI IRQ allocation in alpha arch PCI code with per-bridge
map/swizzle functions with commit 0e4c2eeb758a ("alpha/PCI: Replace
pci_fixup_irqs() call with host bridge IRQ mapping hooks"
On Thu, 26 Oct 2017 16:06:02 +0200
Jarkko Sakkinen wrote:
> On Thu, Oct 26, 2017 at 02:59:02PM +0200, Michal Suchánek wrote:
> > It does not really matter. People ignore the messages unless looking
> > for something specific as you already noticed. Warn seems adequate
> > because the cipher is we
From: Markus Elfring
Date: Thu, 26 Oct 2017 16:51:08 +0200
Add a jump target so that a call of the function "mutex_unlock" is stored
only once at the end of this function implementation.
Replace two calls by goto statements.
This issue was detected by using the Coccinelle software.
Signed-off-b
On Thu, Oct 26, 2017 at 4:17 AM, David Hildenbrand wrote:
> On 26.10.2017 09:13, Paolo Bonzini wrote:
>> For many years some users of assigned devices have reported worse
>> performance on AMD processors with NPT than on AMD without NPT,
>> Intel or bare metal.
>>
>> The reason turned out to be th
joeyli wrote:
> + if (!IS_ENABLED(CONFIG_KEXEC_VERIFY_SIG) &&
> + !is_ima_appraise_enabled() &&
> + kernel_is_locked_down("kexec of unsigned images"))
This doesn't seem right. It seems that you can then kexec unsigned images
into a locked-down kernel if IMA appraise is enabl
On Thu, Oct 26, 2017 at 04:25:15PM +0800, Chen Feng wrote:
>
>
> On 2017/10/25 16:49, Theodore Ts'o wrote:
> > Other people who have sent me fuzzer test reproducers are able to
> > reproduce syzkaller logs into a simple C program. Can you explain to
> > me what the heck:
> >
> >> r3 = syz_open_
On Thu, 26 Oct 2017, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
What about old Qualcomm SoCs? What should they use instead?
Alan Stern
On Thu 26-10-17 07:51:20, Dave Hansen wrote:
> On 10/26/2017 07:31 AM, Michal Hocko wrote:
> > On Thu 26-10-17 07:24:14, Dave Hansen wrote:
> >> Actually, I don't remember whether it was tooling or just confused
> >> humans. I *think* Dan was trying to write test cases for huge page DAX
> >> suppo
On Thu, Oct 26, 2017 at 01:26:33AM -0700, Andy Lutomirski wrote:
> The only user was the 64-bit opportunistic SYSRET failure path, and
> that path didn't really need it. This change makes the
> opportunistic SYSRET code a bit more straightforward and gets rid of
> the label.
>
> Signed-off-by: An
From: Jiada Wang
register SSI_MODE is set when SSI works in TDM Extended or
TDM (Ex-)Split mode, but it isn't reset after SSI stops.
this will cause issue, if SSI starts to work in other modes
which requie SSI_MODE to have different value.
This patch resets SSI_MODE register in .stop callback,
w
From: Ludovic Barre
When memory-mapped mode is used, a prefetching mechanism fully
managed by the hardware allows to optimize the read from external
the QSPI memory. A 32-bytes FIFO is used for prefetching.
When the limit of flash size - fifo size is reached the prefetching
mechanism tries to rea
From: Ludovic Barre
This series adds:
-Fix: to avoid compilation warning with older compiler
versions such as gcc-4.6.
This topic has been discussed on 2 threads with Geert and Arnd
https://lkml.org/lkml/2017/9/15/70
https://www.spinics.net/lists/arm-kernel/msg606269.html
-Fix: abort prefetching
From: Ludovic Barre
-Change the license text with long template.
-Change Copyright to STMicroelectronics.
Signed-off-by: Ludovic Barre
---
drivers/mtd/spi-nor/stm32-quadspi.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/spi-nor/stm32-quad
From: Geert Uytterhoeven
With gcc 4.1.2:
drivers/mtd/spi-nor/stm32-quadspi.c: In function ‘stm32_qspi_tx_poll’:
drivers/mtd/spi-nor/stm32-quadspi.c:230: warning: ‘ret’ may be used
uninitialized in this function
Indeed, if stm32_qspi_cmd.len is zero, ret will be uninitialized.
This leng
On 10/26/2017 9:28 AM, Jeffy Chen wrote:
> drivers/pci/Makefile | 2 +-
> drivers/pci/pci-of.c | 136
> +++
> 2 files changed, 137 insertions(+), 1 deletion(-)
> create mode 100644 drivers/pci/pci-of.c
>
> diff --git a/drivers/pci/Makefile b/dri
vgic_its_restore_cte returns +1 if the collection table entry
is valid and properly decoded. As a consequence, if the
collection table is fully filled with valid data that are
decoded without error, vgic_its_restore_collection_table()
returns +1. This is wrong.
Let's return 0 in that case.
Fixes:
Most of the DSA code still check ds->enabled_port_mask directly to
inspect a given port type instead of using the provided dsa_is_user_port
helper. Change this.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/bcm_sf2.c | 9 -
drivers/net/dsa/bcm_sf2_cfp.c | 2 +-
drivers/net/dsa/mt
The spec says it is UNPREDICTABLE to enable the ITS
if any of the following conditions are true:
- GITS_CBASER.Valid == 0.
- GITS_BASER.Valid == 0, for any GITS_BASER register
where the Type field indicates Device.
- GITS_BASER.Valid == 0, for any GITS_BASER register
where the Type field indic
From: wanghaibin
If ITT only contains invalid entries, vgic_its_restore_itt
returns 1 and this is considered as an an error in
vgic_its_restore_dte.
Also in case the device table only contains invalid entries,
the table restore fails and this is not correct.
This patch fixes those 2 issues:
- v
At the moment we don't properly check the GITS_BASER.Valid
bit before saving the collection and device tables.
On vgic_its_save_collection_table() we use the GITS_BASER gpa
field whereas the Valid bit should be used.
On vgic_its_save_device_tables() there is no check. This can
cause various bugs,
Let's remove kvm_its_unmap_device and use kvm_its_free_device
as both functions are identical.
Signed-off-by: Eric Auger
Acked-by: Christoffer Dall
---
v5 -> v6:
- Added Christoffer's A-b
v5: creation
---
virt/kvm/arm/vgic/vgic-its.c | 14 ++
1 file changed, 2 insertions(+), 12 de
When the GITS_BASER.Valid gets cleared, the data structures in
guest RAM are not valid anymore. The device, collection
and LPI lists stored in the in-kernel ITS represent the same
information in some form of cache. So let's void the cache.
Signed-off-by: Eric Auger
---
v5 -> v6:
- rename type in
From: wanghaibin
We create two new functions that free the device and
collection lists. They are currently called by vgic_its_destroy()
and other callers will be added in subsequent patches.
We also remove the check on its->device_list.next.
Lists are initialized in vgic_create_its() and the dev
On reset we clear the valid bits of GITS_CBASER and GITS_BASER.
We also clear command queue registers and free the cache (device,
collection, and lpi lists).
As we need to take the same locks as save/restore functions, we
create a vgic_its_ctrl() wrapper that handles KVM_DEV_ARM_VGIC_GRP_CTRL
grou
On Wed, Oct 25, 2017 at 02:07:38PM -0700, Andrei Vagin wrote:
> Hi Josh,
>
> Here is one more warning:
> [5.852094] WARNING: can't dereference iret registers at b6ce01b7ffe0
> for ip entry_SYSCALL_64_fastpath+0xa/0xc2
Thanks, I hadn't seen this one yet.
I suspect this is in the middle o
At the moment, the in-kernel emulated ITS is not properly reset.
On guest restart/reset some registers keep their old values and
internal structures like device, ITE, and collection lists are not
freed.
This may lead to various bugs. Among them, we can have incorrect state
backup or failure when s
From: Willem de Bruijn
> Sent: 25 October 2017 19:50
...
> From skb->dev and netdev_priv, the tun device has flags 0x1002 ==
> IFF_TAP | IFF_NO_PI. This kernel precedes the recent support for
> IFF_NAPI and IFF_NAPI_FRAGS. The allocation most likely happened
> in tun_build_skb from current->task_fr
This patch renames dsa_is_normal_port to dsa_is_user_port because "user"
is the correct term in the DSA terminology, not "normal".
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.c | 2 +-
include/net/dsa.h| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
This series fixes various bugs observed when saving/restoring the
ITS state before the guest writes the ITS registers (on first boot or
after reset/reboot).
This is a follow up of Wanghaibin's series [1] plus additional
patches following additional code review. It also proposes one
ITS reset imple
As the comment above the chunk states, the b53 driver attempts to
disable the unused ports. But using ds->enabled_port_mask is misleading,
because this mask reports in fact the user ports.
To avoid confusion and fix this, this patch introduces an explicit
dsa_is_unused_port helper which ensures th
The unused ports are currently configured in normal mode. This does not
prevent the switch from being functional, but it is unnecessary. Skip
unused ports.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx/chip.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/dsa/mv
Now that DSA core provides port types, there is no need to keep this
information at the switch level. This is a static information that is
part of a DSA core dsa_port structure. Remove them.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 3 ---
net/dsa/dsa2.c| 11 ---
net/dsa
The DSA code currently has 3 bitmaps in the dsa_switch structure:
cpu_port_mask, dsa_port_mask and enabled_port_mask.
They are used to store the type of each switch port. This dates back
from when DSA didn't have a dsa_port structure to hold port-specific
data.
The dsa_switch structure is mainly
Introduce an enumerated type for ports, which will be way more explicit
to identify a port type instead of digging into switch port masks.
A port can be of type CPU, DSA, user, or unused by default. This is a
static parsed information that cannot be changed at runtime.
Signed-off-by: Vivien Didel
Introduce a dsa_user_ports() helper to return the ds->enabled_port_mask
mask which is more explicit. This will also minimize diffs when touching
this internal mask.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mt7530.c| 2 +-
drivers/net/dsa/mv88e6060.c | 5 ++---
drivers/net/dsa/qca8k.
Now that DSA exposes an enumerated type for the ports, we can use them
directly instead of checking bitmaps, which is more consistent.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/include/net
In order to know if a port is of type user, dsa_is_normal_port checks
that the given port is not of type DSA nor CPU. This is not enough
because a port can be unused.
Without the previous fix, this caused the unused mv88e6xxx ports to be
configured in normal mode.
The ds->enabled_port_mask report
On Thu, 19 Oct 2017 15:03:20 +0200,
Olivier Moysan wrote:
>
> Add check on substream validity.
>
> Signed-off-by: Olivier Moysan
> ---
> sound/soc/stm/stm32_sai_sub.c | 12
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/sound/soc/stm/stm32_sai_sub.c b/sound/soc
Thu, Oct 26, 2017 at 05:22:57PM CEST, vivien.dide...@savoirfairelinux.com wrote:
>Introduce an enumerated type for ports, which will be way more explicit
>to identify a port type instead of digging into switch port masks.
>
>A port can be of type CPU, DSA, user, or unused by default. This is a
>sta
Hi Jiri,
Jiri Pirko writes:
>>+ enum {
>>+ DSA_PORT_TYPE_UNUSED = 0,
>>+ DSA_PORT_TYPE_CPU,
>>+ DSA_PORT_TYPE_DSA,
>>+ DSA_PORT_TYPE_USER,
>
> Do you plan to expose this to userspace? How?
No. This is a DSA internal data for the moment.
Than
Juergen Gross:
> Commit 96edd61dcf44362d3ef0bed1a5361e0ac7886a63 ("xen/balloon: don't
> online new memory initially") introduced a regression when booting a
> HVM domain with memory less than mem-max: instead of ballooning down
> immediately the system would try to use the memory up to mem-max
> re
> On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote:
> > On Wed, Oct 25, 2017 at 6:44 AM, Jarkko Sakkinen
> > wrote:
> > > I'm implementing a fix for CVE-2017-15361 that simply blacklists
> > > vulnerable FW versions. I think this is the only responsible action from
> > > my side tha
> On Thu, Oct 26, 2017 at 12:26:10AM +0200, Peter Huewe wrote:
> >
> >
> > Am 25. Oktober 2017 20:53:49 MESZ schrieb Jarkko Sakkinen
> :
> > >On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote:
> > >> On Wed, Oct 25, 2017 at 6:44 AM, Jarkko Sakkinen
> > >> wrote:
> > >> > I'm implemen
[Cc'ing Matthew Garrett]
On Thu, 2017-10-26 at 16:02 +0100, David Howells wrote:
> joeyli wrote:
>
> > + if (!IS_ENABLED(CONFIG_KEXEC_VERIFY_SIG) &&
> > + !is_ima_appraise_enabled() &&
> > + kernel_is_locked_down("kexec of unsigned images"))
>
> This doesn't seem right. It seems
On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
>> Hi all,
>>
>> I am failed to reproduce it on target kernel with the reproducer file
>> or replaying the target syzkaller description log file, do I made
>> something wrong or there exi
> > On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote:
> > > On Wed, Oct 25, 2017 at 6:44 AM, Jarkko Sakkinen
> > > wrote:
> > > > I'm implementing a fix for CVE-2017-15361 that simply blacklists
> > > > vulnerable FW versions. I think this is the only responsible action from
> > > >
On Wed, 25 Oct 2017 18:22:02 +0200
Hans de Goede wrote:
> Hi,
>
> On 25-10-17 18:15, SF Markus Elfring wrote:
> >> IMHO, if you do this, you should rework the function so that there is a
> >> single unlock call
> >> at the end, not a separate one in in error label.
> >
> > Thanks for your up
On Wed, 25 Oct 2017 20:07:48 +0200
SF Markus Elfring wrote:
> > What you are suggesting breaks this pattern
>
> I might be looking for an other balance between involved implementation
> details after your constructive feedback for my first approach
> in this software module.
>
>
> > (not usi
Hi Alexey,
> Gentoo ships 5.4.0 which doesn't inline this code on x86_64 defconfig
> (which has OPTIMIZE_INLINING).
I have not actually marked _find_next_bit() inline, it just turns out
that my compiler inlines it.
I've tried out marking the function inline and OPTIMIZE_INLINING does
not un-inlin
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of AceLan Kao
> Sent: Thursday, October 26, 2017 2:54 AM
> To: Darren Hart ; Andy Shevchenko
> ; linux-kernel@vger.kernel.org; platform-driver-
> x...@vger.
On Tue, Oct 24, 2017 at 9:18 AM, Li Bin wrote:
> When queue_work() is used in irq handler, there is a potential
> case that trigger NULL pointer dereference.
>
> worker_thread()
> |-spin_lock_irq()
> |-process_one_work()
> |-
On Thu, 26 Oct 2017, Andy Lutomirski wrote:
>
> Here's the first "real" version of this series. It's based on Linus'
> tree from a couple days ago.
Not seeing any problems in this series. I was hoping it would remove more
lines of code than it adds, and it's the reverse, but that seems to be
On Thu, Oct 26, 2017 at 8:07 AM, Michal Hocko wrote:
> On Thu 26-10-17 07:51:20, Dave Hansen wrote:
>> On 10/26/2017 07:31 AM, Michal Hocko wrote:
>> > On Thu 26-10-17 07:24:14, Dave Hansen wrote:
>> >> Actually, I don't remember whether it was tooling or just confused
>> >> humans. I *think* Dan
We've measured that we spend ~0.6% of sys cpu time in cpumask_next_and().
It's essentially a joined iteration in search for a non-zero bit, which
is currently implemented as a lookup join (find a nonzero bit on the
lhs, lookup the rhs to see if it's set there).
Implement a direct join (find a nonz
On Thu, 26 Oct 2017 16:51:13 +0100
Jonathan Cameron wrote:
> On Wed, 25 Oct 2017 18:22:02 +0200
> Hans de Goede wrote:
>
> > Hi,
> >
> > On 25-10-17 18:15, SF Markus Elfring wrote:
> > >> IMHO, if you do this, you should rework the function so that there is a
> > >> single unlock call
> > >
On Thu, Oct 5, 2017 at 10:19 PM, Anup Patel wrote:
> The RPMSG_VIRTIO is now user selectable option so we explicitly
> select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was
> selected by ST_REMOTEPROC=m in multi_v7_defconfig.
>
> Signed-off-by: Anup Patel
> ---
> arch/arm/configs/multi_v7_d
301 - 400 of 742 matches
Mail list logo
