Hi Arnaldo,
This commit seems to be causing a regression:
$ ./perf trace record -g ls
Perf compiled from acme/perf/core:
$ ./perf trace -i perf.data
0.200 ( 0.016 ms): ls/19722 brk(
0.367 ( 0.024 ms): ls/19722 access(filename: 0xa
On Mon, Jan 29, 2018 at 1:34 AM, Chintan Pandya wrote:
>
>> I was curious, so I implemented it. It ends up being similar to Rasmus's
>> 1st suggestion. The difference is we don't try to store all entries, but
>> rather implement a hash table that doesn't handle collisions. Relying on
>> the fact t
On Wed, Jan 24, 2018 at 02:58:01PM +, Colin King wrote:
> From: Colin Ian King
>
> The pointer ln is assigned a value that is never read, it is re-assigned
> a new value in the list_for_each loop hence the initialization is
> redundant and can be removed.
>
> Cleans up clang warning:
> drive
2018-01-29 18:39 GMT+08:00 Jiri Olsa :
> On Sun, Jan 28, 2018 at 01:31:48PM +0800, weiping zhang wrote:
>> if use -G with one cgroup and -e with multiple events, only the first
>> event has correct cgroup setting, all events from the second will track
>> system-wide events.
>>
>> if user want track
From: Will Deacon
> Sent: 29 January 2018 13:20
...
> Another issue with this style of macro definition exists on architectures
> where the calling convention needs you to carry state around depending on
> how you packed the previous parameters. For example, on 32-bit ARM, 64-bit
> values are passe
Hi Chris,
Could you test following patch?
DECLARE_RTL_COND(rtl_ocp_tx_cond)
{
void __iomem *ioaddr = tp->mmio_addr;
- return RTL_R8(IBISR0) & 0x02;
+ return RTL_R8(IBISR0) & 0x20;
}
static void rtl8168ep_stop_cmac(struct rtl8169_private *tp)
{
void __iomem *io
Commit-ID: 8de50dc26278a05363781514beb092a366c84654
Gitweb: https://git.kernel.org/tip/8de50dc26278a05363781514beb092a366c84654
Author: Benjamin Gaignard
AuthorDate: Thu, 30 Nov 2017 09:45:00 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 29 Jan 2018 16:24:53 +0100
irqchip/stm32: Fi
On Mon, 29 Jan 2018 02:10:26 +0100
Frederic Weisbecker wrote:
> On Wed, Jan 24, 2018 at 10:46:08AM -0500, Luiz Capitulino wrote:
> > On Fri, 19 Jan 2018 01:02:14 +0100
> > Frederic Weisbecker wrote:
> >
> > > Ingo,
> > >
> > > Please pull the sched/0hz-v2 branch that can be found at:
> > >
On 01/29/2018 12:40 AM, Daniel Borkmann wrote:
> On 01/28/2018 03:45 PM, Greg KH wrote:
>> On Wed, Jan 24, 2018 at 11:10:50AM +0100, Daniel Borkmann wrote:
>>> On 01/24/2018 11:07 AM, David Woodhouse wrote:
On Tue, 2018-01-09 at 22:39 +0100, Daniel Borkmann wrote:
> On 01/09/2018 07:04 PM,
On Fri, Jan 19, 2018 at 01:02:18AM +0100, Frederic Weisbecker wrote:
> When a CPU runs in full dynticks mode, a 1Hz tick remains in order to
> keep the scheduler stats alive. However this residual tick is a burden
> for bare metal tasks that can't stand any interruption at all, or want
> to minimiz
On Fri, Jan 19, 2018 at 01:02:18AM +0100, Frederic Weisbecker wrote:
> + queue_delayed_work(system_unbound_wq, dwork, HZ);
Also, why HZ ? No clues were given.
On Mon, Jan 29, 2018 at 06:07:58PM +0300, Kirill A. Shutemov wrote:
> + /*
> + * We are in 5-level paging mode, but we want to switch to 4-level.
> + * Let's take the first entry in the top-level page table as our new
> CR3.
> + */
> + movl%cr3, %eax
> + movl(%ea
On Sun, Jan 28, 2018 at 11:20 PM, Benjamin Poirier wrote:
> On 2018/01/26 08:50, Alexander Duyck wrote:
>> On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote:
>> > This reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d.
>> >
>> > We keep the fix for the first part of the problem (1) de
On Tue, 2018-01-23 at 10:32 +0200, Andy Shevchenko wrote:
> On Mon, 2018-01-22 at 16:46 -0800, h...@zytor.com wrote:
> > On January 22, 2018 4:32:14 PM PST, "Mehta, Sohil"
> > wrote:
> > > On Fri, 2018-01-19 at 16:33 +0200, Andy Shevchenko wrote:
> > > > +build_mmio_read(readq, "q", unsigned long
On Mon, Jan 29, 2018 at 03:03:59PM +0200, Andy Shevchenko wrote:
> Instead of home grown function let's use what library provides us.
>
> Signed-off-by: Andy Shevchenko
Acked-by: Jiri Olsa
thanks,
jirka
> ---
> - recend after couple of years of silence
> - hopefully it will be commented / acc
On Mon, Jan 29, 2018 at 02:10:26AM +0100, Frederic Weisbecker wrote:
> It's beyond the scope of this patchset but indeed that's right, I run my
> kernels with tsc=reliable because my CPUs don't have the TSC_RELIABLE flag.
> That's the only way I found to shutdown the tick completely on my test
> m
On Sun, Jan 28, 2018 at 11:21 PM, Benjamin Poirier wrote:
> On 2018/01/26 09:03, Alexander Duyck wrote:
>> On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote:
>> > This reverts commit 19110cfbb34d4af0cdfe14cd243f3b09dc95b013.
>> > This reverts commit 4110e02eb45ea447ec6f5459c9934de0a273fb91.
On Mon, Jan 29, 2018 at 10:33:16AM -0500, Luiz Capitulino wrote:
> Cool, passing tsc=reliable worked for me. I finally got to the tick to
> go completely away. While I agree that fixing that is beyond the scope
> of this series, I think we should improve it anyway since it will probably
> come up f
On Mon, Jan 29, 2018 at 04:31:42PM +0200, Oleksandr Shamray wrote:
> Initial patch for JTAG driver
> JTAG class driver provide infrastructure to support hardware/software
> JTAG platform drivers. It provide user layer API interface for flashing
> and debugging external devices which equipped with J
On Mon, Jan 29, 2018 at 11:07:35AM +0800, Jianchao Wang wrote:
> nvme_set_host_mem will invoke nvme_alloc_request without NOWAIT
> flag, it is unsafe for nvme_dev_disable. The adminq driver tags
> may have been used up when the previous outstanding adminq requests
> cannot be completed due to some
The CIR Pin of the A83T is located at PL12.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a83t.dtsi
b/arch/arm/boot/dts/sun8i-a83t.dtsi
index de5119a2a91c..06e96db7c41a 100644
--- a/arch/arm/b
This patch series adds support for the sunxi A83T ir module and enhances
the sunxi-ir driver. Right now the base clock frequency for the ir driver
is a hard coded define and is set to 8 MHz.
This works for the most common ir receivers. On the Sinovoip Bananapi M3
the ir receiver needs, a 3 MHz ba
The size of the register should be the size of the whole memory block,
not just the registers, that are needed.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sunxi-h3-h5.dtsi
b/arch/arm/
The Bananapi M3 has an onboard IR receiver.
This enables the onboard IR receiver subnode.
Unlike the other IR receivers this one needs a base clock frequency
of 300 Hz (3 MHz), to be able to work.
Signed-off-by: Philipp Rossak
Acked-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a83t-bananapi
This patch updates the sunxi-ir driver to set the base clock frequency from
devicetree.
This is necessary since there are different ir receivers on the
market, that operate with different frequencies. So this value could be
set if the attached ir receiver needs a different base clock frequency,
th
The cir interface is like on the H3 located at 0x01f02000 and is exactly
the same. This patch adds support for the ir interface on the A83T.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i
This patch updates documentation for Device-Tree bindings for sunxi IR
controller and adds the new optional property for the base clock
frequency.
Signed-off-by: Philipp Rossak
Acked-by: Maxime Ripard
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/media/sunxi-ir.txt | 3 +++
1
Hi Ingo, Hi Peter,
Please let me know if you find anything that prevents you from integrating
this patchset into the scheduler tree.
Thanks,
Mathieu
- On Jan 23, 2018, at 10:57 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Hi Ingo, Peter, Thomas,
>
> Here is the updated
if use -G with one cgroup and -e with multiple events, only the first
event has correct cgroup setting, all events from the second will track
system-wide events.
if user want track multiple events for a specific cgroup, user must give
parameters like follow:
$ perf stat -e e1 -e e2 -e e3 -G test,t
On 01/26/2018 07:02 AM, Alexandre Courbot wrote:
> Document how the request API can be used along with the existing V4L2
> interface.
>
> Signed-off-by: Alexandre Courbot
> ---
> Documentation/media/uapi/v4l/buffer.rst | 10 +-
> Documentation/media/uapi/v4l/common.rst | 1 +
> Docu
On 01/26/2018 07:02 AM, Alexandre Courbot wrote:
> From: Laurent Pinchart
>
> The media request API is made of a new ioctl to implement request
> management. Document it.
>
> Signed-off-by: Laurent Pinchart
> [acour...@chromium.org: adapt for newest API]
> Signed-off-by: Alexandre Courbot
> --
On Tue, Jan 16, 2018 at 05:06:15PM +0100, Peter Rosin wrote:
> Makes them easier to find.
>
> Signed-off-by: Peter Rosin
> ---
> Documentation/devicetree/bindings/eeprom/at24.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This one should go into 4.16. I can apply after rc1 or apply
On Tue, Jan 16, 2018 at 05:06:16PM +0100, Peter Rosin wrote:
> The datasheet talks about the chip being an spd, but the chip is writable
> so atmel,24c02 is more appropriate as fallback.
>
> Signed-off-by: Peter Rosin
> ---
> Documentation/devicetree/bindings/eeprom/at24.txt | 1 +
> 1 file chan
On Tue, Jan 16, 2018 at 07:02:34PM +, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> When Linux is master of BAM, it can directly read registers to know number
> of supported channels, however when its remotely controlled reading these
> registers would trigger a crash
Upgraded some of my older machines to v4.15 today. On a quad P3 HP
NetServer, I get a bootup warning at kernel/irq/chip.c:244
__irq_startup+0x80/0x100 (full dmesg below). It seems it was there
before but I did not notice it.
Reading older kernel logs, I found that up to
4.15.0-rc4-00041-gace52
Release of iproute2 for Linux 4.15
Update to iproute2 utility to support new features in Linux 4.15.
This release ands more JSON output and fixes some bugs that JSON
code introduced. Also more updates to active developing subsystems
such as devlink and bpf.
The tarball can be dowloaded from:
ht
On Tue, Jan 16, 2018 at 07:02:36PM +, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> When Linux is master of BAM, it can directly read registers to know number
> of supported execution enviroments, however when its remotely controlled
> reading these registers would tri
> -Original Message-
> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> Sent: Saturday, January 27, 2018 8:51 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; andy.shevche...@gmail.com; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; l...@kernel.org;
> quasi...
On Tue, Jan 16, 2018 at 10:31:28PM +0100, Krzysztof Kozlowski wrote:
> Fix DTC warnings like:
>
> arch/arm/boot/dts/exynos4412-trats2.dtb: Warning (simple_bus_reg):
> Node /soc/syscon-poweroff missing or empty reg/ranges property
> arch/arm/boot/dts/exynos4412-trats2.dtb: Warning (
On Mon, 29 Jan 2018 16:54:31 +0100
Peter Zijlstra wrote:
> On Mon, Jan 29, 2018 at 10:33:16AM -0500, Luiz Capitulino wrote:
> > Cool, passing tsc=reliable worked for me. I finally got to the tick to
> > go completely away. While I agree that fixing that is beyond the scope
> > of this series, I t
From: Kan Liang
There is a bug when mmap read event->count with large PEBS enabled.
Here is an example.
#./read_count
0x71f0
0x122c0
0x11c54
0x10001257d
0x2bdc5
In fixed period mode, the auto-reload mechanism could be enabled for
PEBS events. But the calculation of even
From: Kan Liang
--
Changes since V2:
- Refined the changelog
- Introduced specific read function for large PEBS.
The previous generic PEBS read function is confusing.
Disabled PMU in pmu::read() path for large PEBS.
Handled the corner case when reload_times == 0.
- Modified the p
From: Kan Liang
The userspace RDPMC usage never works for large PEBS since the large
PEBS is introduced by
commit b8241d20699e ("perf/x86/intel: Implement batched PEBS interrupt
handling (large PEBS interrupt threshold)")
When the PEBS interrupt threshold is larger than one, there is no way to
g
Dear Masami,
Thank you so much for your reply.
Please find some of my answers inline.
On Mon, Jan 29, 2018 at 7:47 PM, Masami Hiramatsu wrote:
> On Mon, 29 Jan 2018 13:40:34 +0530
> Pintu Kumar wrote:
>
>> Hi All,
>>
>> 'perf probe' is failing sometimes on 4.9.20 with AMD-64.
>> # perf probe -
On Mon 29-01-18 16:29:42, Roger He wrote:
> ttm module needs it to determine its internal parameter setting.
Could you be more specific why?
> Signed-off-by: Roger He
> ---
> include/linux/swap.h | 6 ++
> mm/swapfile.c| 15 +++
> 2 files changed, 21 insertions(+)
>
>
From: Kan Liang
Large PEBS needs to be specially handled in event count read.
It is only available for intel_pmu.
Only need to specially handle the large PEBS. For the threshold is one,
even auto-reload is enabled, it doesn't need to be specially handled.
Because,
- auto-reload is only effect w
From: Kan Liang
When the PEBS interrupt threshold is larger than one, there is no way to
get exact auto-reload times and value, which needed for event update
unless flush the PEBS buffer.
Introduce intel_pmu_large_pebs_read() to drain the PEBS buffer in event
read when large PEBS is enabled.
To
From: Christian Brauner
Date: Wed, 24 Jan 2018 15:26:31 +0100
> Based on the previous discussion this enables passing a IFLA_IF_NETNSID
> property along with RTM_SETLINK and RTM_DELLINK requests. The patch for
> RTM_NEWLINK will be sent out in a separate patch since there are more
> corner-cases
From: Kan Liang
Large PEBS needs to be specially handled in event count read.
Signed-off-by: Kan Liang
---
arch/x86/events/core.c | 2 ++
arch/x86/events/perf_event.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 140d332..acd7
Hi Alban,
On Thu, 2018-01-25 at 06:56 -0500, Mimi Zohar wrote:
> > > @@ -228,9 +229,28 @@ static int process_measurement(struct file *file,
> > > char *buf, loff_t size,
> > >IMA_APPRAISE_SUBMASK | IMA_APPRAISED_SUBMASK |
> > >IMA_ACTION_FLA
On 2018-01-28 08:22, Segher Boessenkool wrote:
On Fri, Jan 26, 2018 at 04:59:46PM -0800, Prasad Sodagudi wrote:
Disable -Wunused-const-variable warnings instead of
disabling -Wunused-variable warnings, So that in both
clang and GCC -Wunused-const-variable gets disabled.
Why would you disable -
On Thu, Jan 25, 2018 at 04:57:22PM +, Suzuki K Poulose wrote:
> On 25/01/18 15:36, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 03:38:37PM +, Suzuki K Poulose wrote:
> >>On 23/01/18 14:52, Dave Martin wrote:
> >>>On Tue, Jan 23, 2018 at 12:27:54PM +, Suzuki K Poulose wrote:
> From:
On Mon, 29 Jan 2018, Meelis Roos wrote:
> Upgraded some of my older machines to v4.15 today. On a quad P3 HP
> NetServer,
Your supply of vintage hardware is amazing.
> I get a bootup warning at kernel/irq/chip.c:244
> __irq_startup+0x80/0x100 (full dmesg below). It seems it was there
> before
On Tue, Jan 23, 2018 at 06:08:45PM +, Patrick Bellasi wrote:
> +static inline void util_est_dequeue(struct task_struct *p, int flags)
> +{
> + struct cfs_rq *cfs_rq = &task_rq(p)->cfs;
> + unsigned long util_last = task_util(p);
> + bool sleep = flags & DEQUEUE_SLEEP;
> + unsign
On Mon, Jan 29, 2018 at 1:13 AM, H. Peter Anvin wrote:
> On 01/28/18 11:21, Andy Lutomirski wrote:
>>>
>>> I think the bug is here. I think that, when writing a NULL selector
>>> to DS, ES, FS, or GS, Intel CPUs incorrectly set DPL == RPL, whereas
>>> they should set DPL to 3.
>>
>> As an experim
From: Stanislav Lanci
This patch allow to enable x86 feature TOPOEXT. This is needed to provide
information about SMT on AMD Zen CPUs to the guest.
Signed-off-by: Stanislav Lanci
Tested-by: Nick Sarnie
Reviewed-by: Paolo Bonzini
Signed-off-by: Babu Moger
---
Rebased on top of linux-next.
Ma
On Monday 29 January 2018 15:18:42 Andy Shevchenko wrote:
> +Cc: Pali, who AFAIRC is interested in FAT labeling mess.
Yes, please CC me for FAT labeling discussing in future.
> On Wed, Jan 17, 2018 at 12:43 PM, ChenGuanqiao
> wrote:
>
> Commit message?
>
> > Signed-off-by: ChenGuanqiao
>
> >
On Monday 29 January 2018 16:22:07 mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Pali Rohár [mailto:pali.ro...@gmail.com]
> > Sent: Saturday, January 27, 2018 8:51 AM
> > To: Limonciello, Mario
> > Cc: dvh...@infradead.org; andy.shevche...@gmail.com; linux-
> > ker...@
On Sun, Jan 28, 2018 at 10:33 AM, Ingo Molnar wrote:
>
> * Dan Williams wrote:
>
>> Thomas, Peter, and Alexei wanted s/nospec_barrier/ifence/ and
>
> I just checked past discussions, and I cannot find that part, got any links or
> message-IDs?
>
> PeterZ's feedback on Jan 8 was:
>
>> On Sun, Jan
On Mon, Jan 29, 2018 at 04:38:39PM +0100, Peter Zijlstra wrote:
1;4205;0c> On Fri, Jan 19, 2018 at 01:02:18AM +0100, Frederic Weisbecker wrote:
> > When a CPU runs in full dynticks mode, a 1Hz tick remains in order to
> > keep the scheduler stats alive. However this residual tick is a burden
> > fo
On some platforms there's an ITS available but it's not enabled
because reading or writing the registers is denied by the
firmware. In fact, reading or writing them will cause the system
to reset. We could remove the node from DT in such a case, but
it's better to skip nodes that are marked as "dis
On Thursday 30 November 2017 00:21:26 Pali Rohár wrote:
> On Monday 20 November 2017 12:12:56 Karel Zak wrote:
> > On Sun, Nov 19, 2017 at 01:44:40PM +0100, Pali Rohár wrote:
> > > On Thursday 09 November 2017 22:21:31 Pali Rohár wrote:
> > > > So from all tests and discussion I would propose new u
On 01/28/2018 05:56 AM, Joe Perches wrote:
> commit 321737416c72d ("tty: serial: msm: Move header file into driver")
> removed the .h file, update the patterns.
>
> Signed-off-by: Joe Perches
Acked-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux F
2018-01-29 17:17 GMT+01:00 Rob Herring :
> On Tue, Jan 16, 2018 at 05:06:15PM +0100, Peter Rosin wrote:
>> Makes them easier to find.
>>
>> Signed-off-by: Peter Rosin
>> ---
>> Documentation/devicetree/bindings/eeprom/at24.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This one
On Fri, Jan 26, 2018 at 12:10:11PM +, Suzuki K Poulose wrote:
> On 26/01/18 11:08, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:27:59PM +, Suzuki K Poulose wrote:
> >>Now that each capability describes how to treat the conflicts
> >>of CPU cap state vs System wide cap state, we can unif
On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote:
> Add convenience macro for polling an event that does not have a
> waitqueue.
>
> Signed-off-by: Michal Suchanek
> ---
> include/linux/delay.h | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/include/linux/delay.h
Kirill A. Shutemov wrote:
> On Mon, Jan 29, 2018 at 08:23:57AM +0100, Florian Westphal wrote:
> > > vmalloc() once became killable by commit 5d17a73a2ebeb8d1 ("vmalloc: back
> > > off when the current task is killed") but then became unkillable by commit
> > > b8c8a338f75e052d ("Revert "vmalloc: b
From: Jason Wang
Date: Thu, 25 Jan 2018 15:31:42 +0800
> We try to allocate one more entry for lockless peeking. The adding
> operation may overflow which causes zero to be passed to kmalloc().
> In this case, it returns ZERO_SIZE_PTR without any notice by ptr
> ring. Try to do producing or consu
On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote:
> - ret=cdo->tray_move(cdi,0);
> + ret = cdo->tray_move(cdi, 0);
Please separate whitespace-only changes from functional changes such that
this patch series becomes easier to review.
From: Jason Wang
Date: Mon, 29 Jan 2018 15:10:37 +0800
>
>
> On 2018年01月26日 07:36, Michael S. Tsirkin wrote:
>> This fixes a bunch of issues around ptr_ring use in net core.
>> One of these: "tap: fix use-after-free" is also needed on net,
>> but can't be backported cleanly.
>>
>> I will post a
On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote:
> +static int cdrom_tray_close(struct cdrom_device_info *cdi)
> +{
> + int ret;
> +
> + ret = cdi->ops->tray_move(cdi, 0);
> + if (ret || !cdi->ops->drive_status)
> + return ret;
> +
> + return poll_event_interrup
On Fri, Jan 26, 2018 at 12:21:43PM +, Suzuki K Poulose wrote:
> On 26/01/18 11:22, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:28:00PM +, Suzuki K Poulose wrote:
> >>While processing the list of capabilities, it is useful to
> >>filter out some of the entries based on the given type to
Adding optional resets property for rng.
Signed-off-by: Lionel Debieve
---
Documentation/devicetree/bindings/rng/st,stm32-rng.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/rng/st,stm32-rng.txt
b/Documentation/devicetree/bindings/rng/st,stm32-rng.tx
Hello Matthew, Pavel and MM people,
I am probably too impatient, but what would be the next step after
reaching [PATCH v3] and collecting two Reviewed-by signatures?
Is there a chance that this patch goes into v4.16-rc1 to be less of a
risk for the whole cycle?
Thanks,
Eugeniu.
On Wed, Jan 24,
This set of patches add extended functionalities for stm32 rng
driver.
Patch #1 includes a reset during probe to avoid any error status
which can occur during bootup process and keep safe rng integrity.
Patch #3 adds a new property to manage the clock error detection
feature which can be disabled
Avoid issue when probing the RNG without
reset if bad status has been detected previously
Signed-off-by: Lionel Debieve
---
drivers/char/hw_random/stm32-rng.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/char/hw_random/stm32-rng.c
b/drivers/char/hw_random/stm32-rng.c
ind
Add optional property to enable the clock detection error
on rng block. It is used to allow slow clock source which
give correct entropy for rng.
Signed-off-by: Lionel Debieve
---
Documentation/devicetree/bindings/rng/st,stm32-rng.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documenta
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Horman
[ Upstream commit 848b159835ddef99cc4193083f7e786c3992f580 ]
with the introduction of commit
b0eb57cb97e7837ebb746404c2c58c6f536f23fa, it appears that rq->buf_info
is improperly ha
- Backwards Compatibility:
If userspace wants to determine whether RTM_NEWLINK supports the
IFLA_IF_NETNSID property they should first send an RTM_GETLINK request
with IFLA_IF_NETNSID on lo. If either EACCESS is returned or the reply
does not include IFLA_IF_NETNSID userspace should assume
Add a new property that allow to disable the clock error
detection which is required when the clock source selected
is out of specification (which is not mandatory).
Signed-off-by: Lionel Debieve
---
drivers/char/hw_random/stm32-rng.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(
Currently -Wunused-variable warnings are disabled with
clang and with gcc -Wunused-variable warnings are
enabled, with this setting all unused local variables
would be warned in clang as well.
Disable -Wunused-const-variable warnings instead of
disabling -Wunused-variable warnings, So that in both
Hi,
Based on the previous discussion this enables passing a IFLA_IF_NETNSID
property along with RTM_NEWLINK requests. The latter patch was missing from my
previous series to allow for some more time to test this.
Best,
Christian
Christian Brauner (1):
rtnetlink: enable IFLA_IF_NETNSID for RTM_
On Mon, Jan 29, 2018 at 11:31:57AM -0500, David Miller wrote:
> From: Christian Brauner
> Date: Wed, 24 Jan 2018 15:26:31 +0100
>
> > Based on the previous discussion this enables passing a IFLA_IF_NETNSID
> > property along with RTM_SETLINK and RTM_DELLINK requests. The patch for
> > RTM_NEWLINK
On Wed, Dec 13, 2017 at 03:06:55PM +0100, Thomas Gleixner wrote:
> On Wed, 13 Dec 2017, Takashi Iwai wrote:
> > On Wed, 13 Dec 2017 12:35:54 +0100,
> > Thomas Gleixner wrote:
> > >
> > > > > On Mon, 11 Dec 2017, Anand, Jerome wrote:
> > > > > > > On Fri, 8 Dec 2017, Ville Syrjälä wrote:
> > > > >
On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote:
> When the drive closes it can take tens of seconds until the disc is
> analyzed. Wait for the drive to become ready or report an error.
>
> Signed-off-by: Michal Suchanek
> ---
> drivers/cdrom/cdrom.c | 9 +
> 1 file changed, 9 i
On Fri, Jan 26, 2018 at 09:07:25PM +0100, Borislav Petkov wrote:
> +.macro FILL_RETURN_BUFFER nr:req ftr:req
> #ifdef CONFIG_RETPOLINE
> + ALTERNATIVE "", "call __clear_rsb", \ftr
> #endif
> .endm
>
> @@ -206,15 +174,10 @@ extern char __indirect_thunk_end[];
> static inline void vmexit_fi
On Fri, Jan 26, 2018 at 12:31:18PM +, Suzuki K Poulose wrote:
> On 26/01/18 11:47, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
> >>So far we have had separate routes for triggering errata and feature
> >
> >"triggering errata" ? ;)
> >
>
> :-). Shoul
On Sun, Jan 28, 2018 at 03:06:42PM -0600, Josh Poimboeuf wrote:
> On Mon, Jan 22, 2018 at 12:25:22PM -0800, Guenter Roeck wrote:
> > Hi David,
> >
> > On Mon, Jan 22, 2018 at 07:34:04PM +, David Woodhouse wrote:
> > > On Thu, 2018-01-18 at 11:41 -0800, Guenter Roeck wrote:
> > > >
> > > > > N
On Thu, Jan 18, 2018 at 10:58:36AM +0900, Masahiro Yamada wrote:
> 2018-01-18 1:28 GMT+09:00 Masahiro Yamada :
> > This property is equivalent to "disable-wp" defined in
> > Documentation/devicetree/bindings/mmc/tmio_mmc.txt
>
> This is mistake.
>
> "disable-wp" is defined in
>
> Documentation/d
On Mon, Jan 29, 2018 at 05:48:33PM +0100, Frederic Weisbecker wrote:
> On Mon, Jan 29, 2018 at 04:38:39PM +0100, Peter Zijlstra wrote:
> > I would very much like a few words on why sched_class::task_tick() is
> > safe to call remote -- from a quick look I think it actually is, but it
> > would be g
On 29/01/18 17:14, Dave Martin wrote:
On Fri, Jan 26, 2018 at 12:31:18PM +, Suzuki K Poulose wrote:
On 26/01/18 11:47, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
So far we have had separate routes for triggering errata and feature
"triggering err
From: Vadim Lomovtsev
Date: Thu, 25 Jan 2018 03:38:17 -0800
> From: Vadim Lomovtsev
>
> It was found that ethtool provides unexisting module name while
> it queries the specified network device for associated driver
> information. Then user tries to unload that module by provided
> module name
On Sun, Jan 28, 2018 at 11:28 PM, Benjamin Poirier wrote:
> On 2018/01/26 13:01, Alexander Duyck wrote:
>> On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote:
>> > This reverts commit 16ecba59bc333d6282ee057fb02339f77a880beb.
>> >
>> > It was reported that emulated e1000e devices in vmware e
On Fri, Jan 26, 2018 at 03:46:59PM +, Suzuki K Poulose wrote:
> On 26/01/18 12:25, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:28:03PM +, Suzuki K Poulose wrote:
> >>KPTI capability is a security feature which should be enabled
> >>when at least one CPU on the system needs it. Any late
On Thu, Jan 18, 2018 at 12:46:52AM +0800, John Garry wrote:
> From: Xiaofei Tan
"dt-bindings: ..." is the preferred subject prefix.
>
> Add directly attached disk LED feature for v2 hw.
>
> Signed-off-by: Xiaofei Tan
> Signed-off-by: John Garry
> ---
> Documentation/devicetree/bindings/scsi
On Mon, Jan 29, 2018 at 10:37:44AM +, David Woodhouse wrote:
> On Mon, 2018-01-29 at 10:43 +0100, KarimAllah Ahmed wrote:
> > On 01/29/2018 09:46 AM, David Woodhouse wrote:
> > > Reading the code and comparing with the SDM, I can't see where we're
> > > ever setting VM_EXIT_MSR_STORE_{ADDR,COUN
The new header allows to wrap per-arch atomic operations
and add common functionality to all of them.
Signed-off-by: Dmitry Vyukov
Acked-by: Mark Rutland
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Linus Torvalds
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Will Deacon
Cc: kasan-...@googlegrou
The comments are factored out from the code changes to make them
easier to read. Add them separately to explain some non-obvious
aspects.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Ingo Molnar
Cc: kasan-...@goog
On Mon, Jan 29, 2018 at 09:15:26AM -0800, Guenter Roeck wrote:
> On Sun, Jan 28, 2018 at 03:06:42PM -0600, Josh Poimboeuf wrote:
> > On Mon, Jan 22, 2018 at 12:25:22PM -0800, Guenter Roeck wrote:
> > > Hi David,
> > >
> > > On Mon, Jan 22, 2018 at 07:34:04PM +, David Woodhouse wrote:
> > > > O
Add arch_ prefix to all atomic operations and include
. This will allow
to add KASAN instrumentation to all atomic ops.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Ingo Molnar
Cc: kasan-...@googlegroups.com
Cc: l
301 - 400 of 1013 matches
Mail list logo
