This patch dumps SPI registers on transfer error or timeout for debug
purpose.
Signed-off-by: Sowjanya Komatineni
---
drivers/spi/spi-tegra114.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c
index
On Thu, 04 Apr 2019 07:26:53 PDT (-0700), rost...@goodmis.org wrote:
On Thu, 4 Apr 2019 17:02:10 +0300
"Dmitry V. Levin" wrote:
On Mon, Apr 01, 2019 at 09:41:07AM -0400, Steven Rostedt wrote:
> From: "Dmitry V. Levin"
>
> RISC-V syscall arguments are located in orig_a0,a1..a5 fields
> of
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git
tags/riscv-for-linus-5.1-rc4
for you to fetch changes up to
Add a variety of useful Cortex-A53 PMU specific events which were
recently found useful during a debug session.
Signed-off-by: Florian Fainelli
---
arch/arm64/kernel/perf_event.c | 118 -
1 file changed, 116 insertions(+), 2 deletions(-)
diff --git
In preparation for adding processor specific attributes, group the ARMv8
PMU v3 common events into a macro that can be re-used to fill up an
array of attributes.
Signed-off-by: Florian Fainelli
---
arch/arm64/kernel/perf_event.c | 123 +
1 file changed, 63
Hi all,
This patch series adds support for the Cortex-A53 micro architectural
events that I recently had to use for some debugging exercise.
Events from 0xC0 - 0xD2 are exposed, others could easily be added later
if we wanted to.
Thanks!
Florian Fainelli (2):
arm64: perf: Group common ARMv8
On Fri, Apr 5, 2019 at 12:39 AM Johannes Weiner wrote:
>
> On Thu, Apr 04, 2019 at 11:30:17AM +0800, Zhaoyang Huang wrote:
> > From: Zhaoyang Huang
> >
> > In previous implementation, the number of refault pages is used
> > for judging the refault period of each page, which is not precised as
>
On Tue, Apr 02, 2019 at 02:33:12PM -0700, Randy Dunlap wrote:
> Hi,
>
> nits/typos below:
Hey thanks for reviewing this Randy, first time I read it I got mixed up
and thought the nits were against Kees' additions but I was wrong,
thanks again.
Tobin
On Tue, Apr 02, 2019 at 08:35:54PM +0800, Qii Wang wrote:
> This series are based on 5.1-rc1 and the patch
> https://patchwork.kernel.org/patch/10856987/(for dts)
> We provide six patches to support mt8183 IC.
>
> Main changes compared to v5:
> --add i2c controller nodes in mt8183.dtsi
> --add a
> -Original Message-
> From: Alex Williamson
> Sent: Thursday, April 4, 2019 3:44 PM
> To: Parav Pandit
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> kwankh...@nvidia.com; c...@nvidia.com
> Subject: Re: [PATCHv1 7/7] vfio/mdev: Fix race conditions with mdev device
> life
Hi Guenter,
On Thu, 4 Apr 2019 14:26:18 -0700 Guenter Roeck wrote:
>
> The original subject is "[PATCH] I2C: Move hwmon drivers (2/3)", and
> I consider it quite pointless to include the "[PATCH] " prefix.
> Same for the other tag.
True, sorry for the noise.
--
Cheers,
Stephen Rothwell
Hi all,
Today's linux-next merge of the btrfs-kdave tree got a conflict in:
fs/btrfs/props.c
between commits:
50398fde997f ("btrfs: prop: fix zstd compression parameter validation")
272e5326c783 ("btrfs: prop: fix vanished compression property after failed
set")
from the btrfs-fixes
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86/stackguards
head: f06282dacdf39de480ede989a689743402e1110c
commit: 2e2333a2ed97c5df6bac64f689a1d4695e8e9ec9 [19/29] x86/exceptions: Split
debug IST stack
config: x86_64-randconfig-x003-201913 (attached as .config)
I sent this out previously in a series with a keyboard backlight driver
(https://lkml.org/lkml/2019/4/4/1370), but the backlight driver is
still in flux, and I wanted to get this committed ASAP. Thus I'm
sending this as a separate series, in hopes that this can be
expedited.
The current API for
On Thu, Apr 4, 2019 at 6:47 PM Borislav Petkov wrote:
> On Thu, Apr 04, 2019 at 06:31:37PM +0200, Jann Horn wrote:
> > Uuuh. I *definitely* tested this. I ran this yesterday evening on my
> > home machine, on top of commit
> > 14c741de93861749dfb60b4964028541f5c506ca from Linus' tree, plus two
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86/stackguards
head: f06282dacdf39de480ede989a689743402e1110c
commit: 2e2333a2ed97c5df6bac64f689a1d4695e8e9ec9 [19/29] x86/exceptions: Split
debug IST stack
config: x86_64-randconfig-x002-201913 (attached as .config)
On Thu, Apr 4, 2019 at 3:05 PM Pavel Machek wrote:
>
> On Thu 2019-04-04 14:48:35, Dmitry Torokhov wrote:
> > On Thu, Apr 4, 2019 at 1:42 PM Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > > > > And what to do if internal keyboard is not platform but USB? Like
> > > > > > Google "Whiskers"? (I
On Thu, 4 Apr 2019 17:40:22 +0100, Will Deacon wrote:
> Hi Akira,
>
> On Fri, Apr 05, 2019 at 12:58:36AM +0900, Akira Yokosawa wrote:
>> On Tue, 2 Apr 2019 14:03:46 +0100, Will Deacon wrote:
>>> On Tue, Mar 26, 2019 at 04:41:16PM -0700, Paul E. McKenney wrote:
From: Will Deacon
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and determine whether the code under test behaves as expected; this also
provides a way to group together related test cases in test suites (here
we call
Add support for assertions which are like expectations except the test
terminates if the assertion is not satisfied.
The idea with assertions is that you use them to state all the
preconditions for your test. Logically speaking, these are the premises
of the test case, so if a premise isn't true,
Add documentation for KUnit, the Linux kernel unit testing framework.
- Add intro and usage guide for KUnit
- Add API reference
Signed-off-by: Felix Guo
Signed-off-by: Brendan Higgins
---
Documentation/index.rst | 1 +
Documentation/kunit/api/index.rst | 16 ++
From: Iurii Zaikin
KUnit tests for initialized data behavior of proc_dointvec that is
explicitly checked in the code. Includes basic parsing tests including
int min/max overflow.
Signed-off-by: Iurii Zaikin
Signed-off-by: Brendan Higgins
---
kernel/Makefile | 2 +
kernel/sysctl-test.c
A number of test features need to do pretty complicated string printing
where it may not be possible to rely on a single preallocated string
with parameters.
So provide a library for constructing the string as you go similar to
C++'s std::string.
Signed-off-by: Brendan Higgins
---
From: Felix Guo
The ultimate goal is to create minimal isolated test binaries; in the
meantime we are using UML to provide the infrastructure to run tests, so
define an abstract way to configure and run tests that allow us to
change the context in which tests are built without affecting the
2019-03-22 11:57+, Suthikulpanit, Suravee:
> This series is one of the prerequisites for supporting AMD AVIC with
> in-kernel irqchip (kernel_irqchip=on).
>
> Since AVIC does not support ExtINT interrupt, which is required during
> the booting phase of Windows and FreeBSD VMs (e.g. PIT -> PIC
Add entry for the new proc sysctl KUnit test to the PROC SYSCTL section.
Signed-off-by: Brendan Higgins
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index fc2cedbd9b43e..03054e4c6386c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12523,6
Hi all,
Today's linux-next merge of the at91 tree got a conflict in:
arch/arm/mach-at91/pm.c
between commit:
ba5e60c9b75d ("arm/mach-at91/pm : fix possible object reference leak")
from the at91-fixes tree and commit:
c3f5b8fde71f ("ARM: at91: pm: introduce at91_soc_pm structure")
from
On Thu, 14 Feb 2019, Thomas Gleixner wrote:
> On Thu, 14 Feb 2019, Jan H. Schönherr wrote:
>
> Cc+: Linus (he wrote the original implementation and might have opinions)
>
> > Some systems experience regular interruptions (60 Hz SMI?), that prevent
> > the quick PIT calibration from succeeding:
On Thu 2019-04-04 14:48:35, Dmitry Torokhov wrote:
> On Thu, Apr 4, 2019 at 1:42 PM Pavel Machek wrote:
> >
> > Hi!
> >
> > > > > And what to do if internal keyboard is not platform but USB? Like
> > > > > Google "Whiskers"? (I am not sure why you decided to drop my mention
> > > > > of internal
* Jacek Anaszewski [190404 20:12]:
> Tony,
>
> On 3/21/19 3:28 PM, Dan Murphy wrote:
> > Update the properties for the lm3532 device node for droid4.
> > With this change the backlight LED string and the keypad
> > LED strings will be controlled separately.
> >
> > Signed-off-by: Dan Murphy
>
This fixes multiple issues in buffer_pipe_buf_ops:
- The ->steal() handler must not return zero unless the pipe buffer has
the only reference to the page. But generic_pipe_buf_steal() assumes
that every reference to the pipe is tracked by the page's refcount,
which isn't true for these
On Fri, Apr 05, 2019 at 07:29:14AM +1100, Tobin C. Harding wrote:
> > __d_alloc() is not holding ->d_lock, since the object is not visible to
> > anybody else yet; with your changes it *is* visible.
>
> I don't quite understand this comment. How is the object visible? The
> constructor is only
In some circumstances drivers register clks early and don't have access
to a struct device because the device model isn't initialized yet. Add
an API to let drivers register clks associated with a struct device_node
so that these drivers can participate in getting parent clks through DT.
Cc:
Some clk providers are simple DT nodes that only have a 'clocks'
property without having an associated 'clock-names' property. In these
cases, we want to let these clk providers point to their parent clks
without having to dereference the 'clocks' property at probe time to
figure out the parent's
Convert this driver to a more modern way of specifying parents now that
we have a way to specify clk parents by DT index. This lets us nicely
avoid a problem where a parent clk name isn't know because the parent
clk hasn't been registered yet.
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell
Split out the body of the clk_register() function so it can be shared
between the different types of registration APIs (DT, device).
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hugo
Cc: Chen-Yu Tsai
Cc: Rob Herring
Signed-off-by: Stephen Boyd
---
The common clk framework is lacking in ability to describe the clk
topology without specifying strings for every possible parent-child
link. There are a few drawbacks to the current approach:
1) String comparisons are used for everything, including describing
topologies that are 'local' to a
There are a couple warts with clk parent handling in the common clk
framework. This patch series addresses one of those warts, parent-child
linkages. We use strings for all parent-child linkages, and this leads
to poorly written code that extracts clk names from struct clk pointers
and makes clk
In addition to looking for DT based parents, support clkdev based
clk_lookups. This should allow non-DT based clk drivers to participate
in the parent lookup process.
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hugo
Cc: Chen-Yu Tsai
Signed-off-by:
We recently introduced a change to support devm clk lookups. That change
introduced a code-path that used clk_find() without holding the
'clocks_mutex'. Unfortunately, clk_find() iterates over the 'clocks'
list and so we need to prevent the list from being modified while
iterating over it by
On 4/4/19 5:57 PM, Christopher Lameter wrote:
> On Thu, 4 Apr 2019, Vlastimil Babka wrote:
>
>> I looked a bit at SLUB debugging capabilities and first thing I noticed is
>> there's no static key guarding the runtime enablement as is common for
>> similar
>> debugging functionalities, so here's
On Thu, Apr 4, 2019 at 1:42 PM Pavel Machek wrote:
>
> Hi!
>
> > > > And what to do if internal keyboard is not platform but USB? Like
> > > > Google "Whiskers"? (I am not sure why you decided to drop my mention
> > > > of internal USB keyboards completely off your reply).
> > >
> > > I don't
Hi Carlos / all,
On Thu, Apr 04, 2019 at 04:50:08PM -0400, Carlos O'Donell wrote:
> > > > +/* Signature required before each abort handler code. */
> > > > +#define RSEQ_SIG 0x53053053
> > >
> > > Why isn't this a mips-specific op code?
> >
> > MIPS also has a literal pool just before the
The LLVM linker (ld.lld) defaults to removing local relocations, which
causes KASLR boot failures. ld.bfd and ld.gold already handle this
correctly. This adds the explicit instruction "--discard-none" during
the link phase. There is no change in output for ld.bfd and ld.gold,
but ld.lld now
On 2019-04-02 07:31, Neil Horman wrote:
> On Mon, Apr 01, 2019 at 10:50:03AM -0400, Paul Moore wrote:
> > On Fri, Mar 15, 2019 at 2:35 PM Richard Guy Briggs wrote:
> > > Audit events could happen in a network namespace outside of a task
> > > context due to packets received from the net that
2019-03-22 11:57+, Suthikulpanit, Suravee:
> This series is one of the prerequisites for supporting AMD AVIC with
> in-kernel irqchip (kernel_irqchip=on).
>
> Since AVIC does not support ExtINT interrupt, which is required during
> the booting phase of Windows and FreeBSD VMs (e.g. PIT -> PIC
Remove an exceptional & on function names, otherwise they are used as
pointers without &.
Issue suggested using Coccinelle.
Signed-off-by: Madhumitha Prabakaran
---
.../vc04_services/bcm2835-camera/controls.c | 58 +--
1 file changed, 29 insertions(+), 29 deletions(-)
diff
From: Yazen Ghannam
To enable CPPC on a processor, the OS should write a value "1" to the
CPPC Enable register. Add support for this register.
Signed-off-by: Yazen Ghannam
[ carved out into a patch, cleaned up, productized ]
Signed-off-by: Janakarajan Natarajan
---
drivers/acpi/cppc_acpi.c |
From: Yazen Ghannam
Some CPPC registers can be used to configure the platform. To enable this,
create macros to define the show, store routines and create sysfs entries
with R/W permission.
Signed-off-by: Yazen Ghannam
[ carved into a patch, cleaned up, productized ]
Signed-off-by: Janakarajan
On Fri, Apr 05, 2019 at 07:54:38AM +1100, Stephen Rothwell wrote:
> Hi Guenter,
>
> In commit
>
> 742ad88f0440 ("hwmon: (smsc47b397) Use request_muxed_region for Super-IO
> accesses")
>
> Fixes tag
>
> Fixes: 8d5d45fb1468 ("I2C: Move hwmon drivers (2/3)")
>
The original subject is
From: Yazen Ghannam
The cppc_set_perf() currently only works for DESIRED_PERF. To make it
generic, pass in the index of the register being accessed.
Also, rename cppc_set_perf() to cppc_set_reg(). This is in preparation
for it to be used for more than just the DESIRED_PERF register.
CPPC (Collaborative Processor Performance Control) offers optional
registers which can be used to tune the system based on energy and/or
performance requirements.
Newer AMD processors add support for a subset of these optional CPPC
registers, based on ACPI v6.1.
The following are the supported
Add attributes for registers that are supported by the platform. This prevents
unsupported optional registers from having sysfs entries created.
Also, add a macro REG_SUPPORTED which will decide on the check to perform
based on the type of register.
Signed-off-by: Janakarajan Natarajan
---
From: Yazen Ghannam
Newer AMD processors support a subset of the optional CPPC registers.
Create show, store and helper routines for supported CPPC registers.
Signed-off-by: Yazen Ghannam
[ carved out into a patch, cleaned up, productized ]
Signed-off-by: Janakarajan Natarajan
---
From: Yazen Ghannam
The show_cppc_data macro implicity uses define_one_cppc_ro. This will
prevent the creation of an attribute with read and write permissions.
Create a separate macro that defines a show attribute and creates
a read-only sysfs entry. This is in preparation for adding a macro
to
CPC_SUP_BUFFER_ONLY ensures that an expected BUFFER only register has a
register type of ACPI_TYPE_BUFFER and is not NULL.
Signed-off-by: Janakarajan Natarajan
---
drivers/acpi/cppc_acpi.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/acpi/cppc_acpi.c
Hi Stephen,
On Fri, 5 Apr 2019 07:48:43 +1100
Stephen Rothwell wrote:
> Hi Lee,
>
> In commit
>
> 20bb907f7dc8 ("mfd: twl-core: Disable IRQ while suspended")
>
> Fixes tag
>
> Fixes: 6e2bd956936 ("i2c: omap: Use noirq system sleep pm ops to idle
> device for suspend")
>
> has these
On Wed, Apr 03, 2019 at 06:19:21PM +0100, Al Viro wrote:
> On Wed, Apr 03, 2019 at 06:08:11PM +0100, Al Viro wrote:
>
> > Oh, *brilliant*
> >
> > Let's do d_invalidate() on random dentries and hope they go away.
> > With convoluted and brittle logics for deciding which ones to
> > spare, which
Function name is otherwise used as pointers without &.
Issue suggested by Coccinelle.
Signed-off-by: Madhumitha Prabakaran
---
drivers/staging/rtlwifi/pci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtlwifi/pci.c b/drivers/staging/rtlwifi/pci.c
On Sat, Mar 30, 2019 at 09:14:36AM +0530, Neeraj Upadhyay wrote:
> On 3/30/19 2:57 AM, Paul E. McKenney wrote:
> >On Fri, Mar 29, 2019 at 07:52:15PM +0530, Neeraj Upadhyay wrote:
> >>
> >>
> >>On 3/29/19 6:58 PM, Mukesh Ojha wrote:
> >>>
> >>>On 3/29/2019 4:57 PM, Neeraj Upadhyay wrote:
> Only
On Thu, 28 Mar 2019, Singh, Brijesh wrote:
> > This ensures that the address and length provided to DBG_DECRYPT and
> > DBG_ENCRYPT do not cause an overflow.
> >
> > At the same time, pass the actual number of pages pinned in memory to
> > sev_unpin_memory() as a cleanup.
> >
> > Reported-by:
On Thu, Apr 04, 2019 at 09:44:24PM +0100, Stuart Swales wrote:
> On 04/04/2019 11:35, Russell King - ARM Linux admin wrote:
> Have posted on the RISC OS Open site. I imagine some people will
> complain just because they can. Can't see a need for it in new kernels
> myself; people can always use
On Wed, 20 Mar 2019, Singh, Brijesh wrote:
> > get_num_contig_pages() could potentially overflow int so make its type
> > consistent with its usage.
> >
> > Reported-by: Cfir Cohen
> > Signed-off-by: David Rientjes
> > ---
> > arch/x86/kvm/svm.c | 10 +-
> > 1 file changed, 5
Hi Guenter,
In commit
742ad88f0440 ("hwmon: (smsc47b397) Use request_muxed_region for Super-IO
accesses")
Fixes tag
Fixes: 8d5d45fb1468 ("I2C: Move hwmon drivers (2/3)")
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1
On Wed, 13 Mar 2019, Barret Rhoden wrote:
> > It is very expensive. VMSP exchanges 4K segments via RDMA between servers
> > to build a large address space and run a kernel in the large address
> > space. Using smaller segments can cause a lot of
> > "cacheline" bouncing (meaning transfers of 4K
On 4/4/19 10:16 AM, Josh Poimboeuf wrote:
> On Wed, Apr 03, 2019 at 03:29:17PM -0700, Randy Dunlap wrote:
>> On 4/3/19 1:53 PM, Josh Poimboeuf wrote:
>>> On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
On 4/3/19 1:24 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes
On Tue, Apr 02, 2019 at 04:49:11PM +0200, Andrea Parri wrote:
> On Tue, Mar 26, 2019 at 04:41:20PM -0700, Paul E. McKenney wrote:
> > Given that synchronize_rcu_expedited() is supported, this commit adds
> > support for synchronize_srcu_expedited().
> >
> > Signed-off-by: Paul E. McKenney
> >
On 3/25/19 11:54 AM, Mathieu Desnoyers wrote:
Hi Carlos,
- On Mar 22, 2019, at 4:09 PM, Carlos O'Donell codon...@redhat.com wrote:
[...]
I took care of all your comments for an upcoming round of patches, except the
following that remain open (see answer inline). I'm adding Linux
Hi Lee,
In commit
20bb907f7dc8 ("mfd: twl-core: Disable IRQ while suspended")
Fixes tag
Fixes: 6e2bd956936 ("i2c: omap: Use noirq system sleep pm ops to idle device
for suspend")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: c6e2bd956936 ("i2c: omap: Use
Greg KH, le jeu. 04 avril 2019 22:35:49 +0200, a ecrit:
> On Thu, Apr 04, 2019 at 08:45:29PM +0100, Okash Khawaja wrote:
> > diff --git a/include/linux/selection.h b/include/linux/selection.h
> > index a8f5b97b216f..171d77dfc825 100644
> > --- a/include/linux/selection.h
> > +++
On 04/04/2019 11:35, Russell King - ARM Linux admin wrote:
> Hi,
>
> Recently, a couple of issues have been identified in fs/adfs:
>
> 1. Filename truncation may not work as it should, and Linus has
>apparently expressed a desire to kill this off.
>
> 2. Scanning the ADFS map for disc
On Thu, 4 Apr 2019 00:02:22 +
Parav Pandit wrote:
> > -Original Message-
> > From: Alex Williamson
> > Sent: Wednesday, April 3, 2019 4:27 PM
> > To: Parav Pandit
> > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > kwankh...@nvidia.com; c...@nvidia.com
> > Subject: Re:
On Thu, 4 Apr 2019, Hook, Gary wrote:
> Enablement of AMD's Secure Memory Encryption feature is determined
> very early in the boot cycle. Part of this procedure involves scanning
> the command line for the paramater 'mem_encrypt'.
>
> To determine intended state, the function sme_enable() uses
Hi!
> > > And what to do if internal keyboard is not platform but USB? Like
> > > Google "Whiskers"? (I am not sure why you decided to drop my mention
> > > of internal USB keyboards completely off your reply).
> >
> > I don't have answers for everything. Even if you have USB keyboard, you'll
> >
On Wed, Apr 03, 2019 at 04:03:54PM -0700, Shakeel Butt wrote:
> The callers of cgroup_migrate_prepare_dst() correctly call
> cgroup_migrate_finish() for success and failure cases both. No need to
> call it in cgroup_migrate_prepare_dst() in failure case.
>
> Signed-off-by: Shakeel Butt
Applied
Daniel Lezcano writes:
> The module support for the thermal subsystem makes little sense:
> - some subsystems relying on it are not modules, thus forcing the
>framework to be compiled in
> - it is compiled in for almost every configs, the remaining ones
>are a few platforms where I
On Thu, Apr 04, 2019 at 08:45:29PM +0100, Okash Khawaja wrote:
> diff --git a/include/linux/selection.h b/include/linux/selection.h
> index a8f5b97b216f..171d77dfc825 100644
> --- a/include/linux/selection.h
> +++ b/include/linux/selection.h
> @@ -11,13 +11,12 @@
> #include
> #include
>
>
Hi!
> > > Because I need to understand why you believe that device name for
> > > kbd_backlight matters, and having wilco::kbd_backlight is a bad idea,
> > > but, for example, having max77650::kbd_backlight is perfectly fine if
> > > somebody decided to wire it in this way.
> >
> >
On 4/2/19 3:08 AM, Florian Weimer wrote:
* Michael Ellerman:
I'm a bit vague on what we're trying to do here.
But it seems like you want some sort of "eye catcher" prior to the branch?
That value is a valid instruction on current CPUs (rlwimi.
r5,r24,6,1,9), and even if it wasn't it could
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.1-rc4
with top-most commit 58b0cf8e2418c05ed277c83b5529bd0568bfcc78
Merge branch 'pm-tools'
on top of commit 79a3aaa7b82e3106be97842dedfd8429248896e6
Linux 5.1-rc3
to receive
On Thu, Apr 04, 2019 at 11:19:46AM -0700, Paul E. McKenney wrote:
[snip]
> > > > > Further, from the herd simulator output (below), according to the
> > > > > "States",
> > > > > r1==1 means P1() AFAICS would have already finished the the read and
> > > > > set the
> > > > > r1 register to 1.
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-5.1-rc4
with top-most commit b59fb7ef5240c301ca8b5b70d4298c0f053bb0c3
Merge branch 'acpica' into acpi
on top of commit aa9aaa4d61c0048d3faad056893cd7860bbc084c
ACPI: use different
On Wed, Apr 03, 2019 at 06:48:55PM +0100, Al Viro wrote:
> On Wed, Apr 03, 2019 at 06:19:21PM +0100, Al Viro wrote:
> > On Wed, Apr 03, 2019 at 06:08:11PM +0100, Al Viro wrote:
> >
> > > Oh, *brilliant*
> > >
> > > Let's do d_invalidate() on random dentries and hope they go away.
> > > With
Enablement of AMD's Secure Memory Encryption feature is determined
very early in the boot cycle. Part of this procedure involves scanning
the command line for the paramater 'mem_encrypt'.
To determine intended state, the function sme_enable() uses library
functions cmdline_find_option() and
On Thu, Apr 4, 2019 at 1:20 PM Pavel Machek wrote:
>
> On Thu 2019-04-04 13:13:34, Dmitry Torokhov wrote:
> > On Thu, Apr 4, 2019 at 1:06 PM Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > > > > It is *function* and maybe color that userspace is interested in,
> > > > > > and
> > > > > > here
gt; > > suitable for that. "platform" is.
> > > > > >
> > > > > > Pavel, who exactly wants this and why? Looking at today's -next I
> > > > > > see:
> > > > > >
> > > > > > dtor@dtor-ws:~/kern
On Thu 2019-04-04 13:13:34, Dmitry Torokhov wrote:
> On Thu, Apr 4, 2019 at 1:06 PM Pavel Machek wrote:
> >
> > Hi!
> >
> > > > > It is *function* and maybe color that userspace is interested in, and
> > > > > here we have proper standardization in form of "kbd_backlight". Device
> > > > > name
On Thu, Apr 04, 2019 at 03:01:14PM -0400, Vince Weaver wrote:
>
> I do have a lot of this automated already from tracking down past bugs,
> but it turns out that most of the fuzzer-found bugs aren't deterministic
> so it doesn't always work.
>
> For example this bug, while I can easily repeat
On Thu, Apr 04, 2019 at 08:44:11PM +0200, Miroslav Benes wrote:
> GCC 9 introduces a new option, -flive-patching. It disables certain
> optimizations which could make a compilation unsafe for later live
> patching of the running kernel.
>
> The option is used only if CONFIG_LIVEPATCH is enabled
On 4/2/19 2:02 AM, Michael Ellerman wrote:
Mathieu Desnoyers writes:
Hi Carlos,
- On Mar 22, 2019, at 4:09 PM, Carlos O'Donell codon...@redhat.com wrote:
...
[...]
+++ b/sysdeps/unix/sysv/linux/powerpc/bits/rseq.h
[...]
+/* Signature required before each abort handler code. */
On Thu, Apr 4, 2019 at 1:06 PM Pavel Machek wrote:
>
> Hi!
>
> > > > It is *function* and maybe color that userspace is interested in, and
> > > > here we have proper standardization in form of "kbd_backlight". Device
> > > > name is, well, device name. It should uniquely identify the device led
Tony,
On 3/21/19 3:28 PM, Dan Murphy wrote:
Update the properties for the lm3532 device node for droid4.
With this change the backlight LED string and the keypad
LED strings will be controlled separately.
Signed-off-by: Dan Murphy
---
v5 - No change -
gt; > > > the first place. But it happened. We want all backlights for the
> > > > > > system keyboard to use common name, and "chromeos" is not really
> > > > > > suitable for that. "platform" is.
> > > > >
> > >
On Thu, Apr 4, 2019 at 6:39 AM Steven Rostedt wrote:
>
> On Wed, 3 Apr 2019 17:32:49 -0700
> Matthew Garrett wrote:
>
>
> > +static void tracefs_destroy_inode(struct inode *inode)
> > +{
> > + if S_ISREG(inode->i_mode)
>
> Can we please put parenthesis around the condition. I know that the
board to use common name, and "chromeos" is not really
> > > > > suitable for that. "platform" is.
> > > >
> > > > Pavel, who exactly wants this and why? Looking at today's -next I see:
> > > >
> > > > dtor@dtor-ws:~/k
Hi!
> > > It is *function* and maybe color that userspace is interested in, and
> > > here we have proper standardization in form of "kbd_backlight". Device
> > > name is, well, device name. It should uniquely identify the device led
> > > is attached to, but otherwise is rarely interesting. If
On Sun, 24 Feb 2019 18:40:10 -0300
Camylla Gonçalves Cantanheide wrote:
> This commit align broken line to match upper line parenthesis,
> in lines 80, 130, 237, 242, 255, 264 and 293. Solves the checkpatch.pl's
> message:
>
> CHECK: Alignment should match open parenthesis
>
> In lines 130,
On Thu, Apr 4, 2019 at 12:19 PM Pavel Machek wrote:
>
> On Thu 2019-04-04 12:05:39, Dmitry Torokhov wrote:
> > On Thu, Apr 4, 2019 at 11:59 AM Pavel Machek wrote:
> > >
> > > On Thu 2019-04-04 11:55:27, Dmitry Torokhov wrote:
> > > > On Thu, Apr 4, 2019 at 11:41 AM Nick Crews wrote:
> > > > >
>
Add PCIe host controller driver for DesignWare core based
PCIe controller IP present in Tegra194.
Signed-off-by: Vidya Sagar
---
Changes since [v1]:
* Changed CONFIG_PCIE_TEGRA194 from 'y' to 'm'
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Add support for Synopsys DesignWare core IP based PCIe host controller
present in Tegra194 SoC.
Signed-off-by: Vidya Sagar
---
Changes since [v1]:
* Made CONFIG_PCIE_TEGRA194 as 'm' by default from its previous 'y' state
* Modified code as per changes made to DT documentation
* Refactored code
101 - 200 of 1406 matches
Mail list logo
