* Ard Biesheuvel wrote:
> On 25 October 2017 at 11:14, Ard Biesheuvel wrote:
> > The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
> >
> > Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
> >
> > are available in the git repository at:
> >
> >
Hi Sakari,
and thank you for your input - I've added a few comments below.
On 12/27/2017 07:00 PM, Sakari Ailus wrote:
> Hi Pavel,
>
> Thanks for the patch. Please see my comments below.
>
> On Wed, Dec 27, 2017 at 10:18:28AM +0100, Pavel Machek wrote:
>> From: Filip Matijević
>>
>> This
On Wed, Dec 27, 2017 at 07:02:27PM +0100, Eric Leblond wrote:
> Parse netlink ext attribute to get the error message returned by
> the card. Code is partially take from libnl.
>
> Signed-off-by: Eric Leblond
Acked-by: Alexei Starovoitov
On Wed, Dec 27, 2017 at 07:02:26PM +0100, Eric Leblond wrote:
> Most of the code is taken from set_link_xdp_fd() in bpf_load.c and
> slightly modified to be library compliant.
>
> Signed-off-by: Eric Leblond
Acked-by: Alexei Starovoitov
On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote:
> Get out of the loop when we have a match.
>
> Signed-off-by: Eric Leblond
> ---
> tools/lib/bpf/libbpf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index
On Wed, Dec 27, 2017 at 07:02:29PM +0100, Eric Leblond wrote:
> Signed-off-by: Eric Leblond
thank you.
Acked-by: Alexei Starovoitov
On Tue, Dec 26, 2017 at 06:32:05PM -0800, Alexei Starovoitov wrote:
> On Fri, Dec 22, 2017 at 06:50:01PM +, Quentin Monnet wrote:
> > Hi Roman,
> >
> > 2017-12-22 16:11 UTC+ ~ Roman Gushchin
> > > Bpftool build is broken with binutils version 2.28 and later.
> >
> > Could you check the
Did you try the patch I posted?
On Wed, Dec 27, 2017 at 10:25 AM, Dmitry Vyukov wrote:
> On Wed, Dec 6, 2017 at 4:44 PM, Dmitry Vyukov wrote:
>>> wrote:
On 10/24/2017 08:20 AM, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
>
I Mikhail Fridman. has selected you specially as one of my beneficiaries
for my Charitable Donation, Just as I have declared on May 23, 2016 to give
my fortune as charity.
Check the link below for confirmation:
Bpftool build is broken with binutils version 2.29 and later.
The cause is commit 003ca0fd2286 ("Refactor disassembler selection")
in the binutils repo, which changed the disassembler() function
signature.
Fix this by adding a new "feature" to the tools/build/features
infrastructure and make it
Bpftool determines it's own version based on the kernel
version, which is picked from the linux/version.h header.
It's strange to use the version of the installed kernel
headers, and makes much more sense to use the version
of the actual source tree, where bpftool sources are.
Fix this by
On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote:
> Did you try the patch I posted?
Hi Tom,
No. And I didn't know I need to. Why?
If you think the patch needs additional testing, you can ask syzbot to
test it. See
From: Al Cooper
Set PHY3_IDDQ_OVERRIDE in the xhci uninit routine. This will save
additional power when the XHCI driver is not enabled.
Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver")
Signed-off-by: Al Cooper
---
drivers/phy/broadcom/phy-brcm-usb-init.c | 2 ++
From: Al Cooper
This is caused by a bug in the BDC core. When the BDC core comes
out of reset and it's not selected, it gets a backup clock. When
the BDC core is selected, it get's the main clock. If HOST mode
is then selected the BDC core has the main clock shut off but
the backup clock is not
On Wed, Dec 27, 2017 at 3:09 AM, Fabio Estevam wrote:
> Hi Andrey,
>
> On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov
> wrote:
>> The system has an external watchdog in the environment processor
>> so the internal watchdog is of no use.
>>
>> Cc: Sascha Hauer
>> Cc: Fabio Estevam
>> Cc: Rob
Change "brcm,has_xhci" and "brcm,has_eohci" device tree properties
to the preferred "brcm,has-xhci" and "brcm,has-eohci". This also
matches the existing device tree bindings document.
Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver")
Signed-off-by: Al Cooper
---
From: Al Cooper
Enable the the Low Speed Keep Alive signal on the 7271b0 by setting
the LS_KEEP_ALIVE bit in the USB CTRL OBRIDGE register otherwise
some Dell Low Speed keyboards fail.
Also do a little cleanup of the EBRIDGE ESTOP_SCB_REQ bit. Since
this is only used on one platform, remove it
This patchset contains a series of bug fixes for the Broadcom
STB USB phy driver.
Al Cooper (4):
phy: usb: phy-brcm-usb: Fix two DT properties to match bindings doc
phy: usb: phy-brcm-usb-init: Some Low Speed keyboards fail on 7271
phy: usb: phy-brcm-usb-init: Power down USB 3.0 PHY when
From: "Steven Rostedt (VMware)"
To free the reader page that is allocated with ring_buffer_alloc_read_page(),
ring_buffer_free_read_page() must be called. For faster performance, this
page can be reused by the ring buffer to avoid having to free and allocate
new pages.
The issue arises when the
Hi Robin,
On Tue, Dec 19, 2017 at 04:34:46PM +, Robin Murphy wrote:
> Hi Tomasz,
>
> On 19/12/17 15:13, Tomasz Nowicki wrote:
> >Here is my lspci output of ThunderX2 for which I am observing kernel panic
> >coming from
> >SMMUv3 driver -> arm_smmu_write_strtab_ent() -> BUG_ON(ste_live):
> >
Linus,
While doing tests on tracing over the network, I found that the packets
were getting corrupted. In the process I found three bugs. One was the
culprit, but the other two scared me. After deeper investigation, they
were not as major as I thought they were, due to a signed compared to
an
On Wed, Dec 27, 2017 at 3:11 AM, Fabio Estevam wrote:
> Hi Andrey,
>
> On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov
> wrote:
>> The RTC is manufactured by Maxim. This is a cosmetic fix, as Linux
>> doesn't match the vendor string for i2c devices.
>>
>> Cc: Sascha Hauer
>> Cc: Fabio Estevam
From: "Steven Rostedt (VMware)"
Two info bits were added to the "commit" part of the ring buffer data page
when returned to be consumed. This was to inform the user space readers that
events have been missed, and that the count may be stored at the end of the
page.
What wasn't handled, was the
From: "Steven Rostedt (VMware)"
Jing Xia and Chunyan Zhang reported that on failing to allocate part of the
tracing buffer, memory is freed, but the pointers that point to them are not
initialized back to NULL, and later paths may try to free the freed memory
again. Jing and Chunyan fixed one of
From: "Steven Rostedt (VMware)"
The ring_buffer_read_page() takes care of zeroing out any extra data in the
page that it returns. There's no need to zero it out again from the
consumer. It was removed from one consumer of this function, but
read_buffers_splice_read() did not remove it, and
From: Jing Xia
Double free of the ring buffer happens when it fails to alloc new
ring buffer instance for max_buffer if TRACER_MAX_TRACE is configured.
The root cause is that the pointer is not set to NULL after the buffer
is freed in allocate_trace_buffers(), and the freeing of the ring
buffer
From: Linus Torvalds
Date: Wed, 27 Dec 2017 11:41:30 -0800
Subject: [PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)
Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned up
and unified the IDT invalidation that existed in a couple of places. It
changed no
Hi Tejun,
In my previous messages, I think the message "memsw improves the
performance of the job" might have been conveyed. Please ignore that.
The message I want to express is the "memsw provides users the ability
to consistently limit their job's memory (specifically anon memory)
irrespective
On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel
wrote:
> diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S
> index 7da3e5c366a0..49ae5b43fe2b 100644
> --- a/arch/arm64/kernel/vmlinux.lds.S
> +++ b/arch/arm64/kernel/vmlinux.lds.S
> @@ -156,7 +156,7 @@ SECTIONS
>
On Wed, 27 Dec 2017, Linus Torvalds wrote:
> From: Linus Torvalds
> Date: Wed, 27 Dec 2017 11:41:30 -0800
> Subject: [PATCH] x86-32: fix kexec with stack canary
> (CONFIG_CC_STACKPROTECTOR)
>
> Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned up
> and unified the IDT
On 27 December 2017 at 19:54, Linus Torvalds
wrote:
> On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel
> wrote:
>> diff --git a/arch/arm64/kernel/vmlinux.lds.S
>> b/arch/arm64/kernel/vmlinux.lds.S
>> index 7da3e5c366a0..49ae5b43fe2b 100644
>> --- a/arch/arm64/kernel/vmlinux.lds.S
>> +++
Hi!
> > +Required properties:
> > +- compatible: "avago,apds990x"
> > +- reg: address on the I2C bus
> > +- interrupts: external interrupt line number
> > +- Vdd-supply: power supply for VDD
> > +- Vled-supply: power supply for LEDA
>
> AFAIK the custom is to use lower case letters for regulator
On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel
wrote:
> diff --git a/include/linux/compiler.h b/include/linux/compiler.h
> index 52e611ab9a6c..fe752d365334 100644
> --- a/include/linux/compiler.h
> +++ b/include/linux/compiler.h
> @@ -327,4 +327,15 @@ static __always_inline void
On 27 December 2017 at 20:07, Linus Torvalds
wrote:
> On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel
> wrote:
>> diff --git a/include/linux/compiler.h b/include/linux/compiler.h
>> index 52e611ab9a6c..fe752d365334 100644
>> --- a/include/linux/compiler.h
>> +++ b/include/linux/compiler.h
>> @@
On Wed, Dec 27, 2017 at 10:55:32AM +0800, kernel test robot wrote:
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
> [5.903660] tpm_tis 00:05: 1.2 TPM (device-id 0xFE, rev-id 70)
> [5.934271] tpm tpm0: A TPM error (7) occurred attempting to
On Wed, 27 Dec 2017, Michel Dänzer wrote:
> On 2017-12-27 03:51 PM, Julia Lawall wrote:
> > PP_ASSERT_WITH_CODE prints a newline at the end of the message string,
> > so the message string does not need to include a newline explicitly.
> > Done using Coccinelle.
> >
> > Signed-off-by: Julia
On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel
wrote:
>
> I tried to keep the generic patches generic, so perhaps I should just
> put the arm64 vmlinux.lds.S change in a patch on its own?
I guess it doesn't matter, but regardless of where it gets introduced
I would like to see the explanation
On Wed, Dec 27, 2017 at 9:08 PM, Ozgur wrote:
>
>
> 27.12.2017, 22:21, "Dmitry Vyukov" :
>> On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote:
>>> Did you try the patch I posted?
>>
>> Hi Tom,
>
> Hello Dmitry,
>
>> No. And I didn't know I need to. Why?
>> If you think the patch needs
On Wed, 2017-12-27 at 10:36 +, Mark Brown wrote:
> On Tue, Dec 26, 2017 at 06:45:28PM +, Trent Piepho wrote:
>
> > Or, since this only fixes instances of DMA-unsafe buffers used in
> > access to SPI NOR flash chips, and since there are other SPI master
> > interface users, those chip
Hello Mahesh,
On 27 December 2017 at 18:09, Mahesh Bandewar (महेश बंडेवार)
wrote:
> Hello James,
>
> Seems like I missed your name to be added into the review of this
> patch series. Would you be willing be pull this into the security
> tree? Serge Hallyn has already ACKed it.
We seem to have
On 27 December 2017 at 20:13, Linus Torvalds
wrote:
> On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel
> wrote:
>>
>> I tried to keep the generic patches generic, so perhaps I should just
>> put the arm64 vmlinux.lds.S change in a patch on its own?
>
> I guess it doesn't matter, but regardless
Hi Romain,
Le 27/12/2017 à 15:46, Romain Porte a écrit :
> On 27/12/2017 14:58, Romain Porte wrote:
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
>> index 8bafd462f..18e826d36 100644
>> --- a/drivers/mtd/spi-nor/spi-nor.c
>> +++ b/drivers/mtd/spi-nor/spi-nor.c
>>
Hello,
On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote:
> On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote:
> > Get out of the loop when we have a match.
> >
> > Signed-off-by: Eric Leblond
> > ---
> > tools/lib/bpf/libbpf.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
Hi!
> > Would you list guarantees provided by SGX?
>
> Obviously, confidentiality and integrity. SGX was designed to address
> an Iago threat model, a very difficult challenge to address in
> reality.
Do you have link on "Iago threat model"?
> I don't have the citation immediately available,
On Sat, 23 Dec 2017, Paul E. McKenney wrote:
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index ffebcf878fba..94cce780c574 100644
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -1875,6 +1875,7 @@ int timers_dead_cpu(unsigned int cpu)
>
>
On Wed, 27 Dec 2017, Thomas Gleixner wrote:
> Bah, no. We need to move that into the nohz logic somehow to prevent that
> repetitive expiry yesterday reprogramming. Lemme think about it some more.
The patch below should be the proper cure.
Thanks,
tglx
8<---
Subject:
Hi!
In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few
seconds, but then I get repeated oopses.
On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786),
camera does not start.
Any ideas what might be wrong there?
From: Markus Elfring
Date: Wed, 27 Dec 2017 22:04:22 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/pinctrl/qcom/pinctrl-msm.c | 5 ++---
1 file changed, 2
On Wed, Dec 27, 2017 at 07:50:42PM +0100, Filip Matijević wrote:
> Hi Sakari,
>
> and thank you for your input - I've added a few comments below.
>
> On 12/27/2017 07:00 PM, Sakari Ailus wrote:
> > Hi Pavel,
> >
> > Thanks for the patch. Please see my comments below.
> >
> > On Wed, Dec 27,
On Wed, Dec 27, 2017 at 09:01:47PM +0100, Pavel Machek wrote:
> Hi!
>
> > > +Required properties:
> > > +- compatible: "avago,apds990x"
> > > +- reg: address on the I2C bus
> > > +- interrupts: external interrupt line number
> > > +- Vdd-supply: power supply for VDD
> > > +- Vled-supply: power
On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote:
> Hi!
>
> In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few
> seconds, but then I get repeated oopses.
>
> On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786),
> camera does not start.
>
>
On Thu 2017-12-07 09:42:29, Rob Herring wrote:
> On Wed, Dec 6, 2017 at 4:32 PM, Dan Murphy wrote:
> > Rob
> >
> > On 12/06/2017 03:52 PM, Rob Herring wrote:
> >> On Tue, Dec 05, 2017 at 07:36:37AM -0600, Dan Murphy wrote:
> >>> Fix the address-cells and size-cells example node
> >>> to reflect
Fixed several coding style warnings of "please, no space before tabs".
Signed-off-by: Jianshen Liu
---
drivers/staging/ipx/af_ipx.c| 56 -
drivers/staging/ipx/ipx_proc.c | 2 +-
drivers/staging/ipx/ipx_route.c | 6 ++---
3 files changed, 32
On Tue, Dec 26, 2017 at 10:45 PM, Viresh Kumar wrote:
> On 26-12-17, 14:23, Rob Herring wrote:
>> > cpu_opp_table: cpu_opp_table {
>> > compatible = "operating-points-v2";
>> > opp-shared;
>> >
>> > opp00 {
>> >
Dmitry Vyukov wrote:
> On Wed, Dec 27, 2017 at 7:18 PM, syzbot
> wrote:
> > Hello,
> >
> > syzkaller hit the following crash on
> > beacbc68ac3e23821a681adb30b45dc55b17488d
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> > compiler: gcc (GCC) 7.1.1 20170620
> >
From: Markus Elfring
Date: Wed, 27 Dec 2017 22:34:28 +0100
Omit extra messages for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/pinctrl/spear/pinctrl-plgpio.c | 8 ++--
1 file changed, 2
1;2802;0cOn Wed 2017-12-27 23:17:19, Sakari Ailus wrote:
> On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote:
> > Hi!
> >
> > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few
> > seconds, but then I get repeated oopses.
> >
> > On v4.15-rc0.5 (commit
Hi Rob,
+ Ludovic Desroches, maintainer of the DMA controller drivers for AT91 SoCs.
Le 27/12/2017 à 00:23, Rob Herring a écrit :
> On Sun, Dec 24, 2017 at 05:36:05AM +0100, Cyrille Pitchen wrote:
>> The optional 'dmacap,memcpy' DT property tells the Atmel QSPI controller
>> driver to reserve
Hi Yong,
On Thu, Dec 21, 2017 at 10:49:35AM +0800, Yong wrote:
> Hi,
>
> On Tue, 19 Dec 2017 13:53:28 +0200
> Sakari Ailus wrote:
>
> > Hi Yong,
> >
> > On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote:
> > > Add binding documentation for Allwinner V3s CSI.
> > >
> > >
From: Markus Elfring
Date: Wed, 27 Dec 2017 22:44:04 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/pinctrl/spear/pinctrl-spear.c | 4 +---
1 file changed, 1
Łukasz,
On Wed, Dec 27, 2017 at 11:12 AM, Łukasz Stelmach
wrote:
> It was <2017-12-22 pią 19:30>, when Philippe Ombredanne wrote:
>> On Fri, Dec 22, 2017 at 5:38 PM, Łukasz Stelmach
>> wrote:
>>> It was <2017-12-22 pią 14:34>, when Philippe Ombredanne wrote:
Łukasz,
On Fri, Dec
On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar wrote:
> On 26-12-17, 14:29, Rob Herring wrote:
>> On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote:
>
>> > +On some platforms the exact frequency or voltage may be hidden from the
>> > OS by
>> > +the firmware and the "opp-hz" or the
On Wed, Dec 27, 2017 at 4:20 AM, Sricharan R wrote:
> Hi Rob,
>
> On 12/26/2017 11:06 PM, Rob Herring wrote:
>> On Thu, Dec 21, 2017 at 5:53 AM, Sricharan R
>> wrote:
>>> Hi Rob,
>>>
>>> On 12/21/2017 2:48 AM, Rob Herring wrote:
On Wed, Dec 20, 2017 at 11:55:33AM +0530, Sricharan R wrote:
On 2017-12-27 14:50, Bartosz Golaszewski wrote:
> Current description of the compatible property for at24 is quite vague.
>
> State explicitly that any "," pair is accepted as
> long as one of the listed strings is used as fallback.
>
> Signed-off-by: Bartosz Golaszewski
> ---
>
This patch adds one more generic PHY mode to the phy_mode enum, to allow
configuring generic PHYs to the 2.5G SGMII mode by using the set_mode
callback.
Signed-off-by: Antoine Tenart
---
include/linux/phy/phy.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/phy/phy.h
Hi all,
This series adds 1000BaseX and 2500BaseX support to the Marvell PPv2
driver. In order to use it, the 2.5 SGMII mode is added in the Marvell
common PHY driver (cp110-comphy).
Thanks to theses patches the fourth network interface can be used on the
mcbin, and two patches are attached: one
From: Yan Markman
This patch adds Ethernet aliases in the Marvell Aramada 7040 DB, 8040 DB
and 8040 mcbin device trees so that the bootloader setup the MAC
addresses correctly.
Signed-off-by: Yan Markman
[Antoine: commit message, small fixes]
Signed-off-by: Antoine Tenart
---
This patch adds the 1000Base-X PHY mode support in the Marvell PPv2
driver. 1000Base-X is quite close the SGMII and uses nearly the same
code path.
Signed-off-by: Antoine Tenart
---
drivers/net/ethernet/marvell/mvpp2.c | 45
1 file changed, 35 insertions(+),
This patch allow the CP100 comphy to configure some lanes in the
2.5G SGMII mode. This mode is quite close to SGMII and uses nearly the
same code path.
Signed-off-by: Antoine Tenart
---
drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 17 ++---
1 file changed, 14 insertions(+), 3
This patch adds the 2500Base-X PHY mode support in the Marvell PPv2
driver. 2500Base-X is quite close to 1000Base-X and SGMII modes and uses
nearly the same code path.
Signed-off-by: Antoine Tenart
---
drivers/net/ethernet/marvell/mvpp2.c | 40
1 file
This patch enables the fourth network interface on the Marvell
Macchiatobin. It is configured in the 2500Base-X PHY mode.
Signed-off-by: Antoine Tenart
---
arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 8
1 file changed, 8 insertions(+)
diff --git
On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote:
> This patch enables the fourth network interface on the Marvell
> Macchiatobin. It is configured in the 2500Base-X PHY mode.
>
> Signed-off-by: Antoine Tenart
> ---
> arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 8
On Tue, Dec 26, 2017 at 06:20:54PM +0530, Kishon Vijay Abraham I wrote:
> Hi Niklas,
Hello Kishon
>
> On Wednesday 20 December 2017 04:59 AM, Niklas Cassel wrote:
> > Add a generic function for raising MSI irqs that can be used by all
> > DWC based controllers.
> >
> > Note that certain
Hi Russell,
On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote:
> On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote:
> >
> > +_eth2 {
> > + /* CPS Lane 5 */
> > + status = "okay";
> > + phy-mode = "2500base-x";
> > + /* Generic PHY, providing serdes
On 12/26/17 9:56 PM, Masami Hiramatsu wrote:
On Tue, 26 Dec 2017 17:57:32 -0800
Alexei Starovoitov wrote:
On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote:
Check whether error injectable event is on function entry or not.
Currently it checks the event is ftrace-based kprobes
From: Andi Kleen
Tommi reports:
I'm seeing this kmemleak report in v4.15-rc4:
unreferenced object 0x8801f3d5d720 (size 64):
comm "swapper/0", pid 1, jiffies 4294667312 (age 2687.423s)
hex dump (first 32 bytes):
60 d1 41 ad ff ff ff ff 20 d1 41 ad ff ff ff ff `.A. .A.
On 12/27/17 12:09 AM, Masami Hiramatsu wrote:
On Tue, 26 Dec 2017 18:12:56 -0800
Alexei Starovoitov wrote:
On Tue, Dec 26, 2017 at 04:48:25PM +0900, Masami Hiramatsu wrote:
Support in-kernel fault-injection framework via debugfs.
This allows you to inject a conditional error to specified
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
There already a "dev" variable for that. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc:
There's "dev" variable for this already. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc:
Simplify code a bit by using of_device_get_match_data() instead of
of_match_device().
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Looks like commas were accidentally used where semicolons were
supposed to be. Fix that.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
There's already "dev" variable for that. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Add code to allow avoid having nvmem core append a numeric suffix to
the end of the name by passing config->id of -1.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Srinivas, all:
This patchset contains various small changes that I recently made to
NVMEM, more specifically:
- Patches 1 and 2 are two changes I am hoping are acceptable upstream
- Patches 3 to 14 are a follow up to patch 2
- Patches 15 to 20 are just trivial fixups and I am more than
There's "dev" variable for this already. Use it.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: linux-media...@lists.infradead.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc:
Introduce devm_nvmem_register()/devm_nvmem_unregister() to make
.remove() unnecessary in trivial drivers.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: Matthias Brugger
Cc: Joachim Eastwood
Cc: cphe...@gmail.com
Cc:
On 12/27/2017 09:30 PM, Eric Leblond wrote:
> On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote:
>> On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote:
>>> Get out of the loop when we have a match.
>>>
>>> Signed-off-by: Eric Leblond
>>> ---
>>> tools/lib/bpf/libbpf.c | 1 +
On 12/22/2017 07:12 PM, Jann Horn wrote:
> This checks that it is not possible to bypass the total stack size check in
> update_stack_depth() by calling a function that uses a large amount of
> stack memory *before* using a large amount of stack memory in the caller.
>
> Currently, the first
801 - 900 of 1006 matches
Mail list logo
