Am Donnerstag, 19. Oktober 2017, 11:48:03 CET schrieb Jeffy Chen:
> Add edp panel and enable related nodes on kevin.
>
> Signed-off-by: Jeffy Chen
> Reviewed-by: Mark Yao
applied for 4.16 with Enric's Tested-tag and after also
seeing a bit of output on the edp.
Thanks
Heiko
Olof Johansson writes:
> Thanks, Stephen. I need to get a similar script going to catch these
> things in our own tree.
>
> Since this was a clean revert, I've redone it myself, carrying over
> descriptions from the pull request and keeping attribution to Kevin.
>
> Kevin; hope this is alright wi
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
>
> Kernel Page Table Isolation, prefix kpti_
>
>Linus, your call :)
I think you probably chose the right name here. The alternatives sound
intriguing, but probably not the right thing to do.
How much of this is considered worth tryi
On Mon, Dec 04, 2017 at 06:39:16PM +0100, Javier Martinez Canillas wrote:
> The commit 21dc02eab989 ("tpm/tpm_i2c_infineon.c: Add OF attributes type
> and name to the of_device_id table entries") added type and name fields
> to the OF device ID table entries for the I2C Infineon TPM driver.
>
> Th
On 12/4/2017 11:23 AM, Rob Herring wrote:
> On Fri, Dec 1, 2017 at 10:27 PM, Sinan Kaya wrote:
>> Now that we have a get_match_data() callback as part of the firmware node,
>> implement the OF specific piece for it.
>>
>> Signed-off-by: Sinan Kaya
>> ---
>> drivers/of/property.c | 17 +++
On Mon, Dec 4, 2017 at 4:20 PM, Gustavo A. R. Silva
wrote:
> Hi Joonas,
>
> Quoting Joonas Lahtinen :
>
>> On Mon, 2017-11-27 at 16:17 -0600, Gustavo A. R. Silva wrote:
>>>
>>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>>> where we are expecting to fall through.
>>
>>
>>
From: Colin Ian King
Variable key_ref is being assigned a value that is never read;
key_ref is being re-assigned a few statements later. Hence this
assignment is redundant and can be removed.
Signed-off-by: Colin Ian King
---
security/keys/key.c | 1 -
1 file changed, 1 deletion(-)
diff --gi
On Mon, 4 Dec 2017, Linus Torvalds wrote:
> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> >
> > Kernel Page Table Isolation, prefix kpti_
> >
> >Linus, your call :)
>
> I think you probably chose the right name here. The alternatives sound
> intriguing, but probably not the rig
On Mon, Dec 4, 2017 at 7:56 AM, Will Deacon wrote:
> On Fri, Dec 01, 2017 at 12:10:00PM -0800, Kees Cook wrote:
>> Distros have been shipping with CONFIG_STRICT_DEVMEM=y for years now. It
>> is probably time to flip this default for x86 and arm64.
>
> Should we be defaulting IO_STRICT_DEVMEM on as
[+Ard]
Hi Cyrille,
On Sun, Dec 03, 2017 at 09:44:46PM +0100, Cyrille Pitchen wrote:
[...]
> >> +cdns_pci_map_bus(struct pci_bus *bus, unsigned int devfn, int where)
> >> +{
> >> + struct pci_host_bridge *bridge = pci_find_host_bridge(bus);
> >> + struct cdns_pcie_rc *rc = pci_host_bridg
To increase the readability of the register accesses, the abstraction
of the helpers was increased from simple read and write to set bit,
reset bit and read modify write bit. In addition - according to the
proposal from Walter Harms from 20.07.2017 - instead of marcros inline
functions were used.
On Mon, Dec 04, 2017 at 03:07:20PM +0100, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> 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
>
On Wed, Nov 22, 2017 at 08:43:17PM +0900, Katsuhiro Suzuki wrote:
> +++ b/sound/soc/uniphier/evea.c
> @@ -0,0 +1,567 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Socionext UniPhier EVEA ADC/DAC codec driver.
> + *
> + * Copyright (c) 2016-2017 Socionext Inc.
Make the entire comment a C++
From: Stephen Rothwell
Date: Mon, 4 Dec 2017 11:02:49 +1100
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but
> not used [-Wunused-function]
> static in
> On Dec 3, 2017, at 9:03 AM, Alexei Starovoitov
> wrote:
>
> On Thu, Nov 30, 2017 at 03:50:18PM -0800, Song Liu wrote:
>> Two new perf types, perf_kprobe and perf_uprobe, will be added to allow
>> creating [k,u]probe with perf_event_open. These [k,u]probe are associated
>> with the file decrip
From: Arvind Yadav
Date: Mon, 4 Dec 2017 23:18:20 +0530
> @@ -120,9 +120,10 @@ static int sni_82596_probe(struct platform_device *dev)
> netdevice->dev_addr[5] = readb(eth_addr + 0x06);
> iounmap(eth_addr);
>
> - if (!netdevice->irq) {
> + if (netdevice->irq <= 0) {
>
On 12/4/17 10:24 AM, Song Liu wrote:
On Dec 3, 2017, at 9:03 AM, Alexei Starovoitov
wrote:
On Thu, Nov 30, 2017 at 03:50:18PM -0800, Song Liu wrote:
Two new perf types, perf_kprobe and perf_uprobe, will be added to allow
creating [k,u]probe with perf_event_open. These [k,u]probe are associa
On Mon, Dec 4, 2017 at 10:18 AM, Thomas Gleixner wrote:
>>
>> How much of this is considered worth trying to integrate early?
>
> Probably the entry changes, but we need to sort out that fixmap issue first
> and that affects the entry changes as well. Give me a day or two and I can
> tell you.
Su
On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote:
> These duplicate includes have been found with scripts/checkincludes.pl but
> they have been removed manually to avoid removing false positives.
>
> Unit Testing:
>
> - build successful
> - LTP testsuite passes.
> - checkpatch.pl pas
On Sat, Dec 02, 2017 at 09:06:29AM +0800, Lai Jiangshan wrote:
> On Sat, Dec 2, 2017 at 3:21 AM, Paul E. McKenney
> wrote:
> > Now that cond_resched() also provides RCU quiescent states when
> > needed, it can be used in place of cond_resched_rcu_qs(). This
> > commit therefore makes this change.
On Sat, Dec 02, 2017 at 09:27:46AM +0800, Lai Jiangshan wrote:
> On Sat, Dec 2, 2017 at 3:41 AM, Paul E. McKenney
> wrote:
> > This commit changes the %p printk() in rcutorture to %pK. This could
> > be considered irrelevant, given that any user able to start rcutorture
> > could inflict far heav
On 12/4/2017 10:34 AM, Kirill A. Shutemov wrote:
On Mon, Dec 04, 2017 at 04:00:26PM +, Tom Lendacky wrote:
On 12/4/2017 8:57 AM, Kirill A. Shutemov wrote:
On Mon, Dec 04, 2017 at 08:19:11AM -0600, Tom Lendacky wrote:
On 12/4/2017 5:23 AM, Kirill A. Shutemov wrote:
sme_populate_pgd() open-
On 2017-12-04 10:04 +, Jose Abreu wrote:
> On 03-12-2017 05:20, Nick Bowler wrote:
> > I brought the original test equipment back to the setup so I can
> > see the video and pink bar again. The symptoms remain the same
> > (unexpected size, pink bar, and no audio).
> >
>
> Can you tell me whic
On Mon, Dec 04, 2017 at 09:48:57AM -0700, Nathan Chancellor wrote:
> Merged, compiled, and flashed on my Pixel 2 XL and OnePlus 5.
>
> No initial issues noticed in general usage or dmesg.
Wonderful, thanks for testing and letting me know.
greg k-h
On Mon, Dec 4, 2017 at 6:49 AM, Arnd Bergmann wrote:
> gcc-8 warns about using strncpy() with the source size as the limit:
>
> fs/exec.c:1223:32: error: argument to 'sizeof' in 'strncpy' call is the same
> expression as the source; did you mean to use the size of the destination?
> [-Werror=siz
Am 04.12.2017 um 12:37 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 01:17:37PM +0300, Dan Carpenter wrote:
Perhaps choose different function names if you want? You could do it
as several patches:
patch 1: change types to bool
patch 2: sed -e '/ == optionOn//'
patch 3: split the functions i
If the firmware fails to load then ->fini() will be called before the
device has been initialised, causing the kernel to hang while trying
to write to a register. Add a test in ->fini() to avoid this issue.
This fixes a kernel hang on tegra124.
Fixes: b17de35a2ebbe ("drm/nouveau/bar: implement b
On Mon, Dec 04, 2017 at 03:20:34PM +, Bean Huo (beanhuo) wrote:
> Hi, Bart
> Sorry for later!
> >
> >Hello Bean,
> >
> >Please be more specific. What is inconvenient about sg3_utils on embedded
> >ARM systems?
> >
> Exactly, I don't know how to compile sg3_utils with static library, instead
>
When neither HDMI nor DP is supported such as on the tegra124, the
sor->clk_out is not initialised and remains NULL. In this case, the
parent clock can't be assigned to it so revert to the previous
behaviour of assigning it to the main sor->clock instead.
This fixes a kernel hang on tegra124.
Fi
On Wed, Nov 22, 2017 at 08:43:18PM +0900, Katsuhiro Suzuki wrote:
> sound/soc/uniphier/Makefile | 4 +
> sound/soc/uniphier/aio-core.c| 368 +
> sound/soc/uniphier/aio-dma.c | 266 +++
> sound/soc/uniphier/aio-regctrl.c | 699
> +
On Mon, Dec 4, 2017 at 5:44 PM, Al Viro wrote:
> On Thu, Nov 02, 2017 at 04:05:01AM -0700, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 3a99df9a3d14cd866b5516f8cba515a3bfd554ab
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
>> compiler: gcc (GCC
This adds the devicetree bindings for the LM3692x
I2C LED string driver.
Acked-by: Pavel Machek
Signed-off-by: Dan Murphy
---
v7 - No changes - https://patchwork.kernel.org/patch/10087475/
v6 - No changes -https://patchwork.kernel.org/patch/10085567/
v5 - No Changes - https://patchwork.kernel.o
Introducing the LM3692x Dual-String white LED driver.
Data sheet is located
http://www.ti.com/lit/ds/snvsa29/snvsa29.pdf
Signed-off-by: Dan Murphy
---
v7 - Reverted back to creating the LED label within the driver -
https://patchwork.kernel.org/patch/10087473/
v6 - Use new LED API to compose L
On Mon, Dec 04, 2017 at 07:39:29PM +0100, Dmitry Vyukov wrote:
> On Mon, Dec 4, 2017 at 5:44 PM, Al Viro wrote:
> > On Thu, Nov 02, 2017 at 04:05:01AM -0700, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> 3a99df9a3d14cd866b5516f8cba515a3bfd554ab
> >> git://git.kernel
On Mon Dec 04 17, Mathias Nyman wrote:
Interface drivers like btusb that don't support reset-resume will be
rebound at resume if port was reset. Rebind is done during the pm_ops
.complete callback when probe returns EPROBE_DEFER as default.
Remove the "rebind failed: -517" message.
Device probe
The patch
MAINTAINERS: add entries for UniPhier ASoC sound drivers
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
ASoC: spdif: Add S32_LE support for S/PDIF dummy codec drivers
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 h
The patch
ASoC: uniphier: add support for UniPhier EVEA codec
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 s
The patch
ASoC: eukrea-tlv320: Remove include line of fsl_ssi.h
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
On 4 December 2017 at 18:20, Lorenzo Pieralisi
wrote:
> [+Ard]
>
> Hi Cyrille,
>
> On Sun, Dec 03, 2017 at 09:44:46PM +0100, Cyrille Pitchen wrote:
>
> [...]
>
>> >> +cdns_pci_map_bus(struct pci_bus *bus, unsigned int devfn, int where)
>> >> +{
>> >> + struct pci_host_bridge *bridge = pci_find
The patch
ASoC: amd: added error checks in dma driver
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 L
The patch
ASoC: uniphier: add DT bindings documentation for UniPhier EVEA
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
On Mon, Dec 04, 2017 at 12:33:01PM -0600, Tom Lendacky wrote:
> On 12/4/2017 10:34 AM, Kirill A. Shutemov wrote:
> > On Mon, Dec 04, 2017 at 04:00:26PM +, Tom Lendacky wrote:
> > > On 12/4/2017 8:57 AM, Kirill A. Shutemov wrote:
> > > > On Mon, Dec 04, 2017 at 08:19:11AM -0600, Tom Lendacky wro
On Mon, Dec 04, 2017 at 03:38:56PM +, David Howells wrote:
> Paul E. McKenney wrote:
>
> > - Q = READ_ONCE(P); smp_read_barrier_depends(); D = READ_ONCE(*Q);
> > + Q = READ_ONCE(P); D = READ_ONCE(*Q);
> >
> > the CPU will issue the following memory operations:
> >
> > Q = LO
On Mon, Dec 04, 2017 at 11:59:22AM +1100, James Morris wrote:
> On Fri, 1 Dec 2017, Paul E. McKenney wrote:
>
> > Now that the associative-array library properly heads dependency chains,
> > the various smp_read_barrier_depends() calls in security/keys/keyring.c
> > are no longer needed. This com
On Sat, Dec 02, 2017 at 12:19:27PM +, Jonathan Cameron wrote:
> > diff --git a/drivers/iio/accel/bmc150-accel.h
> > b/drivers/iio/accel/bmc150-accel.h
> > index c38754452883..7f49a09b136f 100644
> > --- a/drivers/iio/accel/bmc150-accel.h
> > +++ b/drivers/iio/accel/bmc150-accel.h
> > @@ -47,6
Am 04.12.2017 um 12:33 schrieb Dan Carpenter:
On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi433_if.h
index 34ff0d4807bd..bcfe29840889 100644
--- a/drivers/staging/pi433/pi433_if.h
+++ b/drivers/staging/pi
On Mon, 4 Dec 2017, J. Bruce Fields wrote:
On Mon, Dec 04, 2017 at 01:39:37PM -0200, Thiago Rafael Becker wrote:
On Mon, 4 Dec 2017, NeilBrown wrote:
I think you need to add groups_sort() in a few more places.
Almost anywhere that calls groups_alloc() should be considered.
net/sunrpc/svca
In cases where group_info is cached (e.g. sunrpc), multiplpe
threads may call set_groups with a freshly created group_info
cache (e.g. nfsd), and attempt to sort them simultaneously,
which configures a race condition that can overwrite some
groups in the cache and lead to errors. In the case of nfs
The responsibility for calling groups_sort is now on the caller
of set_groups.
Signed-off-by: Thiago Rafael Becker
---
kernel/groups.c | 1 +
kernel/uid16.c| 1 +
net/sunrpc/svcauth_unix.c | 7 +++
3 files changed, 9 insertions(+)
diff --git a/kernel/groups.c b/kernel/
In preparation to move group_info sorting to the caller,
make group_sort globally visible.
Signed-off-by: Thiago Rafael Becker
---
include/linux/cred.h | 1 +
kernel/groups.c | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/cred.h b/include/linux/cred.h
When the group_info is cached (e.g. sunrpc) there's the possibility
that threads calling set_groups will attempt to do so simultaneously.
Moving the responsibility of sorting to the caller of set_groups, or
in the case of nfsd, to the point where it is received from rpc.mountd
avoids this issue.
Hi Nick,
On Friday, 1 December 2017 02:11:46 EET Nick Bowler wrote:
> On 2017-11-27 22:30 -0500, Nick Bowler wrote:
> > A note about the test setup: I had to remove the test equipment so I
> > no longer have any information about the video mode from the sink side
> > (like in the photos). Thus, w
On Fri, Dec 01, 2017 at 08:45:13PM -0800, Joe Perches wrote:
> On Fri, 2017-12-01 at 13:44 -0800, Paul E. McKenney wrote:
[ . . . ]
> > Good points! Like this?
> []
> > commit ff155ce179aab891dbe2ca80f82a453383fd165a
> > Author: Paul E. McKenney
> > Date: Mon Nov 27 09:37:35 2017 -0800
> >
>
Reviewed-by: Vidya Sagar
On Sunday 03 December 2017 03:15 AM, Bjorn Helgaas wrote:
The PCIe active link power state is L0. ASPM defines two low-power
states: L0s and L1. The L1 PM Substates feature defines two
additional low-power states: L1.1 and L2.2.
The L1.2 state may have substantial en
Am 04.12.2017 um 12:24 schrieb Dan Carpenter:
On Sun, Dec 03, 2017 at 04:17:25PM +0100, Simon Sandström wrote:
Renames enum dataMode and its values packet, continuous, continuousNoSync
to enum data_mode and PACKET, CONTINUOUS, CONTINUOUS_NO_SYNC. Fixes
checkpatch.pl warnings: "Avoid CamelCase:
On Mon, 2017-12-04 at 11:06 -0800, Paul E. McKenney wrote:
> On Fri, Dec 01, 2017 at 08:45:13PM -0800, Joe Perches wrote:
> > On Fri, 2017-12-01 at 13:44 -0800, Paul E. McKenney wrote:
>
> > If you really wanted to optimize, you could make the first (smp_|)
> > become (?:smp_|) to avoid the unused
Restrict which nodes are valid targets for a DT overlay.
Add a flag bit to struct device_node allowing nodes to be marked as
valid target for overlays.
A driver that is always intended to handle DT overlays can
enable overlays by calling a function for its DT node.
For individual nodes that need
Allow DT nodes to be marked as valid targets for DT
overlays by the added "overlay-allowed" property.
Signed-off-by: Alan Tull
---
drivers/of/base.c | 4 ++--
drivers/of/dynamic.c| 3 +++
drivers/of/fdt.c| 3 +++
drivers/of/of_private.h | 2 ++
4 files changed, 10 insertions(+)
Disregard this. git reset --hard without a git stash. Sorry about it.
On Mon, 4 Dec 2017, Thiago Rafael Becker wrote:
The responsibility for calling groups_sort is now on the caller
of set_groups.
Signed-off-by: Thiago Rafael Becker
---
kernel/groups.c | 1 +
kernel/uid16.c
Add a flag to struct device_node marking the node as a valid target
for device tree overlays. When an overlay is submitted, if any target
in the overlay is not enabled for overlays, the overlay is rejected.
Drivers that support dynamic configuration can enable/disable their
device node with:
vo
On Mon, Dec 04, 2017 at 08:37:51PM +0200, Marcus Wolf wrote:
>
>
> Am 04.12.2017 um 12:37 schrieb Dan Carpenter:
> > On Mon, Dec 04, 2017 at 01:17:37PM +0300, Dan Carpenter wrote:
> > > Perhaps choose different function names if you want? You could do it
> > > as several patches:
> > >
> > > pa
[PATCH v3 1/5] kasan: add compiler support for clang
No change
[PATCH v3 2/5] kasan/Makefile: Support LLVM style asan parameters.
Correctly attributed
Changed to use strip to work in all environments
[PATCH v3 3/5] kasan: support alloca() poisoning
No change
[PATCH v3 4/5] kasan: Add tes
From: Andrey Ryabinin
LLVM doesn't understand GCC-style paramters ("--param asan-foo=bar"),
thus we currently we don't use inline/globals/stack instrumentation
when building the kernel with clang.
Add support for LLVM-style parameters ("-mllvm -asan-foo=bar") to
enable all KASAN features.
Signe
clang's AddressSanitizer implementation adds redzones on either side of
alloca()ed buffers. These redzones are 32-byte aligned and at least 32
bytes long.
__asan_alloca_poison() is passed the size and address of the allocated
buffer, *excluding* the redzones on either side. The left redzone will
For now we can hard-code ASAN ABI level 5, since historical clang builds
can't build the kernel anyway. We also need to emulate gcc's
__SANITIZE_ADDRESS__ flag, or memset() calls won't be instrumented.
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
---
include/linux/compiler-clang.h
Signed-off-by: Greg Hackmann
Signed-off-by: Paul Lawrence
---
lib/test_kasan.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index ef1a3ac1397e..2724f86c4cef 100644
--- a/lib/test_kasan.c
+++ b/lib/test_kasan.c
@@ -472,6 +472,26 @
On Mon, Dec 04, 2017 at 08:59:35PM +0200, Marcus Wolf wrote:
>
> Am 04.12.2017 um 12:33 schrieb Dan Carpenter:
> > On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
> > > diff --git a/drivers/staging/pi433/pi433_if.h
> > > b/drivers/staging/pi433/pi433_if.h
> > > index 34ff0d4807bd
From: Alexander Potapenko
As a code-size optimization, LLVM builds since r279383 may
bulk-manipulate the shadow region when (un)poisoning large memory
blocks. This requires new callbacks that simply do an uninstrumented
memset().
This fixes linking the Clang-built kernel when using KASAN.
Sign
Hello,
On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote:
> diff --git a/drivers/thermal/of-thermal.c b/drivers/thermal/of-thermal.c
> index d04ec3b..e09f035 100644
> --- a/drivers/thermal/of-thermal.c
> +++ b/drivers/thermal/of-thermal.c
> @@ -30,7 +30,6 @@
> #include
> #include
On Mon, Dec 04, 2017 at 01:13:55PM -0600, Alan Tull wrote:
> Restrict which nodes are valid targets for a DT overlay.
>
> Add a flag bit to struct device_node allowing nodes to be marked as
> valid target for overlays.
>
> A driver that is always intended to handle DT overlays can
> enable overla
On Mon, Dec 04, 2017 at 09:12:52PM +0200, Marcus Wolf wrote:
>
>
> Am 04.12.2017 um 12:24 schrieb Dan Carpenter:
> > On Sun, Dec 03, 2017 at 04:17:25PM +0100, Simon Sandström wrote:
> > > Renames enum dataMode and its values packet, continuous, continuousNoSync
> > > to enum data_mode and PACKET,
Am 04.12.2017 um 21:15 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 08:37:51PM +0200, Marcus Wolf wrote:
Am 04.12.2017 um 12:37 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 01:17:37PM +0300, Dan Carpenter wrote:
Perhaps choose different function names if you want? You could do it
as s
On Mon, Dec 04, 2017 at 11:18:49AM -0800, Moritz Fischer wrote:
> On Mon, Dec 04, 2017 at 01:13:55PM -0600, Alan Tull wrote:
> > Restrict which nodes are valid targets for a DT overlay.
> >
> > Add a flag bit to struct device_node allowing nodes to be marked as
> > valid target for overlays.
> >
On Sat, Dec 02, 2017 at 09:36:41AM +, Yafang Shao wrote:
> The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other
> transitions are not traced with tcp_set_state tracepoint.
>
> In order to trace the whole tcp lifespans, two helpers are introduced,
> void __tcp_set_state(struct s
On Wed, Nov 15, 2017 at 2:51 PM, Alan Tull wrote:
Gentle reminder, this patch set is pretty straightforward, could use
some reviewing.
Alan
> This patch set goes on top of v6 of the non-dt support patchset that has
> been acked and I've asked Greg KH to send upstream.
>
> This patchset changes
Hi,
On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> As you reported that the PLL lock failure message is not printed, the
> failure can only come from either the extra delay introduced by the
> above loop, or from reading the HDMI_PHY_STAT0 register.
>
> How many iterations of the for loop e
The subject is way too long.
On Mon, Dec 04, 2017 at 08:18:51PM +0200, Marcus Wolf wrote:
> To increase the readability of the register accesses, the abstraction
> of the helpers was increased from simple read and write to set bit,
> reset bit and read modify write bit. In addition - according to
Second there might be the idea of supporting different chips in the future
(I already thought about).
Linux style is never to write code for the future.
Ok. I didn't know.
To be honest, I already started writing code, also supporting the rf12
some time ago, thus programming a rfxx.c, but neve
On Mon, Dec 04, 2017 at 03:40:56PM +0300, Kirill A. Shutemov wrote:
> We cannot proceed booting if the machine doesn't support the paging mode
> kernel was compiled for.
>
> Getting error the usual way -- via validate_cpu() -- is not going to
> work. We need to enable appropriate paging mode befor
Hi Nick,
On Monday, 4 December 2017 21:30:01 EET Nick Bowler wrote:
> On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> > As you reported that the PLL lock failure message is not printed, the
> > failure can only come from either the extra delay introduced by the
> > above loop, or from reading
On Mon, Dec 4, 2017 at 9:47 AM, Geert Uytterhoeven
wrote:
> The special overlay mutex is taken first, hence it should be released
> last in the error path.
>
> Move "mutex_lock(&of_mutex)" up, as suggested by Frank, as
> free_overlay_changeset() should be called with that mutex held if any
> non-t
On 04/12/2017 at 14:57:08 +0100, Peter Rosin wrote:
> The Axentia Nattis is a device designed for presenting departures for
> public transport systems. The Natte helper board provides power and
> features a battery of battery chargers.
>
> Signed-off-by: Peter Rosin
> ---
>
> This was part of a
On 30/11/2017 at 13:17:40 -0800, Guenter Roeck wrote:
> > I think it's a bugfix; it fixes real problems where the application
> > misbehave due to faulty content when reading from an eeprom. I'm
> > expecting to make a new release for the hw in question RSN and these
> > are the only local patches.
On Mon, Dec 04, 2017 at 12:11:22PM +0100, Gomonovych, Vasyl wrote:
> Hi Christoffer
>
> It is just syntax sugar of course
> and in mentioned function context it looks harmonically because it is
> in the end of function return statement.
> But in context of around source files it is looks not so ha
Am 04.12.2017 um 21:18 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 08:59:35PM +0200, Marcus Wolf wrote:
Am 04.12.2017 um 12:33 schrieb Dan Carpenter:
On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi4
On Mon, Dec 04, 2017 at 03:07:28PM +0100, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> The existing code was a mess, mainly because C arrays are nasty. Turn
> SYSENTER_stack into a struct, add a helper to find it, and do all the
> obvious cleanups this enables.
>
> Signed-off-by: Andy Lut
On Mon, Dec 04, 2017 at 09:22:06PM +0200, Marcus Wolf wrote:
>
>
> Am 04.12.2017 um 21:15 schrieb Dan Carpenter:
> >
> > That's a bad name, because it doesn't just enable it also disables.
> > Please split them.
> >
> > regards,
> > dan carpenter
> >
> >
>
> Same applies to all other stuff,
On 12/04/2017 10:32 AM, Dan Carpenter wrote:
> On Sat, Dec 02, 2017 at 10:05:20PM +0100, Tomas Marek wrote:
>> @@ -578,13 +546,9 @@ static irqreturn_t DIO1_irq_handler(int irq, void
>> *dev_id)
>> SET_CHECKED(rf69_set_mode(spi, standby)); /* this clears the
>> fifo */
>>
Hi Rob,
On Mon, Dec 4, 2017 at 8:35 PM, Rob Herring wrote:
> On Mon, Dec 4, 2017 at 9:47 AM, Geert Uytterhoeven
> wrote:
>> The special overlay mutex is taken first, hence it should be released
>> last in the error path.
>>
>> Move "mutex_lock(&of_mutex)" up, as suggested by Frank, as
>> free_ov
Commit-ID: e085ac7a6ddbd746966083c5e13aa290c3e9a253
Gitweb: https://git.kernel.org/tip/e085ac7a6ddbd746966083c5e13aa290c3e9a253
Author: Xie XiuQi
AuthorDate: Mon, 4 Dec 2017 17:54:37 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 20:38:44 +0100
x86/MCE: Extend table to re
Commit-ID: c8a4364c33ac7ed63278267b8f6d8c15810d5fd1
Gitweb: https://git.kernel.org/tip/c8a4364c33ac7ed63278267b8f6d8c15810d5fd1
Author: Yazen Ghannam
AuthorDate: Mon, 4 Dec 2017 17:54:38 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 20:38:44 +0100
x86/mce/AMD: Don't set
On Mon, Nov 27, 2017 at 9:15 PM, Wu Hao wrote:
> On Mon, Nov 27, 2017 at 10:28:04AM +, David Laight wrote:
>> From: Wu Hao
>> > Sent: 27 November 2017 06:42
>> > From: Zhang Yi
>> >
>> > The Intel FPGA device appears as a PCIe device on the system. This patch
>> > implements the basic framewo
On Mon, 4 Dec 2017 11:45:21 -0500, Prarit Bhargava wrote:
> On 12/04/2017 08:13 AM, Prarit Bhargava wrote:
> > x86: Booting SMP configuration:
> > node #0, CPUs:#1 #2 #3 #4
> > node #1, CPUs:#5 #6 #7 #8 #9
> > node #0, CPUs: #10 #11 #12 #13 #14
> > node
On Mon, Nov 13, 2017 at 09:08:48PM +, Alan Cox wrote:
> On Mon, 13 Nov 2017 18:42:50 +0100
> "Luis R. Rodriguez" wrote:
>
> > On Sat, Nov 11, 2017 at 02:32:40AM +, Alan Cox wrote:
> > > > My assumption here is:
> > > > 1) there are some less important and so security-insensitive firmwares
The AMD IOMMU specification Rev 3.00 (December 2016) introduces a
new Enhanced PPR Handling Support (EPHSup) bit in the MMIO register
offset 0030h (IOMMU Extended Feature Register).
When EPHSup=1, the IOMMU hardware requires the PPR bit of the
device table entry (DTE) to be set in order to support
When an unknown type event occurs, the default information written to
the syslog should dump raw event data. This could provide insight into
the event that occurred.
Signed-off-by: Gary R Hook
---
drivers/iommu/amd_iommu.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a
Simple but useful message log to the user in case of module appraise is
forced and fails due to the lack of file descriptor, that might be
caused by kmod calls to compressed modules.
Signed-off-by: Bruno E. O. Meneguele
---
security/integrity/ima/ima_main.c | 6 +-
1 file changed, 5 insertio
On Mon, Dec 04, 2017 at 03:53:32PM +0100, Rafael J. Wysocki wrote:
> Not really.
>
> This is generic code, so no thinkpad_acpi-specific stuff in this file, please,
> even under #ifdefs.
>
I have some ideas, and I want your confirmation if that would be
acceptable.
Can I do this:
Expose a new
On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
> Add a document for Intel FPGA driver overview.
>
> Signed-off-by: Enno Luebbers
> Signed-off-by: Xiao Guangrong
> Signed-off-by: Wu Hao
>
> v2: added FME fpga-mgr/bridge/region platform driver to driver organization.
> updated open disc
301 - 400 of 1242 matches
Mail list logo
