Hello,
Am 14.02.19 um 19:27 schrieb Dan Murphy:
> Hello
>
> OK I did not give up on this patch series just got a little preoccupied with
> some other kernel work. But here is the update per the comments.
>
> It should be understood I broke these out for reviewability.
> For instance the first
On Thu, Feb 28, 2019 at 11:30:14AM -0500, Johannes Weiner wrote:
> [ Resend #2: Sorry about the spam, I mixed up the header fields in
> git-send-email and I don't know who did and didn't receive the
> garbled previous attempt.
>
> Resend #1: Rebased on top of the latest mmots. ]
>
> The
Wolfgang
On 2/28/19 10:40 AM, Wolfgang Grandegger wrote:
> Hello,
>
> Am 14.02.19 um 19:27 schrieb Dan Murphy:
>> Hello
>>
>> OK I did not give up on this patch series just got a little preoccupied with
>> some other kernel work. But here is the update per the comments.
>>
>> It should be
On Thu, Feb 28, 2019 at 1:40 AM Oliver wrote:
>
> On Thu, Feb 28, 2019 at 7:35 PM Aneesh Kumar K.V
> wrote:
> >
> > Add a flag to indicate the ability to do huge page dax mapping. On
> > architecture
> > like ppc64, the hypervisor can disable huge page support in the guest. In
> > such a case,
On 02/28/19 17:04, Dietmar Eggemann wrote:
> Hi Joel,
>
> On 2/28/19 3:47 PM, Joel Fernandes wrote:
> > On Thu, Feb 28, 2019 at 01:53:43PM +, Qais Yousef wrote:
> > > Hi Joel
> > >
> > > On 02/27/19 14:37, Joel Fernandes (Google) wrote:
>
> [...]
>
> > Ah good catch, I made this change for
Reports the size of the virtgpu framebuffer to userspace and installs
the deferred I/O handlers so that userspace can mmap() and write to it.
Signed-off-by: Joshua Watt
---
drivers/gpu/drm/virtio/virtgpu_fb.c | 4
1 file changed, 4 insertions(+)
diff --git
On Thu, Feb 28, 2019 at 12:09 AM Greg Kroah-Hartman
wrote:
>
> On Wed, Feb 27, 2019 at 03:19:17PM -0700, Daniel Kurtz wrote:
> > In cases such as xhci_abort_cmd_ring(), xhci_handshake() is called with
> > a spin lock held (and local interrupts disabled) with a huge 5 second
> > timeout. This can
Hi, comments inline.
On Sun, Feb 24, 2019 at 3:36 PM Robert Eshleman wrote:
>
> This patch adds support for the ap3216c ambient light and proximity
> sensor.
>
> Supported features include:
>
> * Illuminance (lux)
> * Proximity (raw)
> * IR (raw)
> * Rising/falling
On Thu, Feb 28, 2019 at 7:05 AM Peter Zijlstra wrote:
>
> drivers/gpu/drm/i915/i915_gem_execbuffer.o: warning: objtool:
> .altinstr_replacement+0x3c: redundant UACCESS disable
> drivers/gpu/drm/i915/i915_gem_execbuffer.o: warning: objtool:
> .altinstr_replacement+0x66: redundant UACCESS disable
On Thu, Feb 28, 2019 at 11:59:32AM +0100, Geert Uytterhoeven wrote:
> Suspicious RCU usage messages are reported as warnings.
>
> Fixes: a5dd63efda3d07b5 ("lockdep: Use "WARNING" tag on lockdep splats")
> Signed-off-by: Geert Uytterhoeven
Reviewed-by: Paul E. McKenney
> ---
> And before that,
On Thu, Feb 28, 2019 at 11:57:31AM +0100, Geert Uytterhoeven wrote:
> Since the removal of FS_RECLAIM annotations, lockdep states contain six
> characters, not four.
Does the above want to instead say "four characters, not six"?
Thanx, Paul
On Thu, 28 Feb 2019 15:12:16 +0100
Pierre Morel wrote:
> On 28/02/2019 13:39, Halil Pasic wrote:
> > On Thu, 28 Feb 2019 10:42:23 +0100
> > Christian Borntraeger wrote:
[..]
> >> Correct?
> >
> > IMHO mostly.
> >
> > I also doing the facility checks in kvm is easier, and I think this is
> >
On Thu, 28 Feb 2019 09:48:39 +0100
Pierre Morel wrote:
> On 28/02/2019 09:23, Christian Borntraeger wrote:
> > On 22.02.2019 16:29, Pierre Morel wrote:
> >> To be able to use the VFIO interface to facilitate the
> >> mediated device memory pining/unpining we need to register
> >> a notifier for
In the tps65910/1 datasheets under "Device POWER ON Disable Conditions".
There are four conditions which can disable power on:
Long press interrupt (PWRON_LP_IT) OR thermal trip OR DEV_OFF bit OR
DEV_OFF_RST bit.
The Ouya game console has TPS65911. Before this patch the device will not
power off
On Thu, Feb 28, 2019 at 7:34 AM Greg Kroah-Hartman
wrote:
>
> Linus, this should go in before 5.0-final is out, as it resolves a
> problem found by syzbot. Paolo has given his ack for me to send this
> directly to you. If you want this in [GIT PULL] format, I can do that
> as well.
Applied,
Hi Paul,
On Thu, Feb 28, 2019 at 5:51 PM Paul E. McKenney wrote:
> On Thu, Feb 28, 2019 at 11:57:31AM +0100, Geert Uytterhoeven wrote:
> > Since the removal of FS_RECLAIM annotations, lockdep states contain six
> > characters, not four.
>
> Does the above want to instead say "four characters,
This could also be a parser error. In the HID specification section 6.2.2.8 it
states that the last declared Usage Page is applied to Usages when the Main
item is encountered.
"If the bSize field = 1 or 2 then the Usage is interpreted as an unsigned value
that selects a Usage ID on the
Apply for a loan at 2% reply to this Email for more Info
Start streaming was sometimes failing because of pm_runtime_get_sync()
non-0 return value. In fact return value was not an error but a
positive value (1), indicating that PM was already enabled.
Fix this by going to error path only with negative return value.
Signed-off-by: Hugues Fruchet
---
Avoid call of dmaengine_terminate_all() between
dmaengine_prep_slave_single() and dmaengine_submit() by locking
the whole DMA submission sequence.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/stm32/stm32-dcmi.c | 17 +
1 file changed, 17 insertions(+)
diff --git
Hello Maintainers,
Please help to merge patch.
> -Original Message-
> From: Stephen Boyd
> Sent: Thursday, February 28, 2019 5:31 AM
> To: a...@arndb.de; catalin.mari...@arm.com; devicet...@vger.kernel.org;
> gre...@linuxfoundation.org; kstew...@linuxfoundation.org; linux-arm-
>
In order to support softirq per-vector locking validation, we could
simply iterate over all enabled vectors and perform separate validation
for all of them on every lock event. We can expect that to introduce a
severe performance penalty though.
Therefore, we instead plan to validate the
Introduce a mask iterator that can be used to get the bit numbers from a
lock usage mask.
We don't want the overhead of the bitmap library for a fixed small 64
bit mask. So we just want a simple loop relying on an ffs() like
function. Yet we want to be careful not to shift further 64 bits at once
In order to perform softirq vector-finegrained locking validation we'll
need to be able to check multiple vector usages at once. Prepare the low
level usage mask check functions for that purpose.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel
The usage mask is going to expand to validate softirq related usages in
a per-vector finegrained way.
The current bitmap layout is:
LOCK_USEDHARDIRQ bits
\/
\ /
0
So this set should hopefully address all reviews from the v2, and
fix all reports from the extremely useful (as always) Kbuild testing
bot. It also completes support for all archs.
Unfortunately the already huge pile is ever growing. I should be able to
offload 2 or 3 of those patches but the
valid_state() and print_usage*() functions are not used beyond locking
correctness checks. So move them inside the appropriate
CONFIG_TRACE_IRQFLAGS && CONFIG_PROVE_LOCKING section.
Sadly the "unused function" warning wouldn't fire because valid_state()
is inline.
Signed-off-by: Frederic
check_prev_add_irq() tests all incompatible scenarios one after the
other while adding a lock (@next) to a tree dependency (@prev):
LOCK_USED_IN_HARDIRQ vs LOCK_ENABLED_HARDIRQ
LOCK_USED_IN_HARDIRQ_READ vs LOCK_ENABLED_HARDIRQ
Loosely handle all the softirq vectors verbosity under the same
function.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
Cc: Ingo Molnar
Cc:
mark_lock_irq() is going to deal with lock usages that gather multiple
softirq vectors at once. Therefore the validation through
check_usage_backwards() and check_usage_forwards() will need to handle
expanded usage masks.
So enhance those functions to that purpose.
Reviewed-by: David S. Miller
Now that mark_lock() is going to handle multiple softirq vectors at
once for a given lock usage, the current fast path optimization that
simply check if the new bit usage is already present won't work anymore.
Indeed if the new usage is only partially present, such as for some
softirq vectors and
Since mark_lock() may now be passed more than one usage at once, make
sure to expand the lock usage structure in order to report all of them
while in verbose mode logging.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
We are going to save as much traces as we have softirq vectors involved
in a given usage. Expand the stack trace record code accordingly.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc:
Now that the code is mostly ready to play at this finegrained level,
reuse the macrofied vector list to define the usual 4 lock usage states
for each softirq vectors. This way we can perform the validations
independently for each of them.
The new usage mask layout becomes:
> > Hi Andrew,
> >
> > we produce a lot of boards and we have to change the MAC address,
> > from u-boot, for every board. So I must save in the u-boot
> > environment (SPI NOR flash) the MAC address for every board.
>
> Hi Flavio
>
> u-boot should be able to write the MAC address in the
From: Frederic Weisbecker
Use the subsystem as the prefix to name the __softirq_data accessors.
They are going to be extended and want a more greppable and standard
naming sheme.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc:
The bottom half masking APIs have become interestingly confusing with all
these flavours:
local_bh_enable()
_local_bh_enable()
local_bh_enable_ip()
__local_bh_enable_ip()
_local_bh_enable() is an exception here because it's the only
We are going to extend the softirq bits with an enabled vector mask.
Provide the field with a more generic name to later layout the pending
states on the lower bits and the enabled states on the higher bits.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho
This reverts commit 9aee5f8a7e30330d0a8f4c626dc924ca5590aba5.
We are going to need the 16 high bits above in order to implement
a softirq enable mask. x86 is the only architecture that doesn't use
unsigned int to implement softirq_pending.
Reviewed-by: David S. Miller
Signed-off-by: Frederic
From: Frederic Weisbecker
All softirqs must be set enabled on boot.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
Cc: Ingo Molnar
Cc: Sebastian Andrzej Siewior
Cc: Linus
Disabling the softirqs is currently an all-or-nothing operation: either
all softirqs are enabled or none of them. However we plan to introduce a
per vector granularity of this ability to improve latency response and
make each softirq vector interruptible by the others.
The first step carried here
Pass the softirq vector number to lockdep on callback execution so that
we know which one is involved while holding a lock. We will then be able
to pick up the proper LOCK_USED_IN_*_SOFTIRQ index to perform the
finegrained verifications.
Reviewed-by: David S. Miller
Signed-off-by: Frederic
From: Frederic Weisbecker
All softirqs must be set enabled on boot.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
Cc: Ingo Molnar
Cc: Sebastian Andrzej Siewior
Cc: Linus
From: Frederic Weisbecker
All softirqs must be set enabled on boot.
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
Cc: Ingo Molnar
Cc: Sebastian Andrzej Siewior
Cc: Linus
This is a usage example of spin_lock_bh_mask(). NET_RX, TIMER and
TASKLET are the three softirqs that have been reported by lockdep to
be used for this socket lock, at least on my own usecases.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel
__local_bh_disable_ip() is neither for strict internal use nor does it
require the caller to disable hardirqs. Probaby a celebration for ancient
behaviour.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc:
Provide the low level APIs to support per-vector masking. In order
to allow these to properly nest with itself and with full softirq
masking APIs, we provide two mechanisms:
1) Self nesting: use a caller stack saved/restored state model similar to
that of local_irq_save() and
It allows us to extend the coverage of vector finegrained masking
throughout softirq safe locking. This is especially interesting with
networking that makes extensive use of it.
It works the same way as local_bh_disable_mask():
bh = spin_lock_bh_mask(lock, BIT(NET_RX_SOFTIRQ));
[...]
In order to be able to mix and nest full and per vector softirq masking,
we need to be able to track the nesting state using a "full masking"
counter and a mask of "individual disabled vectors".
Start with introducing the full masking counter. For now it's a simple
mirror of softirq_count()
Remove the old protections that prevented softirqs from interrupting any
softirq-disabled context. Now that we can disable specific vectors on
a given piece of code, we want to be able to soft-interrupt those places
with other vectors.
Reviewed-by: David S. Miller
Signed-off-by: Frederic
On Tue, Feb 26, 2019 at 06:43:41PM +, James Morse wrote:
> From: Zhang Lei
>
> On the Fujitsu-A64FX cores ver(1.0, 1.1), memory access may cause
> an undefined fault (Data abort, DFSC=0b11). This fault occurs under
> a specific hardware condition when a load/store instruction performs an
There is no need to process softirqs if none of those pending are
enabled. Check about that early to avoid unnecessary overhead.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E .
It makes no more sense to check for redundant softirqs on because
trace_softirqs_on() is no more symmetrical to trace_softirqs_off().
Indeed trace_softirqs_off() is called whenever we know that all softirq
vectors have been disabled. And trace_softirqs_on() is called everytime
we enable at least
Now that we have full support from softirqs to perform per vector
masking, let's feed lockdep with the proper inputs and push the vector
numbers involved in a base softirq lock usage:
LOCK_ENABLED_SOFTIRQ: push local_softirq_enabled()
LOCK_USED_IN_SOFTIRQ: push curr->softirq_context, modified by
The common code between both versions of __local_bh_disable_ip(), whether
CONFIG_TRACE_IRQFLAGS is on or off, is going to grow up in order to
support vector masking granularity.
Merge these versions together to prepare for that.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
From: Frederic Weisbecker
Using the bottom-half masking APIs defined in linux/bottom-half.h won't
be possible without passing the relevant softirq vectors that are
currently defined in linux/interrupt.h
Yet we can't include linux/interrupt.h from linux/bottom-half.h due to
circular
From: Frederic Weisbecker
All softirqs must be set enabled on boot.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E . McKenney
Cc: David S . Miller
Cc: Ingo Molnar
Cc:
current->softirqs_enabled used to mean that either all or no softirqs
are enabled. Now things are getting a bit different with the new per
vector masking extension after which current->softirqs_enabled will
stay on as long as there is a single vector still enabled.
Let's adapt the check to the
We are going to need a nand version of softirq_pending_or() in order
to clear specific bits from the pending mask.
But instead of naming the mutators after their implementation, rather
name them after their high level purpose.
Suggested-by: Linus Torvalds
Reviewed-by: David S. Miller
mark_lock_irq() is going to deal with lock usages that gather multiple
softirq vectors at once. Therefore the validation through valid_state()
will need to handle expanded usage masks.
So enhance valid_state() to that purpose.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc:
Define the softirq vectors through macros so that we can later include
them in the automated definition of lockdep usage states.
Reviewed-by: David S. Miller
Signed-off-by: Frederic Weisbecker
Cc: Mauro Carvalho Chehab
Cc: Joel Fernandes
Cc: Thomas Gleixner
Cc: Pavan Kondeti
Cc: Paul E .
On Thu, Feb 28, 2019 at 04:34:37PM +0100, Greg Kroah-Hartman wrote:
> debugfs can now report an error code if something went wrong instead of
> just NULL. So if the return value is to be used as a "real" dentry, it
> needs to be checked if it is an error before dereferencing it.
>
> This is now
On Thu, Feb 28, 2019 at 8:45 PM Rob Herring wrote:
>
> On Tue, Feb 12, 2019 at 05:08:08PM +0530, Jagan Teki wrote:
> > Add missing dt-binding documentation for lm75 hwmon sensor.
> >
> > Signed-off-by: Jagan Teki
> > ---
> > Changes for v2:
> > - Add all compatible nodes available in lm75.
> >
Hi Thierry,
On Tue, Feb 19, 2019 at 1:57 AM Sam Ravnborg wrote:
>
> Hi Thierry
>
> > Pleas let me know if you any further comments on this?
> No further comments from my side, and I consider it
> ready to apply.
Would you please pick this?
Jagan.
Am 14.02.19 um 19:27 schrieb Dan Murphy:
> Migrate the m_can code to use the m_can_platform framework
> code.
>
> Signed-off-by: Dan Murphy
> ---
>
> v5 - Updated copyright, change m_can_classdev to m_can_priv, removed extra
> KCONFIG flag - https://lore.kernel.org/patchwork/patch/1033095/
>
>
On Thu, Feb 28, 2019 at 9:12 AM Frederic Weisbecker wrote:
>
> So this set should hopefully address all reviews from the v2, and
> fix all reports from the extremely useful (as always) Kbuild testing
> bot. It also completes support for all archs.
The one thing I'd still like to see is some
Greg Kroah-Hartman writes:
> On Thu, Feb 28, 2019 at 03:22:24PM +, Måns Rullgård wrote:
>> Greg Kroah-Hartman writes:
>>
>> > On Thu, Feb 28, 2019 at 02:33:44PM +, Mans Rullgard wrote:
>> >> Add a boolean property indicating that a device is hardwired to the
>> >> upstream port.
On Fri, Feb 22, 2019 at 06:04:51PM +, Will Deacon wrote:
> Will Deacon (3):
> asm-generic/io: Pass result of I/O accessor to __io_[p]ar()
> riscv: io: Update __io_[p]ar() macros to take an argument
> arm64: io: Hook up __io_par() for inX() ordering
Since we have the acks in place, I
On Thu, Feb 28, 2019 at 11:00:44PM +0530, Jagan Teki wrote:
> On Thu, Feb 28, 2019 at 8:45 PM Rob Herring wrote:
> >
> > On Tue, Feb 12, 2019 at 05:08:08PM +0530, Jagan Teki wrote:
> > > Add missing dt-binding documentation for lm75 hwmon sensor.
> > >
> > > Signed-off-by: Jagan Teki
[ ... ]
>
On Thu, Feb 28, 2019 at 11:36:21AM +0100, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> On Thu, Feb 28, 2019 at 11:32 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:42fd8df9d1d9 Add linux-nex
On Fri, Feb 01, 2019 at 01:36:07PM +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> The PCIE_AXI_WINDOW0 defines the translate window size for the request
> from EP side. Request outside of this window will be treated as
> unsupported request.
>
> Enlarge this window size from
On Thu, Feb 14, 2019 at 12:36:48PM +0530, Viresh Kumar wrote:
> On 14-02-19, 00:55, Yu Chen wrote:
> > Hi Viresh,
> > On Mon, Feb 11, 2019 at 04:03:07PM +0530, Viresh Kumar wrote:
> > > On 09-02-19, 20:02, Chen Yu wrote:
> > > > On Dell Inc. XPS13 9333, the BIOS changes the value of
> > > >
On Thu, Feb 28, 2019 at 05:03:09PM +0100, Dmitry Vyukov wrote:
> I am missing some knowledge about SMAP to answer this.
> In short, these tools insert lots of callbacks into runtime for memory
> accesses, function entry/exit, atomicops and some other. These
> callbacks can do things of different
On Wed, Jan 30, 2019 at 07:32:41PM +0300, Eugeniy Paltsev wrote:
> As of today we enable unaligned access unconditionally on ARCv2.
> Do this under a Kconfig option to allow disable it for test, benchmarking
> etc. Also while at it
>
> - Select HAVE_EFFICIENT_UNALIGNED_ACCESS
> - Although gcc
On Mon, Feb 25, 2019 at 08:03:42PM -0800, ndesaulni...@google.com wrote:
> Clang warns: vector initializers are not compatible with NEON intrinsics
> in big endian mode [-Wnonportable-vector-initialization]
>
> While this is usually the case, it's not an issue for this case since
> we're
Am 14.02.19 um 19:27 schrieb Dan Murphy:
> Add the TCAN4x5x SPI CAN driver. This device
> uses the Bosch MCAN IP core along with a SPI
> interface map. Leverage the MCAN common core
> code to manage the MCAN IP.
>
> This device has a special method to indicate a
> write/read operation on the
On Thu, Feb 28, 2019 at 08:49:57AM -0800, Linus Torvalds wrote:
> Yes, it is redundant (but harmlessly so) if no fault occurs.
Oooh, there's a label hidden in unsafe_put_user()...
And yes, objtool seems to miss that, damn. I'll go stare at that.
n:
>>>
>>> HEAD commit:42fd8df9d1d9 Add linux-next specific files for 20190228
>>> git tree: linux-next
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=179ba9e0c0
>>> kernel config: https://syzkaller.appspot.com/x/.config?
t;>>
> >>> Hello,
> >>>
> >>> syzbot found the following crash on:
> >>>
> >>> HEAD commit:42fd8df9d1d9 Add linux-next specific files for 20190228
> >>> git tree: linux-next
> >>> console output: https
, Feb 28, 2019 at 11:32 AM syzbot
>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> syzbot found the following crash on:
>>>>>
>>>>> HEAD commit:42fd8df9d1d9 Add linux-next specific files for 2
On Thu, Feb 14, 2019 at 11:21:13AM +0100, Rafael J. Wysocki wrote:
> On Wed, Feb 13, 2019 at 5:44 PM Yu Chen wrote:
> >
> > Hi Rafael,
> > On Mon, Feb 11, 2019 at 11:41:26AM +0100, Rafael J. Wysocki wrote:
> > > On Sat, Feb 9, 2019 at 12:54 PM Chen Yu wrote:
> > > >
> > > > On Dell Inc. XPS13
On Thu, Feb 28, 2019 at 10:59:19AM -0500, Len Brown wrote:
> The SDM is like software -- usually (but not always) you are better
> off with the latest version:-)
If only it existed as a .tex file in a git repo. It has been very useful
to have older versions around a number of times.
Em Thu, Feb 28, 2019 at 10:30:09PM +0800, Jin Yao escreveu:
> Jiri points out that we don't need any time checking and time string
> parsing if the --time option is not set. That makes sense.
>
> This patch refactors the time range parsing code, move the duplicated
> code from perf report and
Wolfgang
On 2/28/19 11:33 AM, Wolfgang Grandegger wrote:
> Am 14.02.19 um 19:27 schrieb Dan Murphy:
>> Migrate the m_can code to use the m_can_platform framework
>> code.
>>
>> Signed-off-by: Dan Murphy
>> ---
>>
>> v5 - Updated copyright, change m_can_classdev to m_can_priv, removed extra
>>
On some problematic platforms, the _PPC notifier is
only delivered to one CPU, which might cause information
inconsistent between CPUs within the package. Thus introduce a boot up
parameter to broadcast this _PPC notifier onto all
online CPUs.
Signed-off-by: Chen Yu
---
On Dell Inc. XPS13 9333, the BIOS changes the value of
MSR_IA32_MISC_ENABLE_TURBO_DISABLE at runtime (e.g., when
the power source changes), the maximum frequency of the
CPU is not updated accordingly. This is due to the policy's
cpuinfo.max is not updated when _PPC notifier fires.
Firstly we
On 02/28/2019 05:25 PM, H.J. Lu wrote:
> On Thu, Feb 28, 2019 at 8:18 AM Daniel Borkmann wrote:
>> On 02/28/2019 01:53 PM, H.J. Lu wrote:
>>> On Thu, Feb 28, 2019 at 3:27 AM David Woodhouse wrote:
On Thu, 2019-02-28 at 03:12 -0800, tip-bot for Daniel Borkmann wrote:
> Commit-ID:
On Dell Inc. XPS13 9333, the BIOS changes the value of
MSR_IA32_MISC_ENABLE_TURBO_DISABLE at runtime (e.g., when
the power source changes), the maximum frequency of the
CPU is not updated accordingly. This is due to the policy's
cpuinfo.max is not updated when _PPC notifier fires.
Fix this
On 26/02/2019 20:44, Nick Desaulniers wrote:
On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
wrote:
On Tue, 26 Feb 2019 at 05:03, wrote:
Clang warns: vector initializers are not compatible with NEON intrinsics
in big endian mode [-Wnonportable-vector-initialization]
While this is usually
On Thu, 2019-02-28 at 17:02 +, Junge, Terry wrote:
> This could also be a parser error. In the HID specification section 6.2.2.8 it
> states that the last declared Usage Page is applied to Usages when the Main
> item is encountered.
>
> "If the bSize field = 1 or 2 then the Usage is
On Thu, Feb 28, 2019 at 06:51:14PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 28, 2019 at 08:49:57AM -0800, Linus Torvalds wrote:
> > Yes, it is redundant (but harmlessly so) if no fault occurs.
>
> Oooh, there's a label hidden in unsafe_put_user()...
>
> And yes, objtool seems to miss that,
Wolfgang
On 2/28/19 11:50 AM, Wolfgang Grandegger wrote:
>
>
> Am 14.02.19 um 19:27 schrieb Dan Murphy:
>> Add the TCAN4x5x SPI CAN driver. This device
>> uses the Bosch MCAN IP core along with a SPI
>> interface map. Leverage the MCAN common core
>> code to manage the MCAN IP.
>>
>> This
bot found the following crash on:
> > >
> > > HEAD commit:42fd8df9d1d9 Add linux-next specific files for 20190228
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=179ba9e0c0
> > > kernel
On Thu, Feb 28, 2019 at 09:17:28AM -0800, Eric Biggers wrote:
> On Thu, Feb 28, 2019 at 04:34:37PM +0100, Greg Kroah-Hartman wrote:
> > debugfs can now report an error code if something went wrong instead of
> > just NULL. So if the return value is to be used as a "real" dentry, it
> > needs to
On Thu, Feb 28, 2019 at 05:34:25PM +, Måns Rullgård wrote:
> >> --- a/drivers/usb/core/hub.c
> >> +++ b/drivers/usb/core/hub.c
> >> @@ -2392,6 +2392,14 @@ static void set_usb_port_removable(struct
> >> usb_device *udev)
> >> break;
> >> }
> >>
> >> + /*
> >> +
These changes fixed a checkpatch error for space required before the
open brace '{' as well as a warning for suspect code indent for
conditional statements.
Signed-off-by: Oscar Gomez Fuente
---
drivers/staging/rtl8192e/rtllib_wx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Thu, Feb 28, 2019 at 9:58 AM Daniel Borkmann wrote:
>
> On 02/28/2019 05:25 PM, H.J. Lu wrote:
> > On Thu, Feb 28, 2019 at 8:18 AM Daniel Borkmann
> > wrote:
> >> On 02/28/2019 01:53 PM, H.J. Lu wrote:
> >>> On Thu, Feb 28, 2019 at 3:27 AM David Woodhouse
> >>> wrote:
> On Thu,
On 2/28/19 9:47 AM, Guenter Roeck wrote:
> On Wed, Jan 30, 2019 at 07:32:41PM +0300, Eugeniy Paltsev wrote:
>> As of today we enable unaligned access unconditionally on ARCv2.
>> Do this under a Kconfig option to allow disable it for test, benchmarking
>> etc. Also while at it
>>
>> - Select
On 02/28/2019 07:09 PM, H.J. Lu wrote:
> On Thu, Feb 28, 2019 at 9:58 AM Daniel Borkmann wrote:
>> On 02/28/2019 05:25 PM, H.J. Lu wrote:
>>> On Thu, Feb 28, 2019 at 8:18 AM Daniel Borkmann
>>> wrote:
On 02/28/2019 01:53 PM, H.J. Lu wrote:
> On Thu, Feb 28, 2019 at 3:27 AM David
Hi Jeremy
On 27/02/2019 01:05, Jeremy Linton wrote:
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off-by: Jeremy Linton
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
diff --git
801 - 900 of 1382 matches
Mail list logo
