The patch
regulator: da9052: Convert to regulator core's simplified DT parsing code
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
regulator: da9055: Convert to regulator core's simplified DT parsing code
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
regulator: 88pm800: Get rid of struct pm800_regulators
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Fri, Mar 15, 2019 at 9:43 AM Steven Rostedt wrote:
>
> On Thu, 14 Mar 2019 21:36:43 -0700
> Daniel Colascione wrote:
>
> > On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> > >
> > > On Thu, 14 Mar 2019 13:49:11 -0700
> > > Sultan Alsawaf wrote:
> > >
> > > > Perhaps I'm missing
On 3/15/19 11:31 AM, Alexandre Bailon wrote:
>>> This series is sent as RFC mostly because the current support of i.MX SoC
>>> won't
>>> benefit of busfreq framework, because the clocks' driver don't support
>>> interconnect / dram frequency scaling.
>>> As exemple, this series implements busfreq
Quoting Jerome Brunet (2019-03-15 03:01:53)
> On Tue, 2019-02-26 at 14:34 -0800, Stephen Boyd wrote:
> > ---
> > drivers/clk/clk.c| 260 ++-
> > include/linux/clk-provider.h | 19 +++
> > 2 files changed, 217 insertions(+), 62 deletions(-)
>
> Sorry
On 15/03/19 00:16, Fenghua Yu wrote:
> Hi, Valo,
>
> On Thu, Mar 14, 2019 at 03:16:33PM +0200, Kalle Valo wrote:
>> Fenghua Yu writes:
>>
>>> From: Paolo Bonzini
>>>
>>> Bitmaps are defined on unsigned longs, so the usage of u32[2] in the
>>> wlcore driver is incorrect. As noted by Peter
In case dmaengine_prep_dma_cyclic fails, the fix returns a proper
error code to avoid NULL pointer dereference.
Signed-off-by: Kangjie Lu
Fixes: 34df42f59a60 ("serial: at91: add rx dma support")
---
V2: simplified the patch as suggested by
Richard Genoud
---
drivers/tty/serial/atmel_serial.c
Adds a new sysfs node under the cros_ec device which contains the uptime
of the EC in milliseconds since boot.
Signed-off-by: Tim Wawrzynczak
---
drivers/platform/chrome/cros_ec_sysfs.c | 34 +
include/linux/mfd/cros_ec_commands.h| 15 +++
2 files changed, 49
Tim Wawrzynczak (1):
platform/chrome: mfd/cros_ec_sysfs: Add sysfs entry to retrieve EC
uptime.
drivers/platform/chrome/cros_ec_sysfs.c | 34 +
include/linux/mfd/cros_ec_commands.h| 15 +++
2 files changed, 49 insertions(+)
--
2.20.1
The group can now be handled independently from the CRTC tracking its
own state.
Introduce an rcar_du_group_atomic_check() call which will iterate the
CRTCs to determine the per-state use-count of the group.
This use count then allows us to determine if the group should be
configured or disabled
Provide helpers to manage the power state, and initial configuration of
the CRTC.
rcar_du_crtc_get() and rcar_du_crtc_get() are no longer used, and are
removed, simplifying the implementation and removing the initialized
flag which was needed to track the state of the CRTC.
Signed-off-by: Kieran
Refactoring of the group control code will soon require more iteration
over the available groups. Simplify this process by introducing a group
iteration helper.
Signed-off-by: Kieran Bingham
---
v2:
- no change
drivers/gpu/drm/rcar-du/rcar_du_drv.h | 5 +
On 15-03-19, 03:49, Katsuhiro Suzuki wrote:
> This patch adds debugfs interface to show the relationship between
> DMA threads (hardware resource for transferring data) and DMA
> channel ID of DMA slave.
>
> Typically, PL330 has many slaves than number of DMA threads.
> So sometimes PL330 cannot
The rcar_du_crtc functions have a heavy reliance on the rcar_du_group
structure, in many cases just to access the DU device context.
To better separate the groups out of the CRTC handling code, give the
rcar_du_crtc its own pointer to the device and remove the indirection
through the group
On Fri, 15 Mar 2019 at 13:57:05 +0100, Geert Uytterhoeven wrote:
> On Fri, Mar 15, 2019 at 11:23 AM George Spelvin wrote:
>> On Fri, 15 Mar 2019 at 09:20:58 +0100, Geert Uytterhoeven wrote:
>>> On Fri, Mar 15, 2019 at 5:33 AM George Spelvin wrote:
One question I should ask everyone: should
Hi Mike,
On 3/15/19 5:17 PM, Michael Turquette wrote:
Hi Alex,
Some nitpick review comments below.
On Wed, Mar 13, 2019 at 12:33 PM Alexandre Bailon wrote:
This series implements busfreq, a framework used in MXP's
s/MXP/NXP/
tree to scale the interconnect and dram frequencies.
In the
On 3/15/19 8:29 AM, Michel Dänzer wrote:
> On 2019-03-15 11:25 a.m., Boris Brezillon wrote:
>> On Fri, 15 Mar 2019 11:11:36 +0100
>> Michel Dänzer wrote:
>>
>>> On 2019-03-14 6:51 p.m., Helen Koike wrote:
On 3/14/19 6:15 AM, Michel Dänzer wrote:
> On 2019-03-13 7:08 p.m., Helen
On Thu, 14 Mar 2019 21:36:43 -0700
Daniel Colascione wrote:
> On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> >
> > On Thu, 14 Mar 2019 13:49:11 -0700
> > Sultan Alsawaf wrote:
> >
> > > Perhaps I'm missing something, but if you want to know when a process has
> > > died
> > > after
Since the enabling and disabling of IRQs within preempt_schedule_irq()
is contained in a need_resched() loop, we don't need the outer arch
code loop.
Note that commit a18815abcdfd ("Use preempt_schedule_irq.") initially
removed the existing loop, but missed the final branch to restore_all.
Commit
On Fri, Mar 15, 2019 at 09:30:42AM -0400, Phil Auld wrote:
> On Fri, Mar 15, 2019 at 11:11:50AM +0100 Peter Zijlstra wrote:
> > Computers _suck_ at /100. And since you're free to pick the constant,
> > pick a power of two, computers love those.
> >
>
> Fair enough, I was thinking percents. And
Quoting Lina Iyer (2019-03-13 14:18:41)
> ---
> Changes in v4:
> - Remove irq_set_wake() on summary IRQ interrupt
> Changes in v3:
> - Use of_irq_domain_map() and pass PDC pin to parent irqdomain
> Changes in v2:
> - Call parent mask when masking GPIO interrupt
> Changes in
This reverts commit caf6fe91ddf62a96401e21e9b7a07227440f4185.
The commit was fine but is no longer needed as of commit 3a2429e1faf4
("kbuild: change if_changed_rule for multi-line recipe"). Let's go
back to using ";" to be consistent.
For some discussion, see:
Hi Rob,
On 3/13/19 2:20 PM, Rob Herring wrote:
On Tue, Mar 12, 2019 at 2:28 PM Thor Thayer wrote:
Hi Rob,
On 3/12/19 11:04 AM, Rob Herring wrote:
On Wed, Feb 27, 2019 at 11:27:22AM -0600, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
Add peripheral bindings for Stratix10 EDAC to
On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote:
>
> On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote:
> > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote:
> > >
> > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote:
> > > > On Thu, Mar 14, 2019 at 12:01 AM Mike
On Fri, Mar 15, 2019 at 04:59:33PM +0100 Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 09:51:25AM -0400, Phil Auld wrote:
> > On Fri, Mar 15, 2019 at 11:33:57AM +0100 Peter Zijlstra wrote:
> > > On Fri, Mar 15, 2019 at 11:11:50AM +0100, Peter Zijlstra wrote:
> > > > diff --git
On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote:
>
> On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote:
> > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote:
> > >
> > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote:
> > > > On Thu, Mar 14, 2019 at 12:01 AM Mike
Hi Alex,
Some nitpick review comments below.
On Wed, Mar 13, 2019 at 12:33 PM Alexandre Bailon wrote:
>
> This series implements busfreq, a framework used in MXP's
s/MXP/NXP/
> tree to scale the interconnect and dram frequencies.
> In the vendor tree, device's driver request for a
>
On Fri, Mar 15, 2019 at 05:03:47PM +0100 Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 11:30:42AM -0400, Phil Auld wrote:
>
> > In my defense here, all the fair.c imbalance pct code also uses 100 :)
>
> Yes, I know, I hate on that too ;-) Just never got around to fixing
> that.
>
>
> > with
Hi.
On Sat, Mar 16, 2019 at 12:19 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Mar 15, 2019 at 7:11 AM Masahiro Yamada
> wrote:
> >
> > On Fri, Mar 15, 2019 at 2:59 AM Douglas Anderson
> > wrote:
> > >
> > > If the call to strip returns an error code then it makes sense for the
> > > build to
On Fri, Mar 15, 2019 at 8:56 AM Suren Baghdasaryan wrote:
>
> On Thu, Mar 14, 2019 at 9:37 PM Daniel Colascione wrote:
> >
> > On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> > >
> > > On Thu, 14 Mar 2019 13:49:11 -0700
> > > Sultan Alsawaf wrote:
> > >
> > > > Perhaps I'm missing
Hi,
On Fri, Mar 15, 2019 at 9:09 AM Masahiro Yamada
wrote:
>
> Hi,
>
> On Sat, Mar 16, 2019 at 12:41 AM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Fri, Mar 15, 2019 at 8:37 AM Masahiro Yamada
> > wrote:
> > >
> > > On Sat, Mar 16, 2019 at 12:27 AM Masahiro Yamada
> > > wrote:
> > > >
> > > >
Add a new VFIO_PCI_DMA_FAULT_IRQ_INDEX index. This allows to
set/unset an eventfd that will be triggered when DMA translation
faults are detected at physical level when the nested mode is used.
Signed-off-by: Eric Auger
---
drivers/vfio/pci/vfio_pci.c | 3 +++
From: Jacob Pan
Traditionally, device specific faults are detected and handled within
their own device drivers. When IOMMU is enabled, faults such as DMA
related transactions are detected by IOMMU. There is no generic
reporting mechanism to report faults back to the in-kernel device
driver or
On Thu, Mar 14, 2019 at 9:16 AM Andrea Arcangeli wrote:
> So this will be for who's paranoid and prefers to disable userfaultfd
> as a whole as an hardening feature like the bpf sysctl allows: it will
> allow to block uffd syscall without having to rebuild the kernel with
> CONFIG_USERFAULTFD=n
This series allows a virtualizer to program the nested stage mode.
This is useful when both the host and the guest are exposed with
an SMMUv3 and a PCI device is assigned to the guest using VFIO.
In this mode, the physical IOMMU must be programmed to translate
the two stages: the one set up by
From: Jacob Pan
DMA faults can be detected by IOMMU at device level. Adding a pointer
to struct device allows IOMMU subsystem to report relevant faults
back to the device driver for further handling.
For direct assigned device (or user space drivers), guest OS holds
responsibility to handle and
From: Jacob Pan
Device faults detected by IOMMU can be reported outside the IOMMU
subsystem for further processing. This patch introduces
a generic device fault data structure.
The fault can be either an unrecoverable fault or a page request,
also referred to as a recoverable fault.
We only
Hi,
On Sat, Mar 16, 2019 at 12:41 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Mar 15, 2019 at 8:37 AM Masahiro Yamada
> wrote:
> >
> > On Sat, Mar 16, 2019 at 12:27 AM Masahiro Yamada
> > wrote:
> > >
> > > On Fri, Mar 15, 2019 at 8:42 AM Douglas Anderson
> > > wrote:
> > > >
> > > > During
Hi Linus,
Here's a few more cleanups that trickled in for the merge window. It's
all fixes for static checker complaints and slowly unwinding typedef
usage. The four patches here have gone through a few days worth of
fstest runs with no new problems observed; and they merge cleanly with
master
On Fri, Mar 15, 2019 at 07:53:27AM +0100, Michal Hocko wrote:
> On Thu 14-03-19 23:45:48, Alexey Dobriyan wrote:
> > Use %lx, save a cast.
> >
> > "addr" is userspace address so using (and mangling) pointer was never
> > necessary.
>
> There shouldn't be any mangling AFAIU. Documentation for
On Fri, Mar 15, 2019 at 07:02:23AM +0900, Tetsuo Handa wrote:
> On 2019/03/15 5:42, Alexey Dobriyan wrote:
> > PTR_ERR((void *)map_addr) == -EEXIST
> >
> > is a very complicated way of doing the obvious.
>
> Michal suggested me to explicitly use PTR_ERR()
without any explanation why...
I
On Fri, Mar 15, 2019 at 11:30:42AM -0400, Phil Auld wrote:
> In my defense here, all the fair.c imbalance pct code also uses 100 :)
Yes, I know, I hate on that too ;-) Just never got around to fixing
that.
> with the below:
>
> [ 117.235804] cfs_period_timer[cpu2]: period too short, scaling
On Fri, Mar 15, 2019 at 09:51:25AM -0400, Phil Auld wrote:
> On Fri, Mar 15, 2019 at 11:33:57AM +0100 Peter Zijlstra wrote:
> > On Fri, Mar 15, 2019 at 11:11:50AM +0100, Peter Zijlstra wrote:
> > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > > index ea74d43924b2..b71557be6b42 100644
On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote:
> On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote:
> >
> > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote:
> > > On Thu, Mar 14, 2019 at 12:01 AM Mike Rapoport wrote:
> > > >
> > > > On Tue, Mar 12, 2019 at 10:08:22PM
On Fri, Mar 15, 2019 at 10:43:42AM +0100, Borislav Petkov wrote:
> On Thu, Mar 14, 2019 at 02:59:52PM -0700, Luck, Tony wrote:
> > I made a patch based on option #3. Rough steps were:
> >
> > $ cat skx_common.c >> skx_common.h
>
> That doesn't look real clean to me. So we have fsl_ddr_edac.c
On 3/14/19 4:26 PM, Masami Hiramatsu wrote:
> Hi Frank and Steve,
>
> Thank you for pointing it out :)
>
> On Thu, 14 Mar 2019 18:19:08 -0400
> Steven Rostedt wrote:
>
>> On Thu, 14 Mar 2019 14:05:02 -0700
>> Frank Rowand wrote:
>>
>>> Hi Steve,
>>>
>>> Ping.
>>
>> Thanks, this got buried.
>>
We track the smallest size that failed for a 32 bit allocation. The
Size decreases only and if we actually walked the tree and noticed an
allocation failure. Current code is broken and wrongly updates the
size value even if we did not try an allocation. This leads to
increased size values and we
On Thu, Mar 14, 2019 at 9:37 PM Daniel Colascione wrote:
>
> On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> >
> > On Thu, 14 Mar 2019 13:49:11 -0700
> > Sultan Alsawaf wrote:
> >
> > > Perhaps I'm missing something, but if you want to know when a process has
> > > died
> > > after
Ping?
On Wed, Feb 20, 2019 at 11:36:59AM +0300, Yury Norov wrote:
> bitmap_parselist has been evolved from a pretty simple idea for long and
> now lacks for refactoring. It is not structured, has nested loops and a
> set of opaque-named variables. All this leads to extremely hard
> understanding
On 3/15/19 10:11 AM, Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 02:44:32PM +, Lendacky, Thomas wrote:
>
@@ -689,6 +731,7 @@ static __initconst const struct x86_pmu amd_pmu = {
.amd_nb_constraints = 1,
.wait_on_overflow =
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f261c4e529dac5608a604d3dd3ae1cd2adf23c89
commit: 0e11faa48b07a063289d65363015a3d51ca4c337 PCI: dwc: Make use of BIT() in
constant definitions
date: 2 weeks ago
reproduce:
# apt-get install sparse
On Tue, Mar 12, 2019 at 09:21:26PM +0100, Mathieu Malaterre wrote:
> Silence warnings (triggered at W=1) by adding relevant __printf attributes.
>
> kernel/workqueue.c:4249:2: warning: function 'alloc_workqueue' might be a
> candidate for 'gnu_printf' format attribute
Hi,
On Fri, Mar 15, 2019 at 8:37 AM Masahiro Yamada
wrote:
>
> On Sat, Mar 16, 2019 at 12:27 AM Masahiro Yamada
> wrote:
> >
> > On Fri, Mar 15, 2019 at 8:42 AM Douglas Anderson
> > wrote:
> > >
> > > During a simple no-op (nothing changed) build I saw 39 invocations of
> > > the C compiler
I noticed that apic test from kvm-unit-tests always hangs on my EPYC 7401P,
the hanging test nmi-after-sti is trying to deliver 3 NMIs and tracing
shows that we're sometimes able to deliver a few but never all.
When we're trying to inject an NMI we may fail to do so immediately for
various
On Sat, Mar 16, 2019 at 12:27 AM Masahiro Yamada
wrote:
>
> On Fri, Mar 15, 2019 at 8:42 AM Douglas Anderson
> wrote:
> >
> > During a simple no-op (nothing changed) build I saw 39 invocations of
> > the C compiler with the argument "-print-file-name=include". We don't
> > need to call the C
Hi Rafael,
On Thursday, March 14, 2019 11:08:03 PM CET Rafael J. Wysocki wrote:
> On Thu, Mar 14, 2019 at 3:42 PM Thomas Renninger wrote:
> > This is a revert of mainline git commits:
> > commit b51ef52df71cb28e9d90cd1d48b79bf19f0bab06
> > commit 17edf2d79f1ea6dfdb4c444801d928953b9f98d6
> >
On Fri, Mar 15, 2019 at 11:11:50AM +0100 Peter Zijlstra wrote:
> On Wed, Mar 13, 2019 at 11:08:26AM -0400, Phil Auld wrote:
...
> Computers _suck_ at /100. And since you're free to pick the constant,
> pick a power of two, computers love those.
>
> > +
> > + if (new_period >
On Fri, Mar 15, 2019 at 8:42 AM Douglas Anderson wrote:
>
> During a simple no-op (nothing changed) build I saw 39 invocations of
> the C compiler with the argument "-print-file-name=include". We don't
> need to call the C compiler 39 times for this--one time will suffice.
>
> Let's change
Hi,
On Fri, Mar 15, 2019 at 7:11 AM Masahiro Yamada
wrote:
>
> On Fri, Mar 15, 2019 at 2:59 AM Douglas Anderson
> wrote:
> >
> > If the call to strip returns an error code then it makes sense for the
> > build to fail. Currently we'll just chug along and ship unstripped
> > modules.
> >
> >
On 15.03.2019 16:43, Alexey Budankov wrote:
> On 15.03.2019 15:28, Jiri Olsa wrote:
>> On Thu, Mar 14, 2019 at 02:26:23PM +0300, Alexey Budankov wrote:
>>>
>
>>> The patch set implements runtime trace compression (-z option) in
>>> record mode and trace auto decompression in report and inject
On Wed, Feb 27, 2019 at 03:21:56PM -0500, Junhan Zhou wrote:
> Add ECC support for Mellanox BlueField SoC DDR controller.
> This requires SMC to the running Arm Trusted Firmware to report
> what is the current memory configuration.
>
> Signed-off-by: Junhan Zhou
> ---
> drivers/edac/Kconfig
On Fri, Mar 15, 2019 at 12:22:36PM +, Okamoto, Takayuki wrote:
> I resend the patch due to whitespace munging.
>
> > -Original Message-
> > From: James Morse
> > Sent: Wednesday, February 27, 2019 3:44 AM
> > To: james.mo...@arm.com; linux-arm-ker...@lists.infradead.org
> > Cc:
On Fri, Mar 15, 2019 at 02:44:32PM +, Lendacky, Thomas wrote:
> >> @@ -689,6 +731,7 @@ static __initconst const struct x86_pmu amd_pmu = {
> >>
> >>.amd_nb_constraints = 1,
> >>.wait_on_overflow = amd_pmu_wait_on_overflow,
> >> + .mitigate_nmi_latency =
Clock name was wrong, vbat & vddio supplies were missing.
Signed-off-by: Alexis Ballier
Cc: devicet...@vger.kernel.org
Cc: Heiko Stuebner
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-rockc...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
Also rename its regulator to match the schematic names.
Signed-off-by: Alexis Ballier
Cc: devicet...@vger.kernel.org
Cc: Heiko Stuebner
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-rockc...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
Despite this not being mentioned in the binding documentation, this
generates a log at boot about it being missing.
Signed-off-by: Alexis Ballier
Cc: devicet...@vger.kernel.org
Cc: Heiko Stuebner
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-rockc...@lists.infradead.org
Cc:
This patch series is based on the rockchip/v5.2-armsoc/dts64 branch and
fixes a few mistakes in the rk3399-orangepi.dts I sent a couple weeks ago.
Alexis Ballier (3):
arm64: dts: rockchip: rk3399-orangepi: Fix clock names and add missing
supplies for bluetooth
arm64: dts: rockchip:
On Fri, Mar 15, 2019 at 11:35:04AM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> > +static void display_attr(struct perf_event_attr *attr)
> > +{
> > + if (verbose >= 2) {
> > + fprintf(stderr, "%.60s\n", graph_dotted_line);
> > + fprintf(stderr, "perf_event_attr:\n");
> >
On 3/14/19 9:38 AM, Wolfgang Grandegger wrote:
> Hello,
>
> Am 14.03.19 um 15:04 schrieb Dan Murphy:
>> Hello
>>
>> On 3/14/19 2:26 AM, Wolfgang Grandegger wrote:
>>> Hello Dan,
>>>
>>> we are close...
>>>
>>> Am 13.03.19 um 17:26 schrieb Dan Murphy:
Create a m_can platform framework that
On Fri, Mar 15, 2019 at 02:24:30PM +, David Howells wrote:
> Al Viro wrote:
>
> > - if (fc->user_ns)
> > - put_user_ns(fc->user_ns);
> > - fc->user_ns = get_user_ns(netns->user_ns);
> > + if (netns) {
> > + if (fc->user_ns)
> > +
On 3/15/19 7:03 AM, Peter Zijlstra wrote:
> On Mon, Mar 11, 2019 at 04:48:51PM +, Lendacky, Thomas wrote:
>> @@ -467,6 +470,45 @@ static void amd_pmu_wait_on_overflow(int idx, u64
>> config)
>> }
>> }
>>
>> +/*
>> + * Because of NMI latency, if multiple PMC counters are active we
Hi,
Le ven. 15 mars 2019 à 9:40, Miquel Raynal
a écrit :
Hi Paul,
Paul Cercueil wrote on Wed, 13 Mar 2019
23:22:56
+0100:
Use the 'ecc-engine' standard property instead of the custom
'ingenic,bch-controller' custom property, which is now deprecated.
Signed-off-by: Paul Cercueil
On (03/15/19 12:31), David Laight wrote:
> From: Sergey Senozhatsky
> >
> > cpu_to_le32() is capable enough to detect __builtin_constant_p()
> > and to use an appropriate compile time ___constant_swahb32()
> > function.
> >
> > So we can use cpu_to_le32() instead of __constant_cpu_to_le32().
>
On Fri, Mar 15, 2019 at 01:47:33PM +0100, Michal Hocko wrote:
> diff --git a/mm/debug.c b/mm/debug.c
> index 1611cf00a137..499c26d5ebe5 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -78,6 +78,9 @@ void __dump_page(struct page *page, const char *reason)
> else if (PageKsm(page))
>
On 3/15/19 12:30 AM, Dominique Martinet wrote:
> Jens, Steven,
>
> Jens Axboe wrote on Thu, Mar 14, 2019:
>> On 3/14/19 7:37 PM, Steven Rostedt wrote:
>>> I noticed this old patch in my inbox. It looks like a legit cleanup.
>>> Want to take it?
>>
>> Indeed, I've applied it. Thanks!
>
> Thanks.
Em Fri, Mar 15, 2019 at 01:15:46PM +0100, Jiri Olsa escreveu:
> On Thu, Mar 14, 2019 at 08:49:11AM -0700, Andi Kleen wrote:
> > > > Still seems like a hack. Even though I don't know of a case that
> > > > would break now. But it would be better to have the precise probing
> > > > in the open retry
On Fri, Mar 15, 2019 at 02:24:30PM +, David Howells wrote:
> Al Viro wrote:
>
> > - if (fc->user_ns)
> > - put_user_ns(fc->user_ns);
> > - fc->user_ns = get_user_ns(netns->user_ns);
> > + if (netns) {
> > + if (fc->user_ns)
> > +
Al Viro wrote:
> - if (fc->user_ns)
> - put_user_ns(fc->user_ns);
> - fc->user_ns = get_user_ns(netns->user_ns);
> + if (netns) {
> + if (fc->user_ns)
> + put_user_ns(fc->user_ns);
> + fc->user_ns = get_user_ns(netns->user_ns);
On Fri, Mar 15, 2019 at 09:56:07PM +0800, maowenan wrote:
> ping...
For what? It's the middle of the merge window at the moment, you should
have gotten an email from my scripts saying what happens at this point
in time, right?
greg k-h
On 03/15/2019 05:25 AM, Peter Zijlstra wrote:
> On Thu, Mar 14, 2019 at 04:42:12PM +0800, Zhenzhong Duan wrote:
>> This reverts commit f99fd22e4d4bc84880a8a3117311bbf0e3a6a9dc.
>>
>> It's unnecessory after commit "acpi_pm: Fix bootup softlockup due to PMTMR
>> counter read contention", the simple
On Fri, Mar 15, 2019 at 2:59 AM Douglas Anderson wrote:
>
> If the call to strip returns an error code then it makes sense for the
> build to fail. Currently we'll just chug along and ship unstripped
> modules.
>
> Fixes: e2a666d52b48 ("kbuild: sign the modules at install time")
> Signed-off-by:
On 15/03/2019 14:26, Pierre Morel wrote:
On 15/03/2019 11:20, Cornelia Huck wrote:
On Wed, 13 Mar 2019 17:04:58 +0100
Pierre Morel wrote:
+/*
+ * handle_pqap: Handling pqap interception
+ * @vcpu: the vcpu having issue the pqap instruction
+ *
+ * We now support PQAP/AQIC instructions and we
On 3/15/19 5:50 AM, Peter Zijlstra wrote:
> On Mon, Mar 11, 2019 at 04:48:44PM +, Lendacky, Thomas wrote:
>> On AMD processors, the detection of an overflowed counter in the NMI
>> handler relies on the current value of the counter. So, for example, to
>> check for overflow on a 48 bit
On Fri, Mar 15, 2019 at 01:15:46PM +0100, Jiri Olsa wrote:
> On Thu, Mar 14, 2019 at 08:49:11AM -0700, Andi Kleen wrote:
> > > > Still seems like a hack. Even though I don't know of a case that
> > > > would break now. But it would be better to have the precise probing
> > > > in the open retry
Current nvmem framework allows user space to read all register space
populated by nvmem binary file, In case we don't want to expose value
of registers to userspace and only want kernel space to read cell
value from nvmem_cell_read_u32.
To protect the same, Add no-read-write property to prevent
Ted,
Am Freitag, 15. März 2019, 14:51:28 CET schrieb Theodore Ts'o:
> On Fri, Mar 15, 2019 at 08:48:10AM +0100, Richard Weinberger wrote:
> > Ted,
> >
> > Am Freitag, 15. März 2019, 00:07:02 CET schrieb Theodore Ts'o:
> > > Richard --- stepping back for a moment, in your use case, are you
> > >
On 2019-03-15 09:35:44 [-0400], Steven Rostedt wrote:
> On Fri, 15 Mar 2019 12:11:30 +0100
> Sebastian Andrzej Siewior wrote:
>
> > +static void rcu_cpu_kthread_park(unsigned int cpu)
> > +{
>
> Should we add one of the trace_rcu_.. trace events here?
If it is required and I'm told which one
ping...
On 2019/3/11 20:19, Dan Carpenter wrote:
> On Mon, Mar 11, 2019 at 05:39:59PM +0800, Mao Wenan wrote:
>> Add the missing uart_unregister_driver() and i2c_del_driver() before
>> return from sc16is7xx_init() in the error handling case.
>>
>> Signed-off-by: Mao Wenan
>> Reviewed-by:
On Fri, Mar 15, 2019 at 4:36 AM Maxime Ripard wrote:
>
> We've never had a board compatibles documentation for the Allwinner boards
> so far.
>
> Let's create a json-schema for them.
>
> Signed-off-by: Maxime Ripard
> ---
> .../devicetree/bindings/arm/sunxi.yaml| 792 ++
On Fri, Mar 15, 2019 at 08:48:10AM +0100, Richard Weinberger wrote:
> Ted,
>
> Am Freitag, 15. März 2019, 00:07:02 CET schrieb Theodore Ts'o:
> > Richard --- stepping back for a moment, in your use case, are you
> > assuming that the encryption key is always going to be present while
> > the
On Fri, Mar 15, 2019 at 11:33:57AM +0100 Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 11:11:50AM +0100, Peter Zijlstra wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index ea74d43924b2..b71557be6b42 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@
Enable USB on the Nexbox A1 STB
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts
b/arch/arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts
index
On Fri, Mar 15, 2019 at 04:44:52PM +0900, Byungchul Park wrote:
> On 03/15/2019 04:31 PM, Byungchul Park wrote:
> > On Mon, Mar 11, 2019 at 09:39:39AM -0400, Joel Fernandes wrote:
> > > On Wed, Aug 29, 2018 at 03:20:34PM -0700, Paul E. McKenney wrote:
> > > > RCU's dyntick-idle code is written to
On 15/03/2019 14:41, Cornelia Huck wrote:
On Fri, 15 Mar 2019 14:26:34 +0100
Pierre Morel wrote:
Conclusion: we must handle this in userland, it will have the benefit
to keep old behavior when there is no callback.
OLD QEMU will not see change as they will not set aqic facility
NEW QEMU will
On Fri, Mar 15, 2019 at 02:32:55PM +0100, Paul Kocialkowski wrote:
> Hi,
>
> On Fri, 2019-03-15 at 18:38 +0530, Jagan Teki wrote:
> > Some display panels would come up with a non-DSI output which
> > can have an option to connect DSI interface by means of bridge
> > convertor.
> >
> > This DSI
On 15.03.2019 15:28, Jiri Olsa wrote:
> On Thu, Mar 14, 2019 at 02:26:23PM +0300, Alexey Budankov wrote:
>>
>> The patch set implements runtime trace compression (-z option) in
>> record mode and trace auto decompression in report and inject modes.
>> Streaming Zstd API [1] is used for
This patchset adds the secure monitor and efuse to the g12a SoC family.
These are sent together because the secure monitor is required for the
efuse driver to work properly. This is probably something the bindings
should show but it was not designed that way when the secure monitor was
introduced
Add the interface to the secure monitor on g12a
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
b/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
index
Add the g12a SoC efuse device
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
b/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
index 92ee8c895ba6..dcc821cf35bb
201 - 300 of 443 matches
Mail list logo
