On Sat, Apr 6, 2019 at 1:26 AM Paul Walmsley wrote:
>
> Running 'make dt_binding_check' fails for
> Documentation/devicetree/bindings/arm/cpus.yaml. This is due to tabs
> used for indentation:
You're the 3rd fix. :( We're waiting on arm-soc folks to apply it.
Rob
Running 'make dt_binding_check' fails for
Documentation/devicetree/bindings/arm/cpus.yaml. This is due to tabs
used for indentation:
$ dt-doc-validate Documentation/devicetree/bindings/arm/cpus.yaml
Documentation/devicetree/bindings/arm/cpus.yaml: while scanning a plain scalar
in "", line 230,
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the problem
On Wed, 3 Apr 2019 10:20:25 +, Jacky Bai wrote:
> From: Bai Ping
>
> Add the binding doc for nxp system counter timer module.
>
> Signed-off-by: Bai Ping
> ---
> change v1->v2
> - remove the blank line at EOF
> change v2->v3
> - update the binding example based on the driver change
> ---
On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote:
> Some RTC devices have a battery-low automatic detection circuit.
> The battery-low event is usually reported with:
>
> - a bit change in a RTC status register
> - a hw signaling (generally using an interrupt generation), changing
>
On Thu, Apr 04, 2019 at 07:09:23AM +0200, Niklas Cassel wrote:
> From: Sricharan R
>
> The kryo cpufreq driver reads the nvmem cell and uses that data to
> populate the opps. There are other qcom cpufreq socs like krait which
> does similar thing. Except for the interpretation of the read data,
>
On Thu, Apr 04, 2019 at 07:09:28AM +0200, Niklas Cassel wrote:
> Add DT bindings to describe the CPR HW found on certain Qualcomm SoCs.
>
> Co-developed-by: Jorge Ramirez-Ortiz
> Signed-off-by: Jorge Ramirez-Ortiz
> Signed-off-by: Niklas Cassel
> ---
> .../bindings/power/avs/qcom,cpr.txt
On Wed, 3 Apr 2019 17:38:20 -0700, Paul Walmsley wrote:
> Add preprocessor macros for the important PRCI output clocks
> that are needed by both the FU540 PRCI driver and DT data.
> Details are available in the FU540 manual in Chapter 7 of
>
> https://static.dev.sifive.com/FU540-C000-v1.0.pdf
On Thu, Apr 04, 2019 at 01:50:20AM +, Chris Packham wrote:
> Hi,
>
> I'm implementing support for some modular Linux based systems using
> device tree overlays. The code is working but it seems a little more
> fiddly that than it should be so I'm wondering if I'm doing it right.
>
> An exam
On Mon, 1 Apr 2019 10:17:18 -0700, Douglas Anderson wrote:
> From: Sean Paul
>
> This patch adds a new subnode to simple-panel allowing us to override
> the typical timing expressed in the panel's display_timing.
>
> Changes in v2:
> - Split out the binding into a new patch (Rob)
> - display-
On Wed, 3 Apr 2019 10:16:25 +0200, =?UTF-8?q?Yannick=20Fertr=C3=A9?= wrote:
> This patch adds documentation of a new property phy-dsi-supply to the
> STM32 DSI controller.
>
> Signed-off-by: Yannick Fertré
> ---
> Documentation/devicetree/bindings/display/st,stm32-ltdc.txt | 3 +++
> 1 file cha
On Tue, 2 Apr 2019 16:18:41 +0300, Beniamin Bia wrote:
> Document support for AD7616 Analog to Digital Converter.
>
> Signed-off-by: Beniamin Bia
> ---
> Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Mon, 1 Apr 2019 12:13:35 +0200, =?UTF-8?q?Guido=20G=C3=BCnther?= wrote:
> Add support for the MIXEL DPHY IP as found on NXP's i.MX8MQ SoCs.
>
> Signed-off-by: Guido Günther
> Reviewed-by: Sam Ravnborg
> ---
> .../bindings/phy/mixel,mipi-dsi-phy.txt | 29 +++
> 1 file
On Fri, 29 Mar 2019 17:06:46 +0100, Jerome Brunet wrote:
> Add a new compatible string and additional clock ids for audio clock
> controller of the g12a SoC family.
>
> Signed-off-by: Jerome Brunet
> ---
> .../bindings/clock/amlogic,axg-audio-clkc.txt | 3 ++-
> include/dt-bindings/clo
On Sat, 30 Mar 2019 06:50:37 +0100, Sergio Paracuellos wrote:
> Add bindings to describe Mediatek MT7621 PCIe PHY.
>
> Signed-off-by: Sergio Paracuellos
> ---
> .../bindings/phy/mediatek,mt7621-pci-phy.txt | 28 +++
> 1 file changed, 28 insertions(+)
> create mode 100644
> Doc
On Wed, Mar 27, 2019 at 01:14:47PM +0800, Peter Shih wrote:
> From: Pi-Hsun Shih
>
> Add a DT binding documentation for ChromeOS EC driver over rpmsg.
>
> Signed-off-by: Pi-Hsun Shih
> ---
> Changes from v6:
> - No change.
>
> Changes from v5:
> - New patch.
> ---
> Documentation/devicetree
On Fri, 29 Mar 2019 15:13:22 +1300, Chris Packham wrote:
> Add an example showing how to use the addr-gpios property to deal with a
> system with limited IO space.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Chris Packham
> ---
> Changes in v2:
> - None
>
> .../devicetree/bindings/mtd/m
On Mon, 1 Apr 2019 14:43:04 +0800, Elaine Zhang wrote:
> Add a new compatible for thermal founding on PX30 SoCs.
>
> Signed-off-by: Elaine Zhang
> ---
> Documentation/devicetree/bindings/thermal/rockchip-thermal.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
Hi,
Cc Andrew for patch inclusion
On 2019/4/6 0:27, Matthew Wilcox wrote:
> On Fri, Apr 05, 2019 at 02:52:17PM +0800, Hou Tao wrote:
>> We have got KASAN splat when tried to set /proc/sys/fs/file-max:
>
> Matteo Croce already has a patch in-flight for this.
>
>
Yes, I find it now: https://lkml
On Sat, Apr 06, 2019 at 09:51:19AM +0800, Baoquan He wrote:
> It's KASLR happened in kernel_randomize_memory() of arch/x86/mm/kaslr.c .
What is "KASLR happened in"? This doesn't make any sense. When you look
at that function, there's a comment above it:
/* Initialize base and padding for each mem
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the problem
On 4/5/19 9:55 AM, Maxime Ripard wrote:
> Hi,
>
> On Fri, Apr 05, 2019 at 06:24:55AM -0400, Yangtao Li wrote:
>> Allwinner Process Voltage Scaling Tables defines the voltage and
>> frequency value based on the speedbin blown in the efuse combination.
>> The sunxi-cpufreq-nvmem driver reads the ef
On Sat, Apr 06, 2019 at 10:17:05AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> dev.2019.04.04a
> head: 6f1d86fa5cd6dc95118310607a6bc6f3c6e3092a
> commit: 07366215c9b454bb6ee5648e18ee91a5c4fd0ea6 [35/54] drivers/gpu/drm/amd:
>
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtlwifi/base.c: In function 'rtl_tx_agg_stop':
drivers/staging/rtlwifi/base.c:1733:23: warning:
variable 'tid_data' set but not used [-Wunused-but-set-variable]
drivers/staging/rtlwifi/base.c: In function 'rtl_check_beacon_key':
driv
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtl8192e/rtl8192e/rtl_pci.c: In function 'rtl92e_check_adapter':
drivers/staging/rtl8192e/rtl8192e/rtl_pci.c:36:6: warning:
variable 'VenderID' set but not used [-Wunused-but-set-variable]
u16 VenderID;
^
It's never used and
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtlwifi/rtl8822be/hw.c: In function
'rtl8822be_update_hal_rate_mask':
drivers/staging/rtlwifi/rtl8822be/hw.c:2144:5: warning:
variable 'curtxbw_40mhz' set but not used [-Wunused-but-set-variable]
It's never used and can be removed.
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/comedi/drivers/dyna_pci10xx.c: In function
'dyna_pci10xx_insn_write_ao':
drivers/staging/comedi/drivers/dyna_pci10xx.c:109:21: warning:
variable 'range' set but not used [-Wunused-but-set-variable]
unsigned int chan, range;
driver
Good Day,
Please accept my apologies for writing you a surprise letter.I am
Mr.Ahmed Owain, account Manager with an investment bank here in
Burkina Faso.I have a very important business I want to discuss with
you.There is a draft account opened in my firm by a long-time client
of our bank.I have t
On 04/05/19 at 07:22pm, Thomas Gleixner wrote:
> On Fri, 5 Apr 2019, Borislav Petkov wrote:
> > On Thu, Apr 04, 2019 at 10:03:13AM +0800, Baoquan He wrote:
> > > In memory region KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate
> >
> > What is "memory region KASLR"?
> >
> > > the initial size o
On 04/05/19 at 06:58pm, Borislav Petkov wrote:
> On Thu, Apr 04, 2019 at 10:03:13AM +0800, Baoquan He wrote:
> > In memory region KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate
>
> What is "memory region KASLR"?
It's KASLR happened in kernel_randomize_memory() of arch/x86/mm/kaslr.c .
In fact
On 03/12/19 at 06:30pm, Baoquan He wrote:
> This is v3 post.
>
> The original v1 post can be found here:
> http://lkml.kernel.org/r/20180829141624.13985-1-...@redhat.com
>
> Later a v1 RESEND version:
> http://lkml.kernel.org/r/20190125022817.29506-1-...@redhat.com
>
> V2 post is here:
> http://
On 04/05/19 at 10:23pm, Thomas Gleixner wrote:
> On Tue, 12 Mar 2019, Baoquan He wrote:
>
> > Add two bits XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
> > Bit XLF_5LEVEL indicates if 5-level related code is contained
> > in this kernel.
> > Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_
The pull request you sent on Fri, 5 Apr 2019 08:46:48 -0600:
> git://github.com/awilliam/linux-vfio.git tags/vfio-v5.1-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3e28fb0fcb69dbedfe254939143198b46d83bfa1
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.w
On 04/05/19 at 10:38pm, Thomas Gleixner wrote:
> On Tue, 12 Mar 2019, Baoquan He wrote:
>
> > In relocate_kernel() CR4.LA57 flag is set before kexec jumping if
> > the kernel has 5-level paging enabled. Then in boot/compressed/head_64.S,
> > it will check if the booting kernel is in 4-level or 5-l
On Thu, Apr 4, 2019 at 4:31 PM Aubrey Li wrote:
>
> On Fri, Feb 22, 2019 at 12:42 AM Peter Zijlstra wrote:
> >
> > On Thu, Feb 21, 2019 at 04:19:46PM +, Valentin Schneider wrote:
> > > Hi,
> > >
> > > On 18/02/2019 16:56, Peter Zijlstra wrote:
> > > [...]
> > > > +static bool try_steal_cookie
The mm-of-the-moment snapshot 2019-04-05-18-28 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
> > I'd have:
> >
> > *x = 1; /* A */
> > smp_mb__before_atomic();
> > r0 = xchg_relaxed(x, 2); /* B (read or write part) */
> >
> > => (A ->barrier B)
>
> Perhaps so. It wasn't clear initially how these should be treated, so
> I just ignored them. For example, what should happ
On Fri, Apr 5, 2019 at 1:26 PM Peter Zijlstra wrote:
>
> On Fri, Apr 05, 2019 at 10:00:03AM -0700, Stephane Eranian wrote:
>
> > > > +static void update_tfa_sched(void *ignored)
> > > > +{
> > > > + struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> > > > + struct pmu *pmu = x86_
So I am starting this thread as a spot to collect my thoughts on the
current guest free page hinting design as well as point out a few
possible things we could do to improve upon it.
1. The current design isn't likely going to scale well to multiple
VCPUs. The issue specifically is that the zone l
The pull request you sent on Fri, 5 Apr 2019 18:17:21 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2f9e10acfa1243a7d0ad323873f4a193144a25c3
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 6 Apr 2019 00:45:47 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bc5725f97408ce78e61735858a113f514738ba3b
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
The pull request you sent on Fri, 5 Apr 2019 10:18:32 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-5.1-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/970b766cfd3f3cb7275bf51144b1678c547882fc
Thank you!
--
Deet-doot-dot,
On Fri, Apr 5, 2019 at 9:22 AM Waiman Long wrote:
>
> v2:
> - Move the negative reader count checking patch (patch 12->10)
> forward to before the merge owner to count patch as suggested by
> Linus & expand the comment.
All looks good to me now.
I didn't apply and _test_ any of the pa
Hi,
> Basically we need to come up with a convention to (optionally) indicate
> the sensors location with a udev attribute set by:
> /lib/udev/hwdb.d/60-sensor.hwdb
So should we start adding `ACCEL_LOCATION=display` and
`ACCEL_LOCATION=keyboard` attributes to that file and patch
iio-sensor-proxy
On 4/5/19 3:53 PM, Dan Carpenter wrote:
> On Fri, Apr 05, 2019 at 03:00:46PM -0500, Madhumitha Prabakaran
> wrote:
>> Fix spinlock_t definition without comment.
>>
>> Signed-off-by: Madhumitha Prabakaran
Madhumitha, the reason one would want a comment associated with
a lock field in a structure
These patches fix issues with the nested VMX MSR bitmap. I have already
sent them to Linus.
Paolo
Marc Orr (2):
KVM: x86: nVMX: close leak of L0's x2APIC MSRs (CVE-2019-3887)
KVM: x86: nVMX: fix x2APIC VTPR read intercept
arch/x86/kvm/vmx/nested.c | 74 -
From: Marc Orr
The nested_vmx_prepare_msr_bitmap() function doesn't directly guard the
x2APIC MSR intercepts with the "virtualize x2APIC mode" MSR. As a
result, we discovered the potential for a buggy or malicious L1 to get
access to L0's x2APIC MSRs, via an L2, as follows.
1. L1 executes WRMSR(
From: Marc Orr
Referring to the "VIRTUALIZING MSR-BASED APIC ACCESSES" chapter of the
SDM, when "virtualize x2APIC mode" is 1 and "APIC-register
virtualization" is 0, a RDMSR of 808H should return the VTPR from the
virtual APIC page.
However, for nested, KVM currently fails to disable the read i
Linus,
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to c73f4c998e1fd4249b9edfa39e23f4
Add control of the charging algorithm used on Wilco devices.
See Documentation/ABI/testing/sysfs-class-power-wilco for the
userspace interface and other info.
Signed-off-by: Nick Crews
---
.../ABI/testing/sysfs-class-power-wilco | 30 +++
drivers/platform/chrome/wilco_ec/Kconfig |
Add "Standard", "Adaptive", and "Custom" modes to the charge_type
property, to expand the existing "Trickle" and "Fast" modes.
In addition, add POWER_SUPPLY_PROP_CHARGE_CONTROL_START_THRESHOLD
and POWER_SUPPLY_PROP_CHARGE_CONTROL_END_THRESHOLD properties, to expand
the existing CHARGE_CONTROL_* pro
On Fri, Mar 29, 2019 at 09:00:58AM +0100, Pierre Crégut wrote:
> Ensure that iov->num_VFs is set before a netlink message is sent
> when the number of VFs is changed. Only the path for num_VFs > 0
> is affected. The path for num_VFs = 0 is already correct.
>
> Monitoring programs can relie on netl
On Wed, 3 Apr 2019, Jacky Bai wrote:
> From: Bai Ping
>
> The system counter (sys_ctr) is a programmable system counter
> which provides a shared time base to the Cortex A15, A7, A53 etc cores.
> It is intended for use in applications where the counter is always
> powered on and supports multipl
On 2019-04-05 3:39 p.m., Bjorn Helgaas wrote:
>> -static const char *disable_acs_redir_param;
>> +static char disable_acs_redir_param[COMMAND_LINE_SIZE];
>
> I certainly acknowledge the problem, but I'm a little hesitant to add
> a static buffer of 256-4096 bytes (2048 on x86, arm64, powerpc, s
On Fri, 5 Apr 2019, Josh Poimboeuf wrote:
> On Fri, Apr 05, 2019 at 05:07:15PM +0200, Thomas Gleixner wrote:
> > +/*
> > + * The exception stack ordering in [cea_]exception_stacks
> > + */
> > +enum exception_stack_ordering {
> > + ISTACK_DF,
> > + ISTACK_NMI,
> > + ISTACK_DB,
> > + ISTACK
On Fri, 5 Apr 2019, Borislav Petkov wrote:
> From: Jann Horn
>
> Change generic_load_microcode() to use the iov_iter API instead of a
> clumsy open-coded version which has to pay attention to __user data
> or kernel data, depending on the loading method. This allows to avoid
> explicit casting b
Hello, I want to set up a social project in town to help the less
privileged and physically challenged. I will give you details about
this project and the reason behind it upon your response.
On Fri, 5 Apr 2019, Josh Poimboeuf wrote:
> On Fri, Apr 05, 2019 at 05:07:18PM +0200, Thomas Gleixner wrote:
> > The current implementation of in_exception_stack() iterates over the
> > exception stacks array. Most of the time this is an useless exercise, but
> > even for the actual use cases (perf
On Fri, Apr 05, 2019 at 05:07:15PM +0200, Thomas Gleixner wrote:
> +/*
> + * The exception stack ordering in [cea_]exception_stacks
> + */
> +enum exception_stack_ordering {
> + ISTACK_DF,
> + ISTACK_NMI,
> + ISTACK_DB,
> + ISTACK_MCE,
> + N_EXCEPTION_STACKS
> +};
While clever,
Starting with 4.18 we noticed changing own commandline in Perl by setting
$0 leads to (a bit) surprising results.
As long as we're setting $0 to something longer than the initial argv0,
everything works (almost) as expected: reading from /proc/$$/cmdline
yields what we set $0 to, followed by a
On Fri, Apr 05, 2019 at 05:07:18PM +0200, Thomas Gleixner wrote:
> The current implementation of in_exception_stack() iterates over the
> exception stacks array. Most of the time this is an useless exercise, but
> even for the actual use cases (perf and ftrace) it takes at least 2
> iterations to g
On Fri, 5 Apr 2019, Borislav Petkov wrote:
> From: Borislav Petkov
>
> The commit in Fixes: added the new define UCODE_NEW to denote that an
That reads odd. What's wrong with:
Commit 2613f36ed965 added
or
A recent commit added
mm?
> update should happen only when newer microcode (than
On Fri, 5 Apr 2019, Borislav Petkov wrote:
> From: Borislav Petkov
>
> This is the ancient loading interface which requires special tools to be
> used. The bigger problem with it is that it is as inadequate for proper
> loading of microcode as the late microcode loading interface is because
> it
On Mon, 1 Apr 2019, Daniel Bristot de Oliveira wrote:
> Currently, the irq_vector class of tracepoints does not include the NMI
> entry. The NMI was in the first set of tracepoints for IRQs, but it was
> dropped off because of the logic of switching IDT when enabling trace[1].
> However, as the swi
Now that Docbook has been deprecated in favor of Sphinx, the -nofunction
option in kernel-doc is defunct, e.g. Sphinx doesn't currently support
it. Furthermore, "functions only" behavior was used by Docproc to avoid
duplicating exported symbols, which is now handled by -export and
-internal.
The
...now that it applies to all symbol types. Do the rename before
Sphinx starts using the existing option.
Signed-off-by: Sean Christopherson
---
scripts/kernel-doc | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 1b40b1079
The -function option applies to all symbol types, not just functions.
Rename it and update its help text and comments to reflect reality.
Signed-off-by: Sean Christopherson
---
Documentation/sphinx/kerneldoc.py | 4 ++--
scripts/kernel-doc| 8
2 files changed, 6 insertio
Hi,
On 05/04/2019 11:14:35+, Han Nandor wrote:
> DS3232 RTC has 236 bytes of persistent memory.
>
> Add RTC SRAM read and write access using
> the NVMEM Framework.
>
> Signed-off-by: Nandor Han
> ---
>
> Description
> ---
> Provides DS3232 RTC SRAM access using NVMEM framework.
>
Missatge de Guenter Roeck del dia dv., 5 d’abr.
2019 a les 23:38:
>
> On Fri, Apr 5, 2019 at 2:09 PM Enric Balletbo Serra
> wrote:
> >
> > Hi Guenter,
> >
> > Missatge de Guenter Roeck del dia dv., 5 d’abr.
> > 2019 a les 21:59:
> > >
> > > Hi Enric,
> > >
> > > On Wed, Apr 3, 2019 at 6:54 AM E
>
> Now I'm confused, isn't this the same patch I picked this morning from
> you and is already applied in chrome-platform for-next?
>
Sorry, I didn't see that it was already applied in for-next. Just ignore
this patch and assume that the next two in this series are based
off the current state of
On 4/5/19 3:55 PM, Guenter Roeck wrote:
> On Fri, Apr 05, 2019 at 01:04:27PM -0500, Gustavo A. R. Silva wrote:
>> Hi all,
>>
>> Friendly ping:
>>
>> Who can take this?
>
> I added it to my watchdog-next branch. Usually Wim will pick it up from there.
>
Awesome. :)
Thanks, Guenter.
--
Gustavo
On Mon, Apr 01, 2019 at 01:33:02PM -0600, Logan Gunthorpe wrote:
> In most cases, kmalloc will not be available early in boot when
> pci_setup() is called. Thus, the kstrdup call that was added to fix the
> __initdata bug with the disable_acs_redir parameter usually returns
> NULL. Thus the paramet
On Fri, Apr 5, 2019 at 2:09 PM Enric Balletbo Serra wrote:
>
> Hi Guenter,
>
> Missatge de Guenter Roeck del dia dv., 5 d’abr.
> 2019 a les 21:59:
> >
> > Hi Enric,
> >
> > On Wed, Apr 3, 2019 at 6:54 AM Enric Balletbo i Serra
> > wrote:
> > >
> > > From: Guenter Roeck
> > >
> > > The CrOS USB
From: Long Li
When packets are waiting for outbound I/O and interrupted, return the
proper error code to user process.
Signed-off-by: Long Li
---
fs/cifs/smbdirect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cifs/smbdirect.c b/fs/cifs/smbdirect.c
index 7259427..df9
From: Long Li
Now upper layer is handling the transport shutdown and reconnect, remove
the code that handling transport shutdown on RDMA disconnect.
Signed-off-by: Long Li
---
fs/cifs/cifs_debug.c | 8 ++--
fs/cifs/smbdirect.c | 120 +++
fs/ci
From: Long Li
Failure to send a packet doesn't mean it's a permanent failure, it can't be
returned to user process. This I/O should be retried or failed based on
server packet response and transport health. This logic is handled by the
upper layer.
Give this decision to upper layer.
Signed-off-
From: Long Li
Memory registration failure doesn't mean this I/O has failed, it means the
transport is hitting I/O error or needs reconnect. This error is not from
the server.
Indicate this error to upper layer, and let upper layer decide how to
reconnect and proceed with this I/O.
Signed-off-by
From: Long Li
When transport is being destroyed, it's possible that some processes may
hold memory registrations that need to be deregistred.
Call them first so nobody is using transport resources, and it can be
destroyed.
Signed-off-by: Long Li
---
fs/cifs/connect.c | 36 +++-
Hi Nick,
Missatge de Nick Crews del dia dv., 5 d’abr.
2019 a les 22:09:
>
> The current API for the wilco EC mailbox interface is bad.
>
> It assumes that most messages sent to the EC follow a similar structure,
> with a command byte in MBOX[0], followed by a junk byte, followed by
> actual data.
On Thu, 04 Apr 2019 23:01:11 PDT (-0700), a...@brainfault.org wrote:
On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote:
On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote:
> The Maximum Physical Memory 2GiB option for 64bit systems is currently
> broken because kernel hangs at bo
On Mon, 1 Apr 2019, Daniel Bristot de Oliveira wrote:
> Currently, the irq_vectors is showing the entry and exit events for
> the interrupts of the architecture, but not for external interrupts.
Those are covered by the irq tracepoints. Is there a really good reason why
we need both?
Thanks,
On Mon, 1 Apr 2019, Jian-Hong Pan wrote:
> +/*
> + * Some machines require the "reboot=e" commandline options
> + */
> +static int __init set_efi_reboot(const struct dmi_system_id *d)
> +{
> + if (reboot_type != BOOT_EFI) {
> + reboot_type = BOOT_EFI;
So if EFI is disabled in the k
On Fri, Apr 05, 2019 at 04:20:47PM +0100, Andre Przywara wrote:
> There is a Marvell 88SE9170 PCIe SATA controller I found on a board
> here. Some quick testing with the ARM SMMU enabled reveals that it
> suffers from the same requester ID mixup problems as the other Marvell
> chips listed already.
Hi Guenter,
Missatge de Guenter Roeck del dia dv., 5 d’abr.
2019 a les 21:59:
>
> Hi Enric,
>
> On Wed, Apr 3, 2019 at 6:54 AM Enric Balletbo i Serra
> wrote:
> >
> > From: Guenter Roeck
> >
> > The CrOS USB PD logging feature is logically separate functionality of
> > the charge manager, hence
On Fri, 5 Apr 2019, Sean Christopherson wrote:
> On Fri, Apr 05, 2019 at 05:07:17PM +0200, Thomas Gleixner wrote:
> > + /*
> > +* Note, this covers the guard page between DB and DB1 as well to
> > +* avoid two checks. But by all means @addr can never point into
> > +* the guard page.
On Fri, 5 Apr 2019, Sean Christopherson wrote:
> On Fri, Apr 05, 2019 at 05:07:07PM +0200, Thomas Gleixner wrote:
> > +#ifdef CONFIG_X86_64
> > +
> > +/* Macro to enforce the same ordering and stack sizes */
> > +#define ESTACKS_MEMBERS(guardsize) \
> > + charDF_stack[EXCEPTION_STKSZ]
On Fri, Apr 05, 2019 at 01:04:27PM -0500, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
I added it to my watchdog-next branch. Usually Wim will pick it up from there.
Guenter
>
> Thanks
> --
> Gustavo
>
> On 3/20/19 7:15 PM, Gustavo A. R. Silva wrote:
> >
>
Commit-ID: bbba0e7c5cdadb47a91edea1d5cd0caadbbb016f
Gitweb: https://git.kernel.org/tip/bbba0e7c5cdadb47a91edea1d5cd0caadbbb016f
Author: Daniel Lezcano
AuthorDate: Thu, 28 Mar 2019 16:13:36 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 5 Apr 2019 22:51:29 +0200
genirq/timings: Add a
On Fri, Apr 05, 2019 at 05:07:17PM +0200, Thomas Gleixner wrote:
> The debug IST stack is actually two separate debug stacks to handle #DB
> recursion. This is required because the CPU starts always at top of stack
> on exception entry, which means on #DB recursion the second #DB would
> overwrite
Commit-ID: bfe83844987a52dc1f71f757b60523811502dc93
Gitweb: https://git.kernel.org/tip/bfe83844987a52dc1f71f757b60523811502dc93
Author: Daniel Lezcano
AuthorDate: Thu, 28 Mar 2019 16:13:35 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 5 Apr 2019 22:51:29 +0200
genirq/timings: Remov
On 4/4/19 1:51 PM, Randy Dunlap wrote:
> 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 Rothwe
On Fri, Apr 05, 2019 at 03:00:46PM -0500, Madhumitha Prabakaran wrote:
> Fix spinlock_t definition without comment.
>
> Signed-off-by: Madhumitha Prabakaran
> ---
> drivers/staging/greybus/connection.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/grey
On Fri, Apr 05, 2019 at 01:48:38PM -0700, Sean Christopherson wrote:
> On Fri, Apr 05, 2019 at 05:07:07PM +0200, Thomas Gleixner wrote:
> > At the moment everything assumes a full linear mapping of the various
> > exception stacks. Adding guard pages to the cpu entry area mapping of the
> > excepti
On Fri, Apr 05, 2019 at 05:07:07PM +0200, Thomas Gleixner wrote:
> At the moment everything assumes a full linear mapping of the various
> exception stacks. Adding guard pages to the cpu entry area mapping of the
> exception stacks will break that assumption.
>
> As a preparatory step convert both
The rt5677 driver uses ACPI-style property names to read from the
device API. However, these do not match the property names in _DSD
used on the Chromebook Pixel 2015, which are closer to the Device Tree
style. Unify the two functions for reading from the device API so that
they try ACPI-style nam
From: Ben Zhang
The rt5677 driver writes to the IRQ control register within the IRQ
handler in order to flip the polarity of the interrupts that have been
signalled. If an interrupt fires in the interval between the
regmap_read and the regmap_write, it will not trigger a new call to
rt5677_irq.
From: Ben Zhang
This patch allows headphone plug detect and mic present
detect to be enabled at the same time. This patch implements
an irq_chip with irq_domain directly instead of using
regmap_irq, so that interrupt source line polarities can
be flipped to support irq sharing.
Signed-off-by: Be
Headphone/mic jack detection doesn't work on the Chromebook Pixel 2015.
This patch changes the irq implementation to support polarity flipping
and fixes the configuration code so that correct GPIO pins are read
from ACPI.
With this series, plugging and unplugging the headphone jack switches
betwe
Quoting Michael Turquette (2019-04-05 08:43:40)
> Hi Jerome,
>
> On Fri, Mar 29, 2019 at 3:58 PM Jerome Brunet wrote:
> >
> > On Fri, 2019-03-29 at 15:14 -0700, Stephen Boyd wrote:
> > > > > We actively discourage using init callbacks. Can you do this some
> > > > > other
> > > > > way?
> > > >
On Tue, 12 Mar 2019, Baoquan He wrote:
> In relocate_kernel() CR4.LA57 flag is set before kexec jumping if
> the kernel has 5-level paging enabled. Then in boot/compressed/head_64.S,
> it will check if the booting kernel is in 4-level or 5-level paging
> mode, and handle accordingly. However, the
1 - 100 of 596 matches
Mail list logo
