From: "Steven Rostedt (VMware)"
When the function profiler is not configured, the "graph_time" option is
meaningless, as the function profiler is the only thing that makes use of
it. Do not expose it if the profiler is not configured.
Link: http://lkml.kernel.org/r/20181123061133.ga195...@google
From: Masami Hiramatsu
Use dyn_event framework for uprobe events. This shows
uprobe events on "dynamic_events" file.
User can also define new uprobe events via dynamic_events.
Link:
http://lkml.kernel.org/r/154140858481.17322.9091293846515154065.stgit@devbox
Reviewed-by: Tom Zanussi
Tested-by
From: Masami Hiramatsu
Add unified dynamic event framework for ftrace kprobes, uprobes
and synthetic events. Those dynamic events can be co-exist on
same file because those syntax doesn't overlap.
This introduces a framework part which provides a unified tracefs
interface and operations.
Link:
From: "Steven Rostedt (VMware)"
The trace_add/remove_event_call_nolock() functions were added to allow
the tace_add/remove_event_call() code be called when the event_mutex
lock was already taken. Now that all callers are done within the
event_mutex, there's no reason to have two different interfa
From: "Steven Rostedt (VMware)"
Functions in the set_graph_notrace no longer subtract FTRACE_NOTRACE_DEPTH
from curr_ret_stack, as that is now implemented via the trace_recursion
flags. Access to curr_ret_stack no longer needs to worry about checking for
this. curr_ret_stack is still initialized
Roman Penyaev wrote:
> Hi all,
>
> The goal of this patch is to reduce contention of ep_poll_callback() which
> can be called concurrently from different CPUs in case of high events
> rates and many fds per epoll. Problem can be very well reproduced by
> generating events (write to pipe or event
> I can't help you on that. I never tried to force errors by grounding the
> signals. You have read the driver. Do you see panic? The idea is to
> report the error and let upper layer to decide what to do. Sometimes
> limping forward is better than reset or panic. Again, it is not driver's
> respon
On Wed, Dec 5, 2018 at 3:20 PM Sean Christopherson
wrote:
>
> Intel Software Guard Extensions (SGX) SGX introduces a new CPL3-only
> enclave mode that runs as a sort of black box shared object that is
> hosted by an untrusted normal CPL3 process.
>
> Enclave transitions have semantics that are a l
On Wed, Dec 05, 2018 at 02:03:10PM -0800, Linus Torvalds wrote:
> On Wed, Dec 5, 2018 at 12:40 PM Andrea Arcangeli wrote:
> >
> > So ultimately we decided that the saner behavior that gives the least
> > risk of regression for the short term, until we can do something
> > better, was the one that
>> On Dec 5, 2018, at 7:04 AM, Josh Poimboeuf wrote:
>
>
>> Anyway, I have a new objection to Josh’s create_gap proposal: what on
>> Earth will kernel CET do to it? Maybe my longjmp-like hack is
>> actually better.
>
> Does CET even care about iret? I assumed it didn't. If it does, your
> propo
Hello,
My name is ms. Reem Al-Hashimi. The UAE minister of state for international
cooperation. I got your contact from an email database from your country. I
have a financial transaction i would like to discuss with you. Please reply to
reem2...@daum.net, for more details if you are interested
>From a081e783383adf1179c71bc37b4e199d087af643 Mon Sep 17 00:00:00 2001
From: Alek Du
Date: Fri, 30 Nov 2018 14:02:28 +0800
Subject: [PATCH] mmc: sdhci: fix the timeout check window for clock and reset
We observed some premature timeouts on a virtualization platform, the log
is like this:
case 1
On Mon, Dec 3, 2018 at 12:14 PM Luis Chamberlain wrote:
> Since this worked before I do agree that we need to keep it working now,
> and I can't think of an issue with returning 0 now. Since this is about
> semantics though I'd like a bit more review from at last one more
> person.
>
> Kees, Eric,
On Wed, Dec 05, 2018 at 04:23:42PM -0700, Logan Gunthorpe wrote:
>
>
> On 2018-12-05 4:20 p.m., Jerome Glisse wrote:
> > And my proposal is under /sys/bus and have symlink to all existing
> > device it agregate in there.
>
> That's so not the point. Use the existing buses don't invent some
> vir
On Wed, Dec 5, 2018 at 12:53 PM Christian Brauner wrote:
> On Wed, Dec 05, 2018 at 12:20:43PM -0600, Eric W. Biederman wrote:
> > Christian Brauner writes:
> > > [1]: https://lkml.org/lkml/2018/11/18/130
> > > [2]:
> > > https://lore.kernel.org/lkml/874lbtjvtd@oldenburg2.str.redhat.com/
>
On 2018-12-05 4:20 p.m., Jerome Glisse wrote:
> And my proposal is under /sys/bus and have symlink to all existing
> device it agregate in there.
That's so not the point. Use the existing buses don't invent some
virtual tree. I don't know how many times I have to say this or in how
many ways. I
On 12/5/18 4:15 PM, Anders Roxell wrote:
On Wed, 5 Dec 2018 at 22:50, Linus Walleij wrote:
Sorry for top-posting,
I don't understand the selftest environment very well so I do not know
if this is the right thing to do.
I can merge the patch through the GPIO tree but I need a nod from
someone
Call fixup_vdso_exception() to attempt to fixup exceptions in vDSO code
before generating a signal for userspace faults. This allows vDSO
functions to utilize exception fixup to report unhandled exceptions
directly to userspace for specific flows in lieu of generating a signal.
Suggested-by: And
The basic concept and implementation is very similar to the kernel's
exception fixup mechanism. The key differences are that the kernel
handler is hardcoded and the fixup entry addresses are relative to
the overall table as opposed to individual entries.
Hardcoding the kernel handler avoids the n
Call fixup_vdso_exception() in the SIGSEGV and SIGBUS paths to attempt
to fixup page faults in vDSO. This allows vDSO functions to utilize
exception fixup to report unhandled page faults directly to userspace
for specific flows in lieu of generating a signal.
In the SIGSEGV flow, make sure to cal
When dumping out binder transactions via a debug node,
the output is too verbose if a process has many nodes.
Change the output for transaction dumps to only display
nodes with pending async transactions.
Signed-off-by: Todd Kjos
---
v2: no change, just resubmitted as #3 of 3 patches instead of b
On Wed, Dec 05, 2018 at 04:09:29PM -0700, Logan Gunthorpe wrote:
>
>
> On 2018-12-05 3:58 p.m., Jerome Glisse wrote:
> > So just to be clear here is how i understand your position:
> > "Single coherent sysfs hierarchy to describe something is useless
> > let's git rm drivers/base/"
>
> I have n
Intel Software Guard Extensions (SGX) SGX introduces a new CPL3-only
enclave mode that runs as a sort of black box shared object that is
hosted by an untrusted normal CPL3 process.
Enclave transitions have semantics that are a lovely blend of SYCSALL,
SYSRET and VM-Exit. In a non-faulting scenari
First things first, this RFC is not intended to address whether or not
vDSO is the appropriate method for supporting SGX enclaves, but rather
its purpose is to hammer out the vDSO implementation *if* we decide it
is the best approach.
Though the code technically stands alone, the intent is to roll
On Wed, Dec 5, 2018 at 2:59 PM Stefan Agner wrote:
>
> On 05.12.2018 19:41, Nick Desaulniers wrote:
> > On Wed, Dec 5, 2018 at 10:40 AM Ard Biesheuvel
> > wrote:
> >>
> >> On Wed, 5 Dec 2018 at 19:36, Nathan Chancellor
> >> wrote:
> >> >
> >> > On Wed, Dec 05, 2018 at 09:09:56AM +0100, Ard Bies
Add __acquire()/__release() annnotations to fix warnings
in sparse context checking
There is one case where the warning was due to a lack of
a "default:" case in a switch statement where a lock was
being released in each of the cases, so the default
case was added.
Signed-off-by: Todd Kjos
---
v
Fix the incomplete kerneldoc header for struct binder_buffer.
Signed-off-by: Todd Kjos
---
v2: no code change. Removed needless "Change-Id:"
There is no dependancy on patch 1/3
drivers/android/binder_alloc.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --gi
On Wed, 5 Dec 2018 at 22:50, Linus Walleij wrote:
>
> Sorry for top-posting,
>
> I don't understand the selftest environment very well so I do not know
> if this is the right thing to do.
>
> I can merge the patch through the GPIO tree but I need a nod from
> someone wise, like Shuah Khan or Ander
I added some s390 and powerpc people.
On Tue, Dec 4, 2018 at 4:18 AM Igor Stoppa wrote:
>
> Implementation of write rare for statically allocated data, located in a
> specific memory section through the use of the __write_rare label.
>
> The basic functions are:
> - wr_memset(): write rare counte
Hi Lukasz/Rob,
On Tue, Oct 9, 2018 at 7:50 AM Lukasz Majewski wrote:
> +&dspi3 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_dspi3>;
> + bus-num = <3>;
> + status = "okay";
> + spi-slave;
> +
> + slave@0 {
> + compatible = "lwn,bk4";
On Wed, Dec 05, 2018 at 04:58:31PM +0800, Xunlei Pang wrote:
> Hi Roman,
>
> On 2018/12/4 AM 2:00, Roman Gushchin wrote:
> > On Mon, Dec 03, 2018 at 04:01:17PM +0800, Xunlei Pang wrote:
> >> When usage exceeds min, min usage should be min other than 0.
> >> Apply the same for low.
> >>
> >> Signed
On Mon, Dec 3, 2018 at 1:31 AM KarimAllah Ahmed wrote:
>
> Copy the VMCS12 directly from guest memory instead of the map->copy->unmap
> sequence. This also avoids using kvm_vcpu_gpa_to_page() and kmap() which
> assumes that there is a "struct page" for guest memory.
>
> Signed-off-by: KarimAllah A
On 2018-12-05 3:58 p.m., Jerome Glisse wrote:
> So just to be clear here is how i understand your position:
> "Single coherent sysfs hierarchy to describe something is useless
> let's git rm drivers/base/"
I have no idea what you're talking about. I'm saying the existing sysfs
hierarchy *shoul
Hi,
On Mon, Nov 12, 2018 at 06:52:35PM +0800, Baolin Wang wrote:
> Since the USB notifier context is atomic, we can not start or stop charging
> in atomic context. Thus this patch adds one work to help to charge or
> discharge.
>
> Signed-off-by: Baolin Wang
> ---
Thanks, patchset queued.
-- S
On 2018.12.03 03:48 Rafael J. Wysocki wrote:
>>> There is an additional issue where if idle state 0 is disabled (with the
>>> above suggested code patch),
>>> idle state usage seems to fall to deeper states than idle state 1.
>>> This is not the expected behaviour.
>>
>> No, it isn't.
>>
>>> Ke
ABS_RESERVED was added in d9ca1c990a7 and accidentally removed as part of
ffe0e7cf290f5c9 when the high-resolution scrolling code was removed.
Signed-off-by: Peter Hutterer
---
include/uapi/linux/input-event-codes.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/uapi/linux/
On 05.12.2018 19:41, Nick Desaulniers wrote:
> On Wed, Dec 5, 2018 at 10:40 AM Ard Biesheuvel
> wrote:
>>
>> On Wed, 5 Dec 2018 at 19:36, Nathan Chancellor
>> wrote:
>> >
>> > On Wed, Dec 05, 2018 at 09:09:56AM +0100, Ard Biesheuvel wrote:
>> > > (+ Arnd)
>> > >
>> > > On Wed, 5 Dec 2018 at 09:0
On Wed, Dec 05, 2018 at 12:10:10PM -0700, Logan Gunthorpe wrote:
>
>
> On 2018-12-05 11:55 a.m., Jerome Glisse wrote:
> > So now once next type of device shows up with the exact same thing
> > let say FPGA, we have to create a new subsystem for them too. Also
> > this make the userspace life much
Hi Guy,
On Wed, 5 Dec 2018 12:25:57 + "Guy Levi(SW)" wrote:
>
> >
> > Huh. So apparently every compiler that tested this patch (0-day, mine,
> > the submitters) optimized this call away because is_atomic_response()
> > always returns 0: meaning mlx5_get_atomic_laddr is never callable and
> >
On Wed, Dec 5, 2018 at 1:41 AM Sasha Levin wrote:
>
> From: Kees Cook
>
> [ Upstream commit 89d328f637b9904b6d4c9af73c8a608b8dd4d6f8 ]
>
> The actual number of bytes stored in a PRZ is smaller than the
> bytes requested by platform data, since there is a header on each
> PRZ. Additionally, if ECC
On 12/5/18 2:54 PM, Tracy Smith wrote:
>>> Question 4) If so, will a panic ever be called if there is a hardware
>>> uncorrectable memory failure?
>
>> No. It is up to upper layer of EDAC driver. Layerscape driver only reports
>> CEs and UEs.
>
> Just to be clear, the upper layer of the EDAC dri
On Wed, 21 Nov 2018 02:38:28 +0530, Sibi Sankar wrote:
> Add power-domain bindings for Q6V5 MSS on SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
>
> Add dt-binding corresponding to https://patchwork.kernel.org/patch/10586893/
> (remoteproc: q6v5: Add support to vote for rpmh power domains)
>
On Wed, 21 Nov 2018 02:32:07 +0530, Sibi Sankar wrote:
> Add optional shutdown-irq binding required for sysmon shutdown on
> SDM845/MSM8996/QCS404 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 5 +++--
> 1 file changed, 3 insertions(+),
>> Question 4) If so, will a panic ever be called if there is a hardware
>> uncorrectable memory failure?
>No. It is up to upper layer of EDAC driver. Layerscape driver only reports CEs
>and UEs.
Just to be clear, the upper layer of the EDAC driver will or will not
panic when a UE is detected on
On Wed, Dec 5, 2018 at 11:32 PM Sven Van Asbroeck wrote:
> On Wed, Dec 5, 2018 at 2:17 PM Greg KH wrote:
> >
> > Great, then call it a 'fieldbus' class, not "fieldbus_dev' class.
>
> Small nit:
>
> Hardware connected to a fieldbus comes in two distinct flavours:
> - clients (e.g. thermometer, rob
On Wed, Dec 5, 2018 at 2:02 PM Konrad Rzeszutek Wilk
wrote:
>
> On Wed, Dec 05, 2018 at 05:19:56PM -0200, Eduardo Habkost wrote:
> > Months ago, we have added code to allow direct access to MSR_IA32_SPEC_CTRL
> > to the guest, which makes STIBP available to guests. This was implemented
> > by com
This is a full revert of ac5b2c18911f ("mm: thp: relax __GFP_THISNODE for
MADV_HUGEPAGE mappings") and a partial revert of 89c83fb539f9 ("mm, thp:
consolidate THP gfp handling into alloc_hugepage_direct_gfpmask").
By not setting __GFP_THISNODE, applications can allocate remote hugepages
when the l
On Wed, Dec 05, 2018 at 09:37:21AM -0800, Bjorn Andersson wrote:
> + linux-arm-msm
>
> On Wed 21 Nov 18:32 PST 2018, Jonathan Marek wrote:
>
> > This fixes the case when CONFIG_QCOM_SCM is not enabled, and linux/errno.h
> > has not been included previously.
> >
> > Signed-off-by: Jonathan Marek
Hello,
My name is ms. Reem Al-Hashimi. The UAE minister of state for international
cooperation. I got your contact from an email database from your country. I
have a financial transaction i would like to discuss with you. Please reply to
reem2...@daum.net, for more details if you are interested
On Wed, Dec 5, 2018 at 4:38 PM Rob Herring wrote:
>
> On Tue, Nov 20, 2018 at 09:27:51AM +, Z.q. Hou wrote:
> > From: Hou Zhiqiang
> >
> > Add PCIe Gen4 controller DT bindings of NXP Layerscape SoCs.
> >
> > Signed-off-by: Hou Zhiqiang
> > ---
> > V2:
> > - Change to use the layerscape-pci.
Hi,
On Wed, Nov 07, 2018 at 06:23:40PM +0100, Alexandre Belloni wrote:
> On 07/11/2018 14:54:17+, claudiu.bez...@microchip.com wrote:
> > Hi Alexandre,
> >
> > On 06.11.2018 23:09, Alexandre Belloni wrote:
> > > Hi Claudiu,
> > >
> > > On 05/11/2018 11:14:26+, claudiu.bez...@microchip.co
On Tue, Nov 20, 2018 at 09:27:51AM +, Z.q. Hou wrote:
> From: Hou Zhiqiang
>
> Add PCIe Gen4 controller DT bindings of NXP Layerscape SoCs.
>
> Signed-off-by: Hou Zhiqiang
> ---
> V2:
> - Change to use the layerscape-pci.txt for PCIe Gen4 controller
>dt-bindings
Sorry someone suggeste
Hi,
On Mon, Nov 05, 2018 at 11:14:28AM +, claudiu.bez...@microchip.com wrote:
> Check at91_shdwc before continuing with probe since we want only one instance
> of
> this driver. Inspired from commit 9f1e44774be5 ("power: reset: at91-poweroff:
> do not procede if at91_shdwc is allocated").
>
Hi,
On Mon, Nov 05, 2018 at 11:14:31AM +, claudiu.bez...@microchip.com wrote:
> Remove at91_ramc_of_match[] since it is not used anywhere in this code.
>
> Signed-off-by: Claudiu Beznea
> ---
Thanks, queued.
-- Sebastian
> drivers/power/reset/at91-poweroff.c | 5 -
> 1 file changed,
Hi,
On Mon, Nov 05, 2018 at 11:14:23AM +, claudiu.bez...@microchip.com wrote:
> Use only one poweroff function and adapt it to work for both scenarios
> (with LPDDR or not). The assignement of pm_power_off was moved at the
> end of probe after all initializations are OK. This patch adapt the i
Gooday To You,
Please i need your kind Assistance. I will be very glad if you can
assist me to receive this sum of ( $22. Million US dollars.) into your
bank account for the benefit of our both families, reply me if you are
ready to receive this fund.
Gooday To You,
Please i need your kind Assistance. I will be very glad if you can
assist me to receive this sum of ( $22. Million US dollars.) into your
bank account for the benefit of our both families, reply me if you are
ready to receive this fund.
Gooday To You,
Please i need your kind Assistance. I will be very glad if you can
assist me to receive this sum of ( $22. Million US dollars.) into your
bank account for the benefit of our both families, reply me if you are
ready to receive this fund.
Gooday To You,
Please i need your kind Assistance. I will be very glad if you can
assist me to receive this sum of ( $22. Million US dollars.) into your
bank account for the benefit of our both families, reply me if you are
ready to receive this fund.
Thanks :)
On Wed, Dec 5, 2018 at 2:17 PM Greg KH wrote:
>
> Great, then call it a 'fieldbus' class, not "fieldbus_dev' class.
Small nit:
Hardware connected to a fieldbus comes in two distinct flavours:
- clients (e.g. thermometer, robotic arm) called "fieldbus devices"
- servers (e.g. a PLC) ca
Hi Mika,
On Wed, 5 Dec 2018 13:37:36 +0200 Mika Westerberg
wrote:
>
> I maintain the Thunderbolt tree that gets merged to mainline via Greg's
> char-misc tree. I would like to get the tree included in linux-next to
> get wider coverage before it hits Greg's tree.
>
> Can you please include bran
cvmx-smix-defs.h is not needed by this driver.
Signed-off-by: Aaro Koskinen
---
drivers/staging/octeon/ethernet-mdio.c | 1 -
drivers/staging/octeon/ethernet.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/staging/octeon/ethernet-mdio.c
b/drivers/staging/octeon/ethernet-mdio
On Tue, Dec 04, 2018 at 03:04:23PM -0800, Paul E. McKenney wrote:
> On Tue, Dec 04, 2018 at 02:24:13PM -0800, Josh Triplett wrote:
> > On Tue, Dec 04, 2018 at 02:09:42PM -0800, tip-bot for Paul E. McKenney
> > wrote:
> > > --- a/tools/testing/selftests/rcutorture/bin/mkinitrd.sh
> > > +++ b/tools/
On Fri, Nov 30, 2018 at 02:58:11PM -0500, Josef Bacik wrote:
> Currently we only drop the mmap_sem if there is contention on the page
> lock. The idea is that we issue readahead and then go to lock the page
> while it is under IO and we want to not hold the mmap_sem during the IO.
>
> The problem
On Wed, Dec 05, 2018 at 09:15:28PM +0100, Michal Hocko wrote:
> If the __GFP_THISNODE should be really used then it should be applied to
> all other types of pages. Not only THP. And as such done in a separate
> patch. Not a part of the revert. The cleanup was meant to unify THP
> allocations and t
On Wed, Dec 05, 2018 at 08:29:36PM +, Jolly Shah wrote:
> Hi Rob,
>
> Thanks for the review. Please find my responses inline.
You need to fix your mail client to wrap lines.
> Thanks,
> Jolly Shah
>
> > -Original Message-
> > From: Rob Herring [mailto:r...@kernel.org]
> > Sent: Tue
Em Wed, Dec 05, 2018 at 01:28:38PM +0100, Jiri Olsa escreveu:
> On Mon, Dec 03, 2018 at 04:18:48PM -0800, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > When looking at PT or brstackinsn traces with perf script
> > it can be very useful to see the source code. This adds a simple
> > facility to p
On Wed, 5 Dec 2018 16:01:16 +0100
Johan Hovold wrote:
> On Sun, Nov 18, 2018 at 10:57:58PM +0100, Andreas Kemnade wrote:
> > Some Wi2Wi devices do not have a wakeup output, so device state can
> > only be indirectly detected by looking whether there is communitcation
> > over the serial lines.
>
Hi Ben,
On Wed, Dec 5, 2018 at 2:36 PM Ben Dooks wrote:
>
> On 02/12/2018 22:08, Martin Blumenstingl wrote:
> > Add support for the RTC block on the 32-bit Amlogic Meson6, Meson8,
> > Meson8b and Meson8m2 SoCs.
> >
> > The RTC is split in to two parts, which are both managed by this driver:
> > -
On 05 December 2018 19:51, Rob Herring wrote:
> Convert string compares of DT node names to use of_node_name_eq helper
> instead. This removes direct access to the node name pointer.
>
> For instances using of_node_cmp, this has the side effect of now using case
> sensitive comparisons. This shou
Hallo,
Ich habe ein Geschäft, das ich gerne besprechen möchte, es geht um einen
Erbanspruch. Ich bin Alan Austin und arbeite bei der Credit Suisse Bank
London. Ich habe Ihren Kontakt während meiner privaten Suche gesehen und
bin der festen Überzeugung, dass Sie sehr ehrlich, engagiert und in d
Adds support to Raspberry Pi's 7" touchscreen device. Instead of using
a conventional bus all information is copied into a memory mapped area
by RPi's VC4 firmware.
Based on the driver found in RPi's downstream kernel repository.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/input/touchscre
Adds device tree documentation for Raspberry Pi's official 7"
touchscreen. The firmware mailbox interface allows the ARM core to
control the device.
Signed-off-by: Nicolas Saenz Julienne
---
.../touchscreen/raspberrypi,firmware-ts.txt | 25 +++
1 file changed, 25 insertions(+)
On Wed, 5 Dec 2018, Linus Torvalds wrote:
> > So ultimately we decided that the saner behavior that gives the least
> > risk of regression for the short term, until we can do something
> > better, was the one that is already applied upstream.
>
> You're ignoring the fact that people *did* report
On 12/5/18 2:00 PM, Tracy Smith wrote:
>> Single-bit errors are corrected by memory controller without involving
>> software.
>
> Sorry for being verbose, but I need to explain the reason for the
> questions below since I need to determine if a memory scrub is
> required on layerscape and why. T
This small series adds support for Raspberry pi's 7" touchscreen. Which
alongside with the backlight driver are the last devices needed to have
a functional touchscreen upstream.
With this setup the board's VC4 firmware takes care of communicating
with the touch chip and provides data though a sha
On Wed, 5 Dec 2018, Andrea Arcangeli wrote:
> > High thp utilization is not always better, especially when those hugepages
> > are accessed remotely and introduce the regressions that I've reported.
> > Seeking high thp utilization at all costs is not the goal if it causes
> > workloads to reg
On Wed, Dec 5, 2018 at 12:40 PM Andrea Arcangeli wrote:
>
> So ultimately we decided that the saner behavior that gives the least
> risk of regression for the short term, until we can do something
> better, was the one that is already applied upstream.
You're ignoring the fact that people *did* r
Hi,
On Tue, Nov 13, 2018 at 01:47:53PM +0100, Heiko Stuebner wrote:
> From: Heiko Stuebner
>
> The bq24196 is another variant of the bq24190 charger ic.
> Its register set is identical to the bq24192 and it even reuses
> the same part number (0x5).
>
> Signed-off-by: Heiko Stuebner
> ---
Than
On Wed, Dec 05, 2018 at 05:19:56PM -0200, Eduardo Habkost wrote:
> Months ago, we have added code to allow direct access to MSR_IA32_SPEC_CTRL
> to the guest, which makes STIBP available to guests. This was implemented
> by commits d28b387fb74d ("KVM/VMX: Allow direct access to
> MSR_IA32_SPEC_CTR
On Wed, Dec 05, 2018 at 01:16:01PM -0800, Todd Kjos wrote:
> 44d8047f1d87a ("binder: use standard functions to allocate fds")
> exposed a pre-existing issue in the binder driver.
>
> fdget() is used in ksys_ioctl() as a performance optimization.
> One of the rules associated with fdget() is that k
On Thu, Dec 06, 2018 at 01:25:55AM +0530, Shreeya Patel wrote:
> On Tue, 2018-12-04 at 18:49 -0700, Jeremy Fertic wrote:
> > This reverts commit 00426e99789357dbff7e719a092ce36a3ce49d94.
> >
> > i2c_smbus_read_byte() returns 0 when a byte with the value 0 is read
> > from
> > the device. This is a
On Wed, 5 Dec 2018, Andrea Arcangeli wrote:
> > thpscale Percentage Faults Huge
> >4.20.0-rc4 4.20.0-rc4
> >mmots-20181130 gfpthisnode-v1r1
> > Percentage huge-395.14 ( 0.00%)7.94 ( -91.65%)
> > Percent
>Single-bit errors are corrected by memory controller without involving
>software.
Sorry for being verbose, but I need to explain the reason for the
questions below since I need to determine if a memory scrub is
required on layerscape and why. There are multiple layers to the
problem of ECC.
Fi
On 12/5/2018 8:16 AM, Al Viro wrote:
> On Wed, Dec 05, 2018 at 10:37:56AM +0100, Ondrej Mosnacek wrote:
>
>> I just tested the Q28 branch rebased onto a recent Fedora rawhide
>> kernel (4.20.0-0.rc5.git0.1) and that code seems to be working fine.
Not so good with Smack.
# mount -t tmpfs -
On Tue, 4 Dec 2018 at 16:42, Peter Hutterer wrote:
>
> A full explanation of why and what is in the v1, v2 patch thread here:
> https://lkml.org/lkml/2018/11/22/625
>
> v3 adds a better commit messages, m560 REL_HWHEEL_HI_RES support and a patch
> moved in the ordering. This is a full patch sequen
Hi,
On Wed, Oct 31, 2018 at 08:11:46PM -0400, Brian Masney wrote:
> Add extcon support so that we can notify USB drivers of cable state
> changes. Based on work from Jonathan Marek. USB OTG was tested on a LG
> Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney
> ---
Thanks, queued.
-
Hi,
On Wed, Oct 31, 2018 at 08:11:44PM -0400, Brian Masney wrote:
> From: Jonathan Marek
>
> This patch adds support for the bq24192 variant to bq24190_charger.
>
> Signed-off-by: Jonathan Marek
> [masn...@onstation.org: Changed if statement to a switch based on
> feedback from Sebastian Reich
Hi,
On Wed, Oct 31, 2018 at 08:11:45PM -0400, Brian Masney wrote:
> From: Jonathan Marek
>
> This patch adds an of_match for the usb-otg-vbus regulator to
> bq24190_charger.
>
> Signed-off-by: Jonathan Marek
> Signed-off-by: Brian Masney
> ---
Thanks, queued.
-- Sebastian
> drivers/power/
On Fri, Nov 23, 2018 at 5:18 PM Nicholas Mc Guire wrote:
> devm_kasprintf() may return NULL on failure of internal allocation thus
> the assignment to .label is not safe if not checked. On error
> npcm7xx_gpio_of() returns negative values so -ENOMEM in the
> (unlikely) failure case of devm_kasp
On 12/05/2018 07:56 PM, Sergei Shtylyov wrote:
> On 12/04/2018 09:19 PM, Marek Vasut wrote:
>
>>> Document the bindings used by the Renesas R-Car Gen3 RPC SPI controller.
>>
>> RPC is SPI and HF controller, it is not a pure SPI controller.
>>
>> How does this deal with the HF part ? Keep in mind t
Hi,
On Wed, Oct 31, 2018 at 08:11:43PM -0400, Brian Masney wrote:
> Add support for the ti,bq24192 variant and a child node for the
> usb-otg-vbus regulator.
>
> Signed-off-by: Brian Masney
> ---
Thanks, queued.
-- Sebastian
> .../devicetree/bindings/power/supply/bq24190.txt | 9
Hi Peter,
On Tue, 4 Dec 2018 at 16:43, Peter Hutterer wrote:
> Changes to v2:
> - m560 now has REL_HWHEEL_HI_RES (untested, I don't have the device)
I just tested with my M560, and it now reports REL_HWHEEL_HI_RES correctly.
Verified-by: Harry Cutts
Thanks,
Harry Cutts
Chrome OS Touch/Input
On Fri, Nov 30, 2018 at 02:58:10PM -0500, Josef Bacik wrote:
> If we do not have a page at filemap_fault time we'll do this weird
> forced page_cache_read thing to populate the page, and then drop it
> again and loop around and find it. This makes for 2 ways we can read a
> page in filemap_fault,
Sorry for top-posting,
I don't understand the selftest environment very well so I do not know
if this is the right thing to do.
I can merge the patch through the GPIO tree but I need a nod from
someone wise, like Shuah Khan or Anders Roxell (Anders has been
using the GPIO selftests) that this is
From: "Steven Rostedt (VMware)"
Functions in the set_graph_notrace no longer subtract FTRACE_NOTRACE_DEPTH
from curr_ret_stack, as that is now implemented via the trace_recursion
flags. Access to curr_ret_stack no longer needs to worry about checking for
this. curr_ret_stack is still initialized
Hi,
On Tue, Nov 27, 2018 at 10:51:09AM -0600, Rob Herring wrote:
> On Sat, Nov 24, 2018 at 8:31 AM Yangtao Li wrote:
> >
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Signed-off-by: Yangtao Li
> > -
Hi,
On Fri, Nov 09, 2018 at 08:57:00PM +0100, Alexandre Belloni wrote:
> Switch the SI to boot mode so on a warm reboot, the SI is able to access
> the flash.
>
> Signed-off-by: Alexandre Belloni
> ---
Thanks, queued.
-- Sebastian
> drivers/power/reset/ocelot-reset.c | 12
> 1 f
Hi,
On Sun, Nov 11, 2018 at 10:45:38PM +0100, Heiko Stuebner wrote:
> From: Heiko Stuebner
>
> Similar to gpio-reset allow to specify active and inactive delays
> while keeping the 100ms defaults that were used previously all the time.
>
> The dt-properties are named the same as in gpio-reset b
On Wed, Dec 05, 2018 at 11:49:26AM -0800, David Rientjes wrote:
> High thp utilization is not always better, especially when those hugepages
> are accessed remotely and introduce the regressions that I've reported.
> Seeking high thp utilization at all costs is not the goal if it causes
> workl
201 - 300 of 1188 matches
Mail list logo
