On Mon, 22 Jan 2018 09:22:25 +0100
Quentin Schulz wrote:
> Hi Jonathan,
>
> On Sun, Jan 21, 2018 at 12:26:55PM +, Jonathan Cameron wrote:
> > On Mon, 15 Jan 2018 11:33:41 +0100
> > Quentin Schulz wrote:
> >
> > > The X-Powers AXP813 PMIC is really close to what is already done for
> > >
On Tue, 23 Jan 2018 17:04:56 +0100
Fabrice Gasnier wrote:
> Error handling in stm32h7_adc_enable routine doesn't unwind enable
> sequence correctly. ADEN can only be cleared by hardware (e.g. by
> writing one to ADDIS).
> It's also better to clear ADRDY just after it's been set by hardware.
>
>
TPM2_CC_Create(0x153) and TPM2_CC_CreatePrimary (0x131) involve generation
of crypto keys which can be a computationally intensive task.
The timeout is set to 3min.
Signed-off-by: Tomas Winkler
---
V2: resent
drivers/char/tpm/tpm-interface.c | 4
drivers/char/tpm/tpm.h | 27 +
Commit-ID: dd085168a74c99c3ebe7f813069e412eb8444243
Gitweb: https://git.kernel.org/tip/dd085168a74c99c3ebe7f813069e412eb8444243
Author: Josh Poimboeuf
AuthorDate: Sat, 27 Jan 2018 20:21:50 -0600
Committer: Thomas Gleixner
CommitDate: Sun, 28 Jan 2018 09:19:12 +0100
x86/ftrace: Add one
On Thu, 25 Jan 2018 22:10:08 +0530
Shreeya Patel wrote:
> iio_dev->mlock is to be used only by the IIO core for protecting
> device mode changes between INDIO_DIRECT and INDIO_BUFFER.
>
> This patch replaces the use of mlock with the already established
> buf_lock mutex.
>
> Introducing 'unlock
On Fri, 26 Jan 2018 16:19:28 +0100
Philipp Rossak wrote:
> From: Icenowy Zheng
>
> As the H3 SoC, which is also in sun8i line, has totally different
> register map for the thermal sensor (a cut down version of GPADC), we
> should rename A23/A33-specified registers to contain A33, in order to
>
I happen to look at the patches for the crash binary and came across
this log entry from Jan 19. I am also using 4.15-rc kernel. Not
knowing anything about crash it is hard to even attempt to fix it.
Initial pass for support of kernel page table isolation. The x86_64
"bt" command may indicate "bt
hi!
> > > Correct. This will depend on the firmware expected format . I
> > > think
> > > ultimately it will be standardized.
> > Is it fair to say that "expected" format is some kind of bytecode for
> > CPU in the gesture sensor?
> Not necessarily a byte code to execute on the CPU in the gesture
On Fri, 26 Jan 2018 16:19:29 +0100
Philipp Rossak wrote:
> For adding newer sensor some basic rework of the code is necessary.
>
> This commit reworks the code and allows the sampling start/end code and
> the position of value readout register to be altered. Later the start/end
> functions will
On Sat, Jan 27, 2018 at 08:21:50PM -0600, Josh Poimboeuf wrote:
> Yeah, Steven reported it a few days ago but I was in backport lala land.
> It's a simple fix:
Thanks dude, yap warning is gone with it. :-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim t
On Fri, 26 Jan 2018 16:19:30 +0100
Philipp Rossak wrote:
> For adding newer sensor some basic rework of the code is necessary.
>
> The SoCs after H3 has newer thermal sensor ADCs, which have two clock
> inputs (bus clock and sampling clock) and a reset. The registers are
> also re-arranged.
>
>
Firstly, I only got a few patches of this series so I couldn't review all of
them
- please Cc: me to all future Meltdown and Spectre related patches!
* Dan Williams wrote:
> 'array_idx' is proposed as a generic mechanism to mitigate against
> Spectre-variant-1 attacks, i.e. an attack that byp
On Fri, 26 Jan 2018 16:19:32 +0100
Philipp Rossak wrote:
> This patch reworks the driver to support nvmem calibration cells.
> The driver checks if the nvmem calibration is supported and reads out
> the nvmem. At the beginning of the startup process the calibration data
> is written to the relate
On Fri, 26 Jan 2018 16:19:33 +0100
Philipp Rossak wrote:
> This patch rewors the driver to support interrupts for the thermal part
> of the sensor.
>
> This is only available for the newer sensor (currently H3 and A83T).
> The interrupt will be trigerd on data available and triggers the update
>
On Fri, 26 Jan 2018 16:19:31 +0100
Philipp Rossak wrote:
multible -> multiple
> For adding newer sensor some basic rework of the code is necessary.
>
> This patch reworks the driver to be able to handle more than one
> thermal sensor. Newer SoC like the A80 have 4 thermal sensors.
> Because of
On Sun, 2018-01-28 at 08:31 +, Jonathan Cameron wrote:
> On Thu, 25 Jan 2018 22:10:08 +0530
> Shreeya Patel wrote:
>
> >
> > iio_dev->mlock is to be used only by the IIO core for protecting
> > device mode changes between INDIO_DIRECT and INDIO_BUFFER.
> >
> > This patch replaces the use of
* Dan Williams wrote:
> --- a/arch/x86/include/asm/uaccess.h
> +++ b/arch/x86/include/asm/uaccess.h
> @@ -124,6 +124,11 @@ extern int __get_user_bad(void);
>
> #define __uaccess_begin() stac()
> #define __uaccess_end() clac()
> +#define __uaccess_begin_nospec() \
> +({
* Dan Williams wrote:
> 'array_idx' uses a mask to sanitize user controllable array indexes,
> i.e. generate a 0 mask if idx >= sz, and a ~0 mask otherwise. While the
> default array_idx_mask handles the carry-bit from the (index - size)
> result in software. The x86 'array_idx_mask' does the sa
Hi!
> > > > This adds support for volume up/down keys in the dts.
> > > >
> > > > Signed-off-by: Pavel Machek
> > >
> > > Reviewed-by: Sebastian Reichel
> >
> > Tony, ping? Can I get you to apply this one?
>
> OK applying that for v4.16 so we have some kind of control of the
> device without
* Dan Williams wrote:
> Quoting Linus:
>
> I do think that it would be a good idea to very expressly document
> the fact that it's not that the user access itself is unsafe. I do
> agree that things like "get_user()" want to be protected, but not
> because of any direct bugs or
On Sun, 2018-01-28 at 00:37 -0800, Joe Smith wrote:
> I happen to look at the patches for the crash binary and came across
> this log entry from Jan 19. I am also using 4.15-rc kernel. Not
> knowing anything about crash it is hard to even attempt to fix it.
It may not work all that well if box doe
* Dan Williams wrote:
> Quoting Linus:
>
> I do think that it would be a good idea to very expressly document
> the fact that it's not that the user access itself is unsafe. I do
> agree that things like "get_user()" want to be protected, but not
> because of any direct bugs or
* Dan Williams wrote:
> Quoting Linus:
>
> "Honestly, I'd rather get rid of the fast-path entirely. Compared to
>all the PTI mess, it's not even noticeable.
>
>And if we ever get CPU's that have this all fixed, we can re-visit
>introducing the fastpath. But this is all very messy
On Sun, 28 Jan 2018 09:40:03 +0100
Pavel Machek wrote:
> hi!
>
> > > > Correct. This will depend on the firmware expected format . I
> > > > think
> > > > ultimately it will be standardized.
> > > Is it fair to say that "expected" format is some kind of bytecode for
> > > CPU in the gesture s
On Sun, 14 Jan 2018 10:43:30 +
Jonathan Cameron wrote:
> On Tue, 9 Jan 2018 21:24:01 +
> Jeremy Cline wrote:
>
> > On 12/10/2017 12:21 PM, Jonathan Cameron wrote:
> > > On Wed, 6 Dec 2017 17:52:34 +
> > > Jeremy Cline wrote:
> > >
> > >> Some BOSC0200 acpi_device-s describe
* Tim Chen wrote:
> Thanks to the reviewers and Andy Lutomirski for the suggestion of
> using ctx_id which got rid of the problem of mm pointer recycling.
> Here's an update of this patch based on Andy's suggestion.
>
> We could switch to a kernel idle thread and then back to the original
> pro
On Sun, 2018-01-28 at 10:20 +0100, Mike Galbraith wrote:
> On Sun, 2018-01-28 at 00:37 -0800, Joe Smith wrote:
> > I happen to look at the patches for the crash binary and came across
> > this log entry from Jan 19. I am also using 4.15-rc kernel. Not
> > knowing anything about crash it is hard to
Vincent Legoll writes:
> On 1/23/18, Michael Ellerman wrote:
>> This has been broken in linux-next for ~6 weeks now, can we please merge
>> this and get it fixed.
>
> Added Stephen Rothwell to cc
It should be fixed in the virtio tree, which the other Michael and Jason
maintain AFAIK.
cheers
Linus,
please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
Two final fixes for 4.15:
- Repair the OWNER_DIED logic in the futex code which got wreckaged with the
recent fix for a subtle race co
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
Four patches which all address lock inversions and deadlocks in the perf
core code and the Intel debug store.
Thanks,
tglx
---
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
A single bug fix to prevent a subtle deadlock in the scheduler core code
vs. cpu hotplug.
Thanks,
tglx
-->
Peter Zij
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single fix for a ~10 years old problem which causes high resolution
timers to stop after a CPU unplug/plug cycle due to a stale flag in the
On Sat, 27 Jan 2018 17:07:48 +
Al Viro wrote:
Hi Al,
> On Sat, Jan 27, 2018 at 01:59:56PM +, Dmitry Safonov wrote:
> >
> > > Incidentally, shouldn't filter_parse_regex("*[ab]", 5, &s, ¬)
> > > end up with s = "*[ab]"? We are returning MATCH_GLOB, after all,
> > > so we want the entir
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A set of small fixes for 4.15:
- Fix vmapped stack synchronization on systems with 4-level paging and a
large amount of memory caused by a mis
On Sun, 2018-01-28 at 10:56 +0100, Ingo Molnar wrote:
>
> What tree is this patch against? It doesn't apply to linus's latest, nor to
> tip:master.
It's in my tree at
http://git.infradead.org/users/dwmw2/linux-retpoline.git/shortlog/refs/heads/ibpb
which is gradually being finalized and flushe
Linus,
please pull the latest x86-pti-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus
Remove the ESP/RSP thunks for retpoline as they cannot ever work. Remove
them before they show up in a release.
Thanks,
tglx
--
On 28.01.2018 09:50, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:30 +0100
Philipp Rossak wrote:
For adding newer sensor some basic rework of the code is necessary.
The SoCs after H3 has newer thermal sensor ADCs, which have two clock
inputs (bus clock and sampling clock) and a reset.
On Sun, 28 Jan 2018, Ingo Molnar wrote:
> * Dan Williams wrote:
> > +
> > +#ifndef __NOSPEC_H__
> > +#define __NOSPEC_H__
_LINUX_NOSPEC_H
We have an established practice for those header guards...
> > +/*
> > + * When idx is out of bounds (idx >= sz), the sign bit will be set.
> > + * Extend th
On Fri, Jan 26, 2018 at 11:54:35AM -0700, Shuah Khan wrote:
> Upstream commit 1c9de5bf4286 ("usbip: vhci-hcd: Add USB3 SuperSpeed
> support")
Hm, I think you have the wrong commit id here.
I don't see any commit upstream with the Subject you have here, what are
you referring to?
thanks,
greg k-
mthca_user.h is unused since commit 486f60954c71 ("IB/mthca: Move user vendor
structures")
Remove it from tree.
Signed-off-by: Corentin Labbe
---
drivers/infiniband/hw/mthca/mthca_user.h | 112 ---
1 file changed, 112 deletions(-)
delete mode 100644 drivers/infiniba
Am 27.01.2018 um 15:28 schrieb Julia Lawall:
Check the variable that was most recently initialized.
The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
//
@@
expression x, y, f, g, e, m;
statement S1,S2,S3,S4;
@@
x = f(...);
if (\(<+...x...+>\&e\)) S1 else S
On 28.01.2018 09:43, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:29 +0100
Philipp Rossak wrote:
For adding newer sensor some basic rework of the code is necessary.
This commit reworks the code and allows the sampling start/end code and
the position of value readout register to be alte
于 2018年1月28日 GMT+08:00 下午9:34:17, Philipp Rossak 写到:
>
>
>On 28.01.2018 09:43, Jonathan Cameron wrote:
>> On Fri, 26 Jan 2018 16:19:29 +0100
>> Philipp Rossak wrote:
>>
>>> For adding newer sensor some basic rework of the code is necessary.
>>>
>>> This commit reworks the code and allows the s
On 28.01.2018 10:02, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:32 +0100
Philipp Rossak wrote:
This patch reworks the driver to support nvmem calibration cells.
The driver checks if the nvmem calibration is supported and reads out
the nvmem. At the beginning of the startup process the
On 28.01.2018 10:06, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:33 +0100
Philipp Rossak wrote:
This patch rewors the driver to support interrupts for the thermal part
of the sensor.
This is only available for the newer sensor (currently H3 and A83T).
The interrupt will be trigerd on
于 2018年1月28日 GMT+08:00 下午9:46:18, Philipp Rossak 写到:
>
>
>On 28.01.2018 10:02, Jonathan Cameron wrote:
>> On Fri, 26 Jan 2018 16:19:32 +0100
>> Philipp Rossak wrote:
>>
>>> This patch reworks the driver to support nvmem calibration cells.
>>> The driver checks if the nvmem calibration is suppo
Fix the first few missing or defective patterns shown
by ./scripts/get_maintainer.pl --self-test=patterns
Joe Perches (6):
MAINTAINERS: Remove ANDROID ION pattern
MAINTAINERS: Remove ARM/CLKDEV SUPPORT file pattern
MAINTAINERS: Update Cortina/Gemini patterns
MAINTAINERS: Update "ARM/OXNAS
commit 321737416c72d ("tty: serial: msm: Move header file into driver")
removed the .h file, update the patterns.
Signed-off-by: Joe Perches
cc: Stephen Boyd
cc: Andy Gross
cc: David Brown
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3efa8
commit 4c25c5d2985c ("ARM: pxa: make more mach/*.h files local")
moved the files around, update the patterns.
Signed-off-by: Joe Perches
cc: Arnd Bergmann
cc: Marek Vasut
cc: Tomas Cech
---
MAINTAINERS | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/MAINTAINER
commit 4d5ae32f5e1e ("net: ethernet: Add a driver for Gemini gigabit ethernet")
added invalid patterns. Fix it.
Signed-off-by: Joe Perches
cc: Linus Walleij
cc: Hans Ulli Kroll
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
commit 9e6c62b05c1b ("ARM: dts: rename oxnas dts files") renamed
the files, update the patterns.
Signed-off-by: Joe Perches
cc: Daniel Golle
cc: Arnd Bergmann
cc: Neil Armstrong
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
i
commit 34d2f4d3a4d6 ("ARM: Use generic clkdev.h header") removed
the file, remove the pattern.
Signed-off-by: Joe Perches
cc: Russell King
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 89c2e7752eab..e92ab5e64ddf 100644
--- a/MAINTAINERS
+++ b
File drivers/staging/android/uapi/ion_test.h was removed by
commit 9828282e33a0 ("staging: android: ion: Remove old platform support")
Remove the pattern.
Signed-off-by: Joe Perches
cc: Laura Abbott
cc: Sumit Semwal
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINER
On 01/28/2018 05:56 AM, Joe Perches wrote:
File drivers/staging/android/uapi/ion_test.h was removed by
commit 9828282e33a0 ("staging: android: ion: Remove old platform support")
Remove the pattern.
Acked-by: Laura Abbott
Signed-off-by: Joe Perches
cc: Laura Abbott
cc: Sumit Semwal
---
On 28.01.2018 10:08, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:31 +0100
Philipp Rossak wrote:
multible -> multiple
^^ Ok, I will fix that.
For adding newer sensor some basic rework of the code is necessary.
This patch reworks the driver to be able to handle more than one
thermal
On 28.01.2018 14:37, Icenowy Zheng wrote:
于 2018年1月28日 GMT+08:00 下午9:34:17, Philipp Rossak 写到:
On 28.01.2018 09:43, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:29 +0100
Philipp Rossak wrote:
For adding newer sensor some basic rework of the code is necessary.
This commit reworks
Denis Du writes:
>>From the above code, I can get that only Carrier have some change, it
> will restart the protocol by hdlc_proto_start(dev);and thus the timer,
> the previous timer expired due to protocol fail.
>
> If carrier keep no change by if (hdlc->carrier == on)
> goto carrier_exi
On 28.01.2018 14:52, Icenowy Zheng wrote:
于 2018年1月28日 GMT+08:00 下午9:46:18, Philipp Rossak 写到:
On 28.01.2018 10:02, Jonathan Cameron wrote:
On Fri, 26 Jan 2018 16:19:32 +0100
Philipp Rossak wrote:
This patch reworks the driver to support nvmem calibration cells.
The driver checks if t
On Sat, Jan 27, 2018 at 3:32 PM, Pali Rohár wrote:
> Dell platform team told us that some (DMI whitelisted) Dell Latitude
> machines have ST microelectronics accelerometer at i2c address 0x29.
>
> Presence of that ST microelectronics accelerometer is verified by existence
> of SMO88xx ACPI device
On 1/27/2018 8:17 PM, SF Markus Elfring wrote:
From: Markus Elfring
Date: Sat, 27 Jan 2018 19:02:34 +0100
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in
iser_send_data_out()
On Sat, Jan 27, 2018 at 10:07:41PM +0200, Dan Aloni wrote:
> commit cabfb3680f78 upstream.
Are you sure?
$ gsr cabfb3680f78
cabfb3680f78 ("CIFS: Enable encryption during session setup phase")
Doesn't seem to match up at all here :(
totally confused,
greg k-h
On Sunday 28 January 2018 16:39:25 Andy Shevchenko wrote:
> On Sat, Jan 27, 2018 at 3:32 PM, Pali Rohár wrote:
> > +static bool is_dell_system_with_lis3lv02d(void)
> > +{
>
> > + /*
> > +* Check that ACPI device SMO88xx exists and is enabled. That ACPI
> > +* device represen
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, Alexei Starovoitov wrote:
> >>>
> >>> The BPF interpreter has been used as part of the spectre
On Sun, Jan 28, 2018 at 12:39:43PM +, Corentin Labbe wrote:
> mthca_user.h is unused since commit 486f60954c71 ("IB/mthca: Move user vendor
> structures")
> Remove it from tree.
>
> Signed-off-by: Corentin Labbe
> ---
> drivers/infiniband/hw/mthca/mthca_user.h | 112
> --
On Sun, Jan 28, 2018 at 03:43:48PM +0100, Greg KH wrote:
> On Sat, Jan 27, 2018 at 10:07:41PM +0200, Dan Aloni wrote:
> > commit cabfb3680f78 upstream.
>
> Are you sure?
> $ gsr cabfb3680f78
> cabfb3680f78 ("CIFS: Enable encryption during session setup phase")
>
> Doesn't seem to match up at all
On Sun, Jan 28, 2018 at 4:45 PM, Pali Rohár wrote:
> On Sunday 28 January 2018 16:39:25 Andy Shevchenko wrote:
>> On Sat, Jan 27, 2018 at 3:32 PM, Pali Rohár wrote:
>> > +static bool is_dell_system_with_lis3lv02d(void)
>> > +{
>>
>> > + /*
>> > +* Check that ACPI device SMO88xx exis
On Fri, Jan 26, 2018 at 8:21 PM, Juergen Gross wrote:
> On 26/01/18 19:08, Andy Shevchenko wrote:
>> On Thu, Jan 25, 2018 at 4:36 PM, Juergen Gross wrote:
>>> Add a function to get the address of the RSDP table. Per default use a
>>> __weak annotated function being a nop.
>>
>> The problem with w
qib_keys.c was left uncompilable in commit 7c2e11fe2dbe ("IB/qib: Remove qp and
mr functionality from qib")
Since nothing need it, remove it from tree.
Signed-off-by: Corentin Labbe
---
drivers/infiniband/hw/qib/qib_keys.c | 235 ---
1 file changed, 235 deletions
Hi
On Thu, Jan 25, 2018 at 04:17:06PM +0100, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v4.14.15-rt12 patch set.
>
> Changes since v4.14.15-rt11:
>
> - Drop ping-sysrq. Since it won't reach mainline in its current shape,
> lets drop. Suggested by C
cxio_dbg.c is uncompiled since commit 2b540355cd2f ("RDMA/cxgb3: cleanups")
10 years after, we could remove it.
Signed-off-by: Corentin Labbe
---
drivers/infiniband/hw/cxgb3/cxio_dbg.c | 206 -
1 file changed, 206 deletions(-)
delete mode 100644 drivers/infiniban
> On Jan 28, 2018, at 1:29 AM, Ingo Molnar wrote:
>
>
> * Dan Williams wrote:
>
>> Quoting Linus:
>>
>> "Honestly, I'd rather get rid of the fast-path entirely. Compared to
>> all the PTI mess, it's not even noticeable.
>>
>> And if we ever get CPU's that have this all fixed, we can
Good luck in your efforts, and thanks for your work on static analysis.
> On Jan 27, 2018, at 9:12 PM, Jia-Ju Bai wrote:
>
>
>
>> On 2018/1/28 1:48, Ed Cashin wrote:
>> If the tool cannot tell whether the protected state is manipulated by
>> *another* piece of code called in atomic context, t
Hi,
Thanks for the report.
On Sat 27 Jan 2018 at 15:49, kbuild test robot wrote:
> Hi Rui,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on crypto/master]
> [also build test ERROR on v4.15-rc9 next-20180126]
> [cannot apply to cryptodev/master]
> [if your patch is appl
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 -Wunused-const-variable on GCC? You do not
ex
Hi,
According to my understanding, the allocation fall back order
completely depends on heap->id that is assigned during the heap
creation:
plist_for_each_entry(heap, &dev->heaps, node) {
/* if the caller didn't specify this heap id */
if (!((1 << heap->id) & heap_id_mask))
On Sun, 2018-01-28 at 15:11 +, Corentin Labbe wrote:
> cxio_dbg.c is uncompiled since commit 2b540355cd2f ("RDMA/cxgb3: cleanups")
> 10 years after, we could remove it.
OK, now you could remove the prototypes and probably
CONFIG_INFINIBAND_CXGB3_DEBUG too.
There is a DEBUG test and many uses
On Sun, Jan 28, 2018 at 12:55 AM, Ingo Molnar wrote:
>
> Firstly, I only got a few patches of this series so I couldn't review all of
> them
> - please Cc: me to all future Meltdown and Spectre related patches!
>
> * Dan Williams wrote:
>
>> 'array_idx' is proposed as a generic mechanism to miti
On Mon, Jan 22, 2018 at 4:51 PM, Meghana Madhyastha
wrote:
> Add of_find_backlight, a helper function which is a generic version
> of tinydrm_of_find_backlight that can be used by other drivers to avoid
> repetition of code and simplify things.
> +struct backlight_device *of_find_backlight(struct
On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Not sure if those two worked by design or just by chance so far. In any
> case, it's at least cleaner and clearer to express this in a single
> config statement.
Congrats! You found by the way a bug in
commit e279b6c1d329
On Mon, Jan 22, 2018 at 7:04 AM, Jonathan Neuschäfer
wrote:
Style issues below.
> +#define HW_GPIO_OWNER 0x3c
> +
> +
> +struct hlwd_gpio {
No need extra empty line in between.
> + struct gpio_chip gpioc;
> + void __iomem *regs;
> + struct device *dev;
> +};
> +
> +s
Applied.
thanks!
-Len
On Tue, Dec 19, 2017 at 11:02 PM, Laura Abbott wrote:
> rpm-lint flagged these as being executable:
>
> kernel-tools.x86_64: W: spurious-executable-perm
> /usr/share/man/man8/turbostat.8.gz
> kernel-tools.x86_64: W: spurious-executable-perm
> /usr/share/man/man8/x86_ener
* 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 07, 2018 at 06:24:11PM -0800, Alexei Starovoitov wrote:
> > How abo
>
> kallsyms failure: relative symbol value 0x8100 out of
> range in relative mode
>
> I seem to get that all the time here, and have also disabled it for now,
> but it sounds important (and breaks the build).
Need to take a look at it.
I had some patches that completely revamped k
On Sun, 28 Jan 2018, Dan Williams wrote:
> On Sun, Jan 28, 2018 at 12:55 AM, Ingo Molnar wrote:
> >> + */
> >> +#define array_idx(idx, sz) \
> >> +({ \
> >> + typeof(idx) _i = (idx);
The SYCALLL64 fast path was a nice, if small, optimization back in
the good old days when syscalls were actually reasonably fast. Now
we have PTI to slow everything down, and indirect branches are
verboten, making everything messier. The retpoline code in the fast
path was particularly nasty.
Ju
__SYSCALL_DEFINE is rather magical. Add a bit of documentation.
Signed-off-by: Andy Lutomirski
---
include/linux/syscalls.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
index a78186d826d7..d3f244a447c5 100644
--- a/include/l
Three changes in here:
- Get rid of the SYSCALL64 fast path as suggested by Linus.
- Move TS_COMPAT into the same cacheline as thread_info::flags, also
suggested by Linus.
- Document SYSCALL_DEFINE a bit better.
Andy Lutomirski (3):
x86/entry/64: Remove the SYSCALL64 fast path
x86/asm:
The TS_COMPAT bit is very hot and is accessed from code paths that
mostly also touch thread_info::flags. Move it into struct
thread_info to improve cache locality.
The only reason it was in thread_struct is that there was a brief
period during which we didn't allow arch-specific fields in struct
From: Fengguang Wu
fs/btrfs/volumes.c:742:10-17: WARNING: ERR_CAST can be used with fs_devices
Use ERR_CAST inlined function instead of ERR_PTR(PTR_ERR(...))
Generated by: scripts/coccinelle/api/err_cast.cocci
Fixes: bf155c98d312 ("btrfs: get device pointer from device_list_add()")
CC: Anand
>
> cxio_dbg.c is uncompiled since commit 2b540355cd2f ("RDMA/cxgb3:
> cleanups")
> 10 years after, we could remove it.
>
> Signed-off-by: Corentin Labbe
Acked-by: Steve Wise
* Andy Lutomirski wrote:
> The SYCALLL64 fast path was a nice, if small, optimization back in
> the good old days when syscalls were actually reasonably fast. Now
> we have PTI to slow everything down, and indirect branches are
> verboten, making everything messier. The retpoline code in the f
* Andy Lutomirski wrote:
> The TS_COMPAT bit is very hot and is accessed from code paths that
> mostly also touch thread_info::flags. Move it into struct
> thread_info to improve cache locality.
>
> The only reason it was in thread_struct is that there was a brief
> period during which we didn
On Sun, Jan 28, 2018 at 10:38 AM, Andy Lutomirski wrote:
> __SYSCALL_DEFINE is rather magical. Add a bit of documentation.
Ack.
Is that "long long" part of the example on purpose? Because that's
likely the only really nasty part about any ptregs wrapper: some
arguments aren't _one_ register, th
On Sun, Jan 28, 2018 at 10:38 AM, Andy Lutomirski wrote:
>
> Linus suggested further changing:
>
> ti->status &= ~(TS_COMPAT|TS_I386_REGS_POKED);
>
> to:
>
> if (unlikely(ti->status & (TS_COMPAT|TS_I386_REGS_POKED)))
> ti->status &= ~(TS_COMPAT|TS_I386_REGS_POKED);
>
> on the theory
* Andy Lutomirski wrote:
> __SYSCALL_DEFINE is rather magical. Add a bit of documentation.
>
> Signed-off-by: Andy Lutomirski
> ---
> include/linux/syscalls.h | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
> index a78
On Fri, Jan 26, 2018 at 2:42 PM, Andy Lutomirski wrote:
> On Fri, Jan 26, 2018 at 2:38 PM, Andy Lutomirski wrote:
>> On Fri, Jan 26, 2018 at 11:46 AM, Andy Lutomirski wrote:
>>> On Fri, Jan 26, 2018 at 10:59 AM, Andy Lutomirski wrote:
On Fri, Jan 26, 2018 at 8:22 AM, Andy Lutomirski wrote
On Fri, Jan 26, 2018 at 2:56 PM, Borislav Petkov wrote:
> On Fri, Jan 26, 2018 at 02:38:28PM -0800, Andy Lutomirski wrote:
>> Borislav, any chance you could run the attached program on an AMD
>> machine to see what it does?
>
> [boris@pd: /tmp> ./gs1
> PID = 3420
> ax = 0, cx = 0, dx = 0
>
> This
Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for guests
that will only mitigate Spectre V2 through IBRS+IBPB and will not be using a
retpoline+IBPB based approach.
To avoid the overhead of atomically saving and restoring the MSR_IA32_SPEC_CTRL
for guests that do not actually
Thoses files are unused since commit b3b961448f70 ("V4L/DVB (13795):
[Mantis/Hopper] Code overhaul, add Hopper devices into the PCI ID list")
8 year after, we could remove it.
Signed-off-by: Corentin Labbe
---
drivers/media/pci/mantis/mantis_vp3028.c | 38
drive
On Sun, Jan 28, 2018 at 09:51:00AM +0200, Tomas Winkler wrote:
> diff --git a/include/linux/tpm.h b/include/linux/tpm.h
> index bcdd3790e94d..06639fb6ab85 100644
> +++ b/include/linux/tpm.h
> @@ -44,7 +44,7 @@ struct tpm_class_ops {
> bool (*update_timeouts)(struct tpm_chip *chip,
>
1 - 100 of 528 matches
Mail list logo
