Hi,
Some more info on chained irq vs mux below that might
help.
* Tony Lindgren [190219 15:36]:
> * Lokesh Vutla [190219 08:51]:
> > With this can you tell me how can we not have a device-tree and still
> > support
> > irq allocation?
>
> Using standard dts reg property to differentiate the
On Wed, Feb 20, 2019 at 09:15:50AM +0100, Christian Hohnstaedt wrote:
> - Fix list of valid LS3 currents from mA to µA
> - Fix selection of min/max microAmps of LS3.
> Selecting one of the configured values as max value now really
> selects it instead of the next lower one
This is two
On Tue, Feb 19, 2019 at 11:08:23PM -0500, Joel Fernandes (Google) wrote:
> From: Joel Fernandes
>
> rtnl_register_internal() and rtnl_unregister_all tries to directly
> dereference an RCU protected pointed outside RCU read side section.
> While this is Ok to do since a lock is held, let us use
On Mon, 18 Feb 2019 15:03:18 +0100
Patrick Havelange wrote:
> This driver exposes the counter for the quadrature decoder of the
> FlexTimer Module, present in the LS1021A soc.
>
> Signed-off-by: Patrick Havelange
> Reviewed-by: Esben Haabendal
Given you cc'd William, I'm guessing you know
Hi,
On 2/19/19 9:20 PM, Yauhen Kharuzhy wrote:
On Tue, Feb 19, 2019 at 02:39:55PM +0100, Hans de Goede wrote:
I also wonder if you've considered just disabling the extcon driver
for the PMIC leaving it in automatic mode. Unlike the GPD win / pocket
with their Type-C connector, your device
rmi4 got spam data after S3 resume on some ThinkPads.
Then TrackPoint lost when be detected by psmouse.
Clear irqs status before set irqs will make TrackPoint back.
BugLink: https://bugs.launchpad.net/bugs/1791427
Cc:
Signed-off-by: Aaron Ma
---
drivers/input/rmi4/rmi_driver.c | 11 +++
Some of ThinkPad X1C6 touchpads didn't wakeup after resume.
Forcing enable nosleep make touchpad back.
Add nosleep via sysfs, so user can control it to workaround issue.
/sys/devices/rmi4-00/nosleep can be written non-zero will enable
nosleep mode.
BugLink:
On Thu, 21 Feb 2019 01:04:53 +0900
Masami Hiramatsu wrote:
> > What about just adding 'u' to the end of the offset? Say you have a
> > data structure in kernel space that has a field in user space you want
> > to reference?
> >
> >
> > field_val=+8u(+0(%si))
>
> Ah, that looks good :~)
On Tue, Feb 19, 2019 at 08:11:36PM -0800, Joel Fernandes wrote:
> On Tue, Feb 19, 2019 at 8:08 PM Joel Fernandes (Google)
> wrote:
> >
> > These patches fix various RCU API usage issues found due to sparse errors
> > as a
> > result of the recent check to add rcu_check_sparse() to
> >
Thanks for comments.
> > + if (!IS_ENABLED(CONFIG_SUSPEND_SKIP_SYNC)) {
> > + ktime_t start;
> > + unsigned int elapsed_msecs;
> > +
> > + trace_suspend_resume(TPS("sync_filesystems"), 0, true);
> > + pr_info("Syncing filesystems ... ");
> > +
Commit 57384592c433 ("iommu/vt-d: Store bus information in RMRR PCI
device path") changed the type of the path data, however, the change in
path type was not reflected in size calculations. Update to use the
correct type and prevent a buffer overflow.
This bug manifests in systems with deep PCI
If there are more trigger consumers than
CONFIG_IIO_CONSUMERS_PER_TRIGGER, iio_trigger_attach_poll_func will
silently fail. Add an error message to inform the user that
CONFIG_IIO_CONSUMERS_PER_TRIGGER limit might be exceeded.
Signed-off-by: Mathieu Othacehe
---
On 2/20/19 6:00 AM, Jonathan Cameron wrote:
On Wed, 13 Feb 2019 09:10:53 +0100
David Lechner wrote:
On 2/12/19 9:57 PM, justinpo...@gmail.com wrote:
From: Justin Chen
The ADS79XX has GPIO pins that can be used. Add support for the GPIO
pins using the GPIO chip framework.
Signed-off-by:
The AXP20X_xxx_START/END/STEPS defines make the code hard to read and
very hard to check the linear range settings because it needs to check
the defines one-by-one.
The original code without the defines is very good in readability
as the meaning of each field of REGULATOR_LINEAR_RANGE is clear.
So
On Wed, Feb 20, 2019 at 09:15:52AM +0100, Christian Hohnstaedt wrote:
> + TPS65218_REGULATOR("LS2", "regulator-ls2", TPS65218_LS_2,
> +REGULATOR_CURRENT, tps65218_ls23_ops, 0, 0, 0,
> +TPS65218_REG_ENABLE2, TPS65218_ENABLE2_LS2_EN,
> +
The first version of this method was missing the check for
`ret == PATH_MAX`; then such a check was added, but it didn't call kfree()
on error, so there was still a small memory leak in the error case.
Fix it by using strndup_user() instead of open-coding it.
Fixes: 0eadcc7a7bc0 ("perf/core: Fix
On Mon, 18 Feb 2019 15:03:21 +0100
Patrick Havelange wrote:
> This is implemented by polling the counter value. A new parameter
> "poll-interval" can be set in the device tree, or can be changed
> at runtime. The reason for the polling is to avoid interrupts flooding.
> If the quadrature input
When we hotplug a CPU in a memoryless/cpuless node, the kernel crashes when it
rebuilds the sched_domains data.
I reproduce this problem on POWER and with a pseries VM, with the following
QEMU parameters:
-machine pseries -enable-kvm -m 8192 \
-smp 2,maxcpus=8,sockets=4,cores=2,threads=1 \
On Wed, Sep 26, 2018 at 9:49 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:739d0def85ca Merge branch 'hv_netvsc-Support-LRO-RSC-in-th..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13aa179e40
> kernel config:
On Wed, 20 Feb 2019 17:49:10 +0100
Mathieu Othacehe wrote:
> If there are more trigger consumers than
> CONFIG_IIO_CONSUMERS_PER_TRIGGER, iio_trigger_attach_poll_func will
> silently fail. Add an error message to inform the user that
> CONFIG_IIO_CONSUMERS_PER_TRIGGER limit might be exceeded.
>
On Wed, Sep 12, 2018 at 3:23 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1333df0140
> kernel config:
On Wed, Aug 22, 2018 at 8:28 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:0214f46b3a03 Merge branch 'siginfo-linus' of git://git.ker..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11bc9c2e40
> kernel config:
On 2/20/19 5:51 PM, Arnd Bergmann wrote:
> On Wed, Feb 20, 2019 at 3:45 PM Andrey Konovalov
> wrote:
>>
>> On Tue, Feb 19, 2019 at 10:49 PM Arnd Bergmann wrote:
>>>
>>> Building an arm64 allmodconfig kernel with clang results in over 140
>>> warnings
>>> about overly large stack frames, the
20.02.2019 19:36, Michał Mirosław пишет:
> On Wed, Feb 20, 2019 at 04:30:20PM +0300, Dmitry Osipenko wrote:
>> 18.02.2019 3:17, Dmitry Osipenko пишет:
>>> Hello,
>>>
>>> This patchset adds support for the Trusted Foundations firmware on
>>> NVIDIA Tegra30. Pretty much all of Tegra30 consumer
On Wed, Feb 20, 2019 at 12:15 AM Dominik Brodowski
wrote:
>
> On Tue, Feb 19, 2019 at 04:54:49PM -0800, Kees Cook wrote:
> > diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> > index cb28e98a0659..7e0ea4470f8e 100644
> > --- a/arch/x86/kernel/cpu/common.c
> > +++
On Tue, Feb 19, 2019 at 6:37 PM Jann Horn wrote:
>
> On Wed, Feb 20, 2019 at 1:55 AM Kees Cook wrote:
> > + if (WARN_ONCE(cr4_pin && (val & cr4_pin) == 0,
>
> Don't you mean `cr4_pin && (val & cr4_pin) != cr4_pin)`?
Whoops! Yes, thanks. :)
--
Kees Cook
On 2/20/19 9:15 AM, Julien Grall wrote:
> Hi Boris,
>
> Thank you for your answer.
>
> On 20/02/2019 00:02, Boris Ostrovsky wrote:
>> On Tue, Feb 19, 2019 at 05:31:10PM +, Julien Grall wrote:
>>> Hi all,
>>>
>>> I have been looking at using Linux RT in Dom0. Once the guest is
>>> started,
>>>
On Wed, 20 Feb 2019 17:20:29 +0100
"H. Nikolaus Schaller" wrote:
> > Am 20.02.2019 um 17:14 schrieb Jonathan Cameron :
> >
> > On Wed, 20 Feb 2019 15:00:50 +0100
> > "H. Nikolaus Schaller" wrote:
> >
> >> This patch allows to read a mount-matrix device tree
> >> property and report to
On Wed, Feb 20, 2019 at 05:55:20PM +0100, Laurent Vivier wrote:
> index 3f35ba1d8fde..372278605f0d 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -1651,6 +1651,7 @@ void sched_init_numa(void)
>*/
> tl[i++] = (struct sched_domain_topology_level){
>
On Tue, Feb 12, 2019 at 1:37 PM Dan Williams wrote:
>
> Lately Linux has encountered platforms that collide Persistent Memory
> regions between each other, specifically cases where ->start_pad needed
> to be non-zero. This lead to commit ae86cbfef381 "libnvdimm, pfn: Pad
> pfn namespaces relative
On Tue, Feb 19, 2019 at 06:32:50PM +0100, Håkon Bugge wrote:
>Anyway, Jason mentioned in a private email that maybe we could use the
>new completion API or something? I am not familiar with that one
>(yet).
I was thinking of the stuff in core/cq.c - but it also doesn't have
automatic
On Tue, Feb 19, 2019 at 08:46:27PM -0700, Jason Gunthorpe wrote:
> On Tue, Feb 19, 2019 at 05:26:09PM -0800, Matthew Wilcox wrote:
> > On Tue, Feb 19, 2019 at 04:53:49PM -0700, Jason Gunthorpe wrote:
> > > Hey Matt,
> > >
> > > Did you intend that xa_release doesn't work on allocating arrays:
> >
On Wed, 13 Feb 2019 17:42:55 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> Add a test case verifying that basic action combinations fail as
> expected.
>
Hi Tom,
This test appears to fail:
# echo 'hist:keys=comm:onmatch(sched.sched_wakeup).save(comm,prio)' >>
On 20/02/2019 18:11, Dan Williams wrote:
> Hello valued reviewers, can I plead for a sanity check of at least
> "libnvdimm/pfn: Introduce super-block minimum version requirements"
> and "libnvdimm/pfn: Fix 'start_pad' implementation"? In particular
> Jeff / Johannes this has end user / distro
Hi Tony,
On 2/20/2019 10:06 PM, Tony Lindgren wrote:
> Hi,
>
> Some more info on chained irq vs mux below that might
> help.
>
> * Tony Lindgren [190219 15:36]:
>> * Lokesh Vutla [190219 08:51]:
>>> With this can you tell me how can we not have a device-tree and still
>>> support
>>> irq
On 2/20/19 6:17 AM, Jonathan Cameron wrote:
> On Mon, 11 Feb 2019 16:23:18 -0600
> "Gustavo A. R. Silva" wrote:
>
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the following warning:
>>
>>
On 20/02/2019 17:15, Dan Williams wrote:> I wouldn't be opposed to
syzkaller fuzzing the nvdimm-ioctl path.
As a heads up, I've started adding the ioctl() definitions to syzcaller.
Just so we don't duplicate any efforts.
Byte,
Johannes
--
Johannes Thumshirn
On Tue, Feb 12, 2019 at 5:08 PM Jagan Teki wrote:
>
> Add missing dt-binding documentation for lm75 hwmon sensor.
>
> Signed-off-by: Jagan Teki
> ---
> Changes for v2:
> - Add all compatible nodes available in lm75.
>
> .../devicetree/bindings/hwmon/lm75.txt| 37 +++
>
On Wed, 20 Feb 2019 10:48:49 -0600
David Lechner wrote:
> On 2/20/19 6:00 AM, Jonathan Cameron wrote:
> > On Wed, 13 Feb 2019 09:10:53 +0100
> > David Lechner wrote:
> >
> >> On 2/12/19 9:57 PM, justinpo...@gmail.com wrote:
> >>> From: Justin Chen
> >>>
> >>> The ADS79XX has GPIO pins
This patch add an helper which wraps 'mtsrin' instruction
to write into segment registers.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/reg.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h
index
This patch defined CONFIG_PPC_PAGE_SHIFT in order
to be able to use PAGE_SHIFT value inside Kconfig.
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig| 7 +++
arch/powerpc/include/asm/page.h | 13 ++---
2 files changed, 9 insertions(+), 11 deletions(-)
diff
Now that mmu_mapin_ram() is able to handle other blocks
than the one starting at 0, the WII can use it for all
its blocks.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/pgtable_32.c | 25 +++--
1 file changed, 7 insertions(+), 18 deletions(-)
diff --git
'nobats' kernel parameter or some options like CONFIG_DEBUG_PAGEALLOC
deny the use of BATS for mapping memory.
This patch makes sure that the specific wii RAM mapping function
takes it into account as well.
Fixes: de32400dd26e ("wii: use both mem1 and mem2 as ram")
Cc: sta...@vger.kernel.org
Do not set IBAT when setbat() is called without _PAGE_EXEC
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/ppc_mmu_32.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/mm/ppc_mmu_32.c b/arch/powerpc/mm/ppc_mmu_32.c
index 5fc59b195fef..ff8580c6ab11
On 8xx, large pages (512kb or 8M) are used to map kernel linear
memory. Aligning to 8M reduces TLB misses as only 8M pages are used
in that case. We make 8M the default for data.
This patchs allows the user to do it via Kconfig.
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig
setibat() and clearibat() allows to manipulate IBATs independently
of DBATs.
update_bats() allows to update bats after init. This is done
with MMU off.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/mmu-hash.h | 2 ++
arch/powerpc/kernel/head_32.S | 35
This patch implements handling of STRICT_KERNEL_RWX with
large TLBs directly in the TLB miss handlers.
To do so, etext and sinittext are aligned on 512kB boundaries
and the miss handlers use 512kB pages instead of 8Mb pages for
addresses close to the boundaries.
It sets RO PP flags for addresses
Depending on the number of available BATs for mapping the different
kernel areas, it might be needed to increase the alignment of _etext
and/or of data areas.
This patchs allows the user to do it via Kconfig.
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig | 32
CONFIG_STRICT_KERNEL_RWX requires a special alignment
for DATA for some subarches. Today it is just defined
as an #ifdef in vmlinux.lds.S
In order to get more flexibility, this patch moves the
definition of this alignment in Kconfig
On some subarches, CONFIG_STRICT_KERNEL_RWX will
require a
This patch reworks mmu_mapin_ram() to be more generic and map as much
blocks as possible. It now supports blocks not starting at address 0.
It scans DBATs array to find free ones instead of forcing the use of
BAT2 and BAT3.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/ppc_mmu_32.c | 63
Add a helper to know whether STRICT_KERNEL_RWX is enabled.
This is based on rodata_enabled flag which is defined only
when CONFIG_STRICT_KERNEL_RWX is selected.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/mmu.h | 11 +++
arch/powerpc/mm/init_32.c | 4 +---
2
wii_mmu_mapin_mem2() is not used anymore, remove it.
Signed-off-by: Christophe Leroy
---
arch/powerpc/platforms/embedded6xx/wii.c | 28
1 file changed, 28 deletions(-)
diff --git a/arch/powerpc/platforms/embedded6xx/wii.c
b/arch/powerpc/platforms/embedded6xx/wii.c
Today, STRICT_KERNEL_RWX is based on the use of regular pages
to map kernel pages.
On Book3s 32, it has three consequences:
- Using pages instead of BAT for mapping kernel linear memory severely
impacts performance.
- Exec protection is not effective because no-execute cannot be set at
page level
At the time being, mmu_mapin_ram() always maps RAM from the beginning.
But some platforms like the WII have to map a second block of RAM.
This patch adds to mmu_mapin_ram() the base address of the block.
At the moment, only base address 0 is supported.
Signed-off-by: Christophe Leroy
---
When CONFIG_BDI_SWITCH is set, the page tables have to be populated
allthough large TLBs are used, because the BDI switch knows nothing
about those large TLBs which are handled directly in TLB miss logic.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/pgtable_32.c | 5 -
1 file
The purpose of this serie is to:
- use BATs with STRICT_KERNEL_RWX on book3s (See patch 13 for details.)
- use LTLBs with STRICT_KERNEL_RWX on 8xx (See patch 15 for a few details.)
v3:
- Reordered to avoid build failure due to setibat() not being used for several
steps in the serie.
Now the
On Wed, Feb 20, 2019 at 6:00 PM Andrey Ryabinin wrote:
> On 2/20/19 5:51 PM, Arnd Bergmann wrote:
> > On Wed, Feb 20, 2019 at 3:45 PM Andrey Konovalov
> > wrote:
> > I would have to some more research, but I expect several hundred
> > patches before we get to a clean randconfig build with a
Hi Steve,
On Wed, 2019-02-20 at 12:17 -0500, Steven Rostedt wrote:
> On Wed, 13 Feb 2019 17:42:55 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > Add a test case verifying that basic action combinations fail as
> > expected.
> >
>
> Hi Tom,
>
> This test appears to fail:
>
> #
Le 25/01/2019 à 13:34, Christophe Leroy a écrit :
Use SPRN_SPRG5 to store the current thread PGDIR and
avoid reading thread_struct->pgdir at every TLB miss.
I'll send out v2 with an additional patch getting rid of SPRN_SPRG_RTAS
hence freeing SPRN_SPRG2 which I will use here instead of
Dan Williams writes:
> On Tue, Feb 12, 2019 at 1:37 PM Dan Williams wrote:
>>
>> Lately Linux has encountered platforms that collide Persistent Memory
>> regions between each other, specifically cases where ->start_pad needed
>> to be non-zero. This lead to commit ae86cbfef381 "libnvdimm, pfn:
On Wed, Feb 20, 2019 at 09:14:14AM -0800, Matthew Wilcox wrote:
> > void __xa_release(struct xarray *xa, unsigned long index)
> > {
> > XA_STATE(xas, xa, index);
> > void *curr;
> >
> > curr = xas_load();
> > if (curr == XA_ZERO_ENTRY)
> > xas_store(, NULL);
> > }
> >
> On 20 Feb 2019, at 18:14, Jason Gunthorpe wrote:
>
> On Tue, Feb 19, 2019 at 06:32:50PM +0100, Håkon Bugge wrote:
>> Anyway, Jason mentioned in a private email that maybe we could use the
>> new completion API or something? I am not familiar with that one
>> (yet).
>
> I was thinking
Le 19/02/2019 à 18:23, Christophe Leroy a écrit :
This patch adds KASAN support for PPC32.
The KASAN shadow area is located between the vmalloc area and the
fixmap area.
KASAN_SHADOW_OFFSET is calculated in asm/kasan.h and extracted
by Makefile prepare rule via asm-offsets.h
For modules,
The pull request you sent on Wed, 20 Feb 2019 09:08:25 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
> tags/pinctrl-v5.0-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fb83f15ef9dd984834bc60b380efbeffdf1ecc04
Thank you!
--
The pull request you sent on Wed, 20 Feb 2019 09:03:22 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
> tags/gpio-v5.0-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c828c2651b9a8184e1414fa0611d18b84d3847dd
Thank you!
--
The pull request you sent on Wed, 20 Feb 2019 11:42:46 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-5.0
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2137397c92aec3713fa10be3c9b830f9a1674e60
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Wed, 20 Feb 2019 08:56:53 +0100:
> git://git.infradead.org/linux-mtd.git tags/mtd/fixes-for-5.0-rc8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7d9d592caf8cc5d91f7923c5e717b69d0b1e246f
Thank you!
--
Deet-doot-dot, I am a bot.
Hi!
I really wanted to do another review on previous series but got distracted by
analyzing one particulary troublesome H264 sample. It still doesn't work
correctly, so I would ask you if you can test it with your stack (it might be
userspace issue):
The patch
ASoC: samsung: odroid: Fix of_node refcount unbalance
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)
The patch
regulator: max77650: Add missing .owner field in regulator_desc
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 patch
regulator: twl6030: Constify regulator_ops
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 hours) and
The patch
regulator: tps65218.c: fix LS3 issues
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 hours) and sent
The patch
regulator: max77620: Add missing .owner field in regulator_desc
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 patch
regulator: twl6030: Use regulator_list_voltage_linear_range for
twl6030ldo_ops
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
Colin King wrote:
> From: Colin Ian King
>
> There is an uppercase 'N' that should be a lowercase 'n', fix this.
>
> Signed-off-by: Colin Ian King
Patch applied to wireless-drivers-next.git, thanks.
0421dd4167ec rtlwifi: rtl8192ce: fix typo, "PairwiseENcAlgorithm" ->
Lubomir Rintel wrote:
> We'll need to talk to the firmware to get a hardware address before
> device is registered with ieee80211 subsystem at the end of
> lbtf_add_card(). Hooking the callbacks after that is too late.
>
> Signed-off-by: Lubomir Rintel
3 patches applied to
Paul Kocialkowski writes:
> Hi,
>
> Here is a fourth iteration of the VC4 load tracking series, which was
> initially developed by Boris Brezillon and that I have now taken over.
>
> This new iteration takes in account comments from v3 and comes with a
> new approach for avoiding underrun
On Wed, Feb 20, 2019 at 11:51:34AM +0100, Arnd Bergmann wrote:
> On Tue, Feb 19, 2019 at 7:22 PM Nathan Chancellor
> wrote:
> >
>
> > diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c
> > b/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c
> > index
On 20/02/2019 18:08, Peter Zijlstra wrote:
> On Wed, Feb 20, 2019 at 05:55:20PM +0100, Laurent Vivier wrote:
>> index 3f35ba1d8fde..372278605f0d 100644
>> --- a/kernel/sched/topology.c
>> +++ b/kernel/sched/topology.c
>> @@ -1651,6 +1651,7 @@ void sched_init_numa(void)
>> */
>> tl[i++]
On Wed, 20 Feb 2019 11:38:22 -0600
Tom Zanussi wrote:
> Hi Steve,
>
> On Wed, 2019-02-20 at 12:17 -0500, Steven Rostedt wrote:
> > On Wed, 13 Feb 2019 17:42:55 -0600
> > Tom Zanussi wrote:
> >
> > > From: Tom Zanussi
> > >
> > > Add a test case verifying that basic action combinations
On Wed, Feb 20, 2019 at 12:59 AM Peter Zijlstra wrote:
>
> On Tue, Feb 19, 2019 at 05:48:36PM -0800, Olof Johansson wrote:
> > Getting notified of unknown NMIs is obviously important, but getting
> > notified on every single one, especially on larger systems with slow
> > (serial) console causes
On Wed, Feb 20, 2019 at 07:19:30AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 19, 2019 at 09:30:33PM -0800, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > Resending these as I had only 1 minor comment which I believe we have
> > covered
> > in this series. I was anticipating these
On 12/02/2019 19:06, Sowjanya Komatineni wrote:
> This patch adds DMA support for Tegra I2C.
>
> Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
> transfer size of the max FIFO depth and DMA mode is used for
> transfer size higher than max FIFO depth to save CPU overhead.
>
>
Hi,
On 20/02/2019 17:07, Boris Ostrovsky wrote:
On 2/20/19 9:15 AM, Julien Grall wrote:
Hi Boris,
Thank you for your answer.
On 20/02/2019 00:02, Boris Ostrovsky wrote:
On Tue, Feb 19, 2019 at 05:31:10PM +, Julien Grall wrote:
Hi all,
I have been looking at using Linux RT in Dom0.
20.02.2019 21:02, Jon Hunter пишет:
>
> On 12/02/2019 19:06, Sowjanya Komatineni wrote:
>> This patch adds DMA support for Tegra I2C.
>>
>> Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
>> transfer size of the max FIFO depth and DMA mode is used for
>> transfer size higher than
Hi,
On Mon, Feb 11, 2019 at 11:01:12AM -0800, egran...@chromium.org wrote:
> From: Enrico Granata
>
> ACPI 5 added support for GpioInt resources as a way to provide
> information about interrupts mediated via a GPIO controller.
>
> Several device buses (e.g. SPI, I2C) have support for
On 2/20/19 11:21 AM, Gustavo A. R. Silva wrote:
>
>
> On 2/20/19 6:17 AM, Jonathan Cameron wrote:
>> On Mon, 11 Feb 2019 16:23:18 -0600
>> "Gustavo A. R. Silva" wrote:
>>
>>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>>> cases where we are expecting to fall through.
>>>
+ Evgenii
On Wed, Feb 20, 2019 at 9:36 AM Arnd Bergmann wrote:
>
> On Wed, Feb 20, 2019 at 6:00 PM Andrey Ryabinin
> wrote:
> > On 2/20/19 5:51 PM, Arnd Bergmann wrote:
> > > On Wed, Feb 20, 2019 at 3:45 PM Andrey Konovalov
> > > wrote:
> > > I would have to some more research, but I expect
On Wed, Feb 20, 2019 at 08:40:34AM -0800, Paul E. McKenney wrote:
> On Tue, Feb 19, 2019 at 11:08:23PM -0500, Joel Fernandes (Google) wrote:
> > From: Joel Fernandes
> >
> > rtnl_register_internal() and rtnl_unregister_all tries to directly
> > dereference an RCU protected pointed outside RCU
Several recent exploits have used direct calls to the native_write_cr4()
function to disable SMEP and SMAP before then continuing their exploits
using userspace memory access. This pins bits of cr4 so that they cannot
be changed through a common function. This is not intended to be general
ROP
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 2/11/19 12:31 PM, Gustavo A. R. Silva wrote:
> Add missing break statement in order to prevent the code from falling
> through to case S_DIN_to_DES.
>
> This bug was found thanks to the ongoing efforts to enable
>
On Wed, Feb 20, 2019 at 08:42:43AM -0800, Paul E. McKenney wrote:
> On Tue, Feb 19, 2019 at 08:11:36PM -0800, Joel Fernandes wrote:
> > On Tue, Feb 19, 2019 at 8:08 PM Joel Fernandes (Google)
> > wrote:
> > >
> > > These patches fix various RCU API usage issues found due to sparse errors
> > >
Hi Steve,
On Wed, 2019-02-20 at 12:56 -0500, Steven Rostedt wrote:
> On Wed, 20 Feb 2019 11:38:22 -0600
> Tom Zanussi wrote:
>
> > Hi Steve,
> >
> > On Wed, 2019-02-20 at 12:17 -0500, Steven Rostedt wrote:
> > > On Wed, 13 Feb 2019 17:42:55 -0600
> > > Tom Zanussi wrote:
> > >
> > > >
When phys do not start at address 0 like on the mv88e6341 the wrong
phy address is used and therefore the slave ports can not be
initialized. This patch adds the proper offset to the phy address.
Signed-off-by: Marcel Reichmuth
---
drivers/net/dsa/mv88e6xxx/chip.c | 3 +++
include/net/dsa.h
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 2/12/19 3:43 PM, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
>
The clock driver may probe after ours and so we need to pass the
-EPROBE_DEFER out. Fix the other error path while we're here.
v2: Use dom->name instead of dom->gov as the flag for initialized
domains, since we aren't setting up a governor. Make sure to
clear ->clk when no clk is
Florian Fainelli writes:
> On 2/13/19 2:33 PM, Stefan Wahren wrote:
>>
>>> Eric Anholt hat am 13. Februar 2019 um 19:28 geschrieben:
>>>
>>>
>>> Stefan Wahren writes:
>>>
Hi Eric,
Am 13.02.19 um 01:33 schrieb Eric Anholt:
> The clock driver may probe after ours and so we
We don't have ASB master/slave regs for this domain, so just skip that
step.
Signed-off-by: Eric Anholt
Fixes: 670c672608a1 ("soc: bcm: bcm2835-pm: Add support for power domains under
a new binding.")
---
drivers/soc/bcm/bcm2835-power.c | 14 --
1 file changed, 12 insertions(+), 2
On Mon, Oct 8, 2018 at 10:24 AM Gustavo A. R. Silva
wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 1397962 ("Missing break in switch")
> Signed-off-by: Gustavo A. R. Silva
> ---
>
On Wed, Feb 20, 2019 at 2:00 AM Daniel Borkmann wrote:
>
> On 02/20/2019 10:32 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:abf446c90405 Add linux-next specific files for 20190220
> > git tree:
601 - 700 of 1140 matches
Mail list logo
