On Wed, Jun 10, 2020 at 11:47:35AM +0200, Christian Brauner wrote:
> On Tue, Jun 09, 2020 at 09:52:12PM -0700, Kees Cook wrote:
> > Hi,
> >
> > This extends the recent work hch did for scm_detach_fds(), and updates
> > the compat path as well, fixing bugs in the process. Additionally,
> > an
Hello,
syzbot found the following crash on:
HEAD commit:7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0d3a610
kernel config: https://syzkaller.appspot.com/x/.config?x=d195fe572fb15312
On Wed, Jun 10, 2020 at 7:18 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Wed, Jun 10, 2020 at 11:09:56AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Jun 10, 2020 at 11:05:26AM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Tue, Jun 09, 2020 at 04:43:44PM -0700, Ian Rogers escreveu:
>
On 6/10/20 6:33 AM, Dmitry Osipenko wrote:
10.06.2020 09:02, Sowjanya Komatineni пишет:
This patch adds an API of_tegra_mipi_request() to allow creating
mipi device for specific device node rather than a device so Tegra
CSI driver can use it for calibrating MIPI pads for each stream
On 6/10/20 6:14 AM, Dmitry Osipenko wrote:
10.06.2020 09:02, Sowjanya Komatineni пишет:
VI I2C is on host1x bus and is part of VE power domain.
During suspend/resume VE power domain goes through power off/on.
So, controller reset followed by i2c re-initialization is required
after the
On Wed, May 06, 2020 at 04:20:59PM +0800, Yang Weijiang wrote:
> Several parts in KVM have been updated to provide VM CET support, including:
> CPUID/XSAVES config, MSR pass-through, user space MSR access interface,
> vmentry/vmexit config, nested VM etc. These patches have dependency on CET
>
On Wed, Jun 10, 2020 at 8:48 AM Gerald Schaefer
wrote:
>
> This was found by coincidence in s390 code, and a quick check showed that
> there are quite a lot of other architectures that seem to be affected in a
> similar way. I'm preparing a fix for s390, by moving the accounting behind
> the
On Wed, Jun 10, 2020 at 9:34 AM Heikki Krogerus
wrote:
>
> On Tue, Jun 09, 2020 at 04:57:40PM -0700, Prashant Malani wrote:
> > Hi Rob,
> >
> > Thanks again for the comments and feedback. Kindly see responses inline:
> >
> > (Trimming unrelated text from thread):
> >
> > On Tue, Jun 09, 2020 at
On Wed, Jun 10, 2020 at 05:48:11PM +0200, Gerald Schaefer wrote:
> Hi,
Hi, Gerald,
>
> Some architectures have their page fault accounting code inside the fault
> retry loop, and rely on only going through that code once. Before commit
> 4064b9827063 ("mm: allow VM_FAULT_RETRY for multiple
Sorry, error message was not posted. Following is the error message
crash: cannot determine VA_BITS_ACTUAL
-Original Message-
From: Bharat Gooty [mailto:bharat.go...@broadcom.com]
Sent: Wednesday, June 10, 2020 10:18 PM
To: Scott Branden; 'Bhupesh Sharma'; 'Amit Kachhap'
Cc: 'Mark
On Wed, Jun 10, 2020 at 01:59:24PM +0200, Geert Uytterhoeven wrote:
> On Wed, Jun 10, 2020 at 1:08 PM Mark Brown wrote:
> > To repeat my previous feedback I'd expect a driver update as well.
> No driver update is needed.
> Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml says:
I'm
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Thanks for addressing the previous comments, this looks
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> v2: Introduce changes suggested by Florian:
> - Add separate YAML file for dt-bindings.
> -
Hello Bhupesh,
V6 patch set on Linux 5.7, did not help.
I have applied makedump file
http://lists.infradead.org/pipermail/kexec/2019-November/023963.html changes
also (makedump-1.6.6). Tried to apply it on makedumpfile 1.6.7. Patch set_2
failed. Would like to know, if you have V5 patch set for
Hi Pi-Hsun,
Thank you for your patch.
On 10/6/20 11:07, Pi-Hsun Shih wrote:
> Add driver for cros-ec-regulator, representing a voltage regulator that
> is connected and controlled by ChromeOS EC, and is controlled by kernel
> with EC host commands.
>
> Signed-off-by: Pi-Hsun Shih
> ---
>
On Tue, Jun 09, 2020 at 09:52:14PM -0700, Kees Cook wrote:
> The sock counting (sock_update_netprioidx() and sock_update_classid())
> was missing from this implementation of fd installation, compared to
> SCM_RIGHTS. Use the new scm helper to get the work done, after adjusting
> it to return the
On 6/10/2020 9:32 AM, Álvaro Fernández Rojas wrote:
> BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
> to enable/disable certain components in order to save power.
>
> Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Florian Fainelli
--
Florian
On Fri 08-05-20 14:30:56, Johannes Weiner wrote:
> Memcg maintains private MEMCG_CACHE and NR_SHMEM counters. This
> divergence from the generic VM accounting means unnecessary code
> overhead, and creates a dependency for memcg that page->mapping is set
> up at the time of charging, so that page
Em Wed, Jun 10, 2020 at 05:41:29PM +0200, Jiri Olsa escreveu:
> On Tue, Jun 09, 2020 at 10:17:15PM -0700, Ian Rogers wrote:
> > This simplifies computing ratios in json expressions.
>
> please put in the comment some usage example and add
> a test for this to tests/expr.c
>
> same for the '<>'
On Sat, May 16, 2020 at 01:36:38AM +0900, Sergey Senozhatsky wrote:
> On (20/05/15 17:32), Sumit Garg wrote:
> > > Can I please have some context what problem does this solve?
> >
> > You can find the problem description here [1] which leads to this fix.
>
> [..]
>
> > [1]
It was reported that older GCCs compile smm_test in a way that breaks
it completely:
kvm_exit: reason EXIT_CPUID rip 0x4014db info 0 0
func 7ffd idx 830 rax 0 rbx 0 rcx 0 rdx 0, cpuid entry not found
...
kvm_exit: reason EXIT_MSR rip 0x40abd9 info 0 0
On Wed, Jun 10, 2020 at 05:31:03PM +0200, Jerome Brunet wrote:
> I'm not sure what to do with this report.
> I tried to reproduce has instructed, the log is full of warnings and the
> compilation eventually fails to link.
> It seems that most (if not all) drivers with a MODULE_DEVICE_TABLE()
Power Management Controller (PMC) can override the PLLM clock settings,
including the enable-state. Although PMC could only act as a second level
gate, meaning that PLLM needs to be enabled by the Clock and Reset
Controller (CaR) anyways if we want it to be enabled. Hence, when PLLM is
overridden
On Mon, Mar 16, 2020 at 06:00:42PM -0300, Helen Koike wrote:
> Hi,
>
> This series adds support for simultaneous streaming from both capture
> devices (rkisp1_selfpath and rkisp1_mainpath).
>
> It depends on the following series for multistream to work properly, but
> it doesn't mean it can't be
BCM6362 SoCs have a power domain controller to enable/disable certain
components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
---
v2: Add dt-bindings header files.
arch/mips/boot/dts/brcm/bcm6362.dtsi | 6 ++
BCM6318 SoCs have a power domain controller to enable/disable certain
components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
---
v2: Add BCM6318 dt-bindings header file.
include/dt-bindings/soc/bcm6318-pm.h | 17 +
1 file changed, 17 insertions(+)
create
BCM63268 SoCs have a power domain controller to enable/disable certain
components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
---
v2: Add support for BCM63268 too.
arch/mips/boot/dts/brcm/bcm63268.dtsi | 6 ++
include/dt-bindings/soc/bcm63268-pm.h | 21
BCM6328 SoCs have a power domain controller to enable/disable certain
components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
Acked-by: Florian Fainelli
---
v2: Add dt-bindings header files.
arch/mips/boot/dts/brcm/bcm6328.dtsi | 6 ++
Hi,
this series puts together the recent series "replace runtime slub_debug
toggling with more capable boot parameter" [4] (no longer RFC, thanks for
reviews), with older RFC [5] to introduce a static key for slub_debug. It's
because the removal of runtime toggling makes the static key addition
On 6/10/20 6:42 PM, Krzysztof Kozlowski wrote:
>
> Driver allocates DMA memory with dma_alloc_coherent() but frees it with
> dma_unmap_single().
>
> This causes DMA warning during system shutdown (with DMA debugging) on
> Toradex Colibri VF50 module:
>
> WARNING: CPU: 0 PID: 1 at
There are few more places in SLUB that could benefit from reduced overhead of
the static key introduced by a previous patch:
- setup_object_debug() called on each object in newly allocated slab page
- setup_page_debug() called on newly allocated slab page
- __free_slab() called on freed slab page
The function cache_from_obj() was added by commit b9ce5ef49f00 ("sl[au]b:
always get the cache from its page in kmem_cache_free()") to support kmemcg,
where per-memcg cache can be different from the root one, so we can't use
the kmem_cache pointer given to kmem_cache_free().
Prior to that commit,
BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
to enable/disable certain components in order to save power.
v2: Introduce changes suggested by Florian:
- Add separate YAML file for dt-bindings.
- Add bcm63xx folder in drivers/soc/bcm.
- Update MAINTAINERS.
-
One advantage of CONFIG_SLUB_DEBUG is that a generic distro kernel can be built
with the option enabled, but it's inactive until simply enabled on boot,
without rebuilding the kernel. With a static key, we can further eliminate the
overhead of checking whether a cache has a particular debug flag
BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
to enable/disable certain components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
---
v2: Add separate YAML file.
.../bindings/soc/bcm/brcm,bcm63xx-power.yaml | 44 +++
1 file changed,
BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
to enable/disable certain components in order to save power.
Signed-off-by: Álvaro Fernández Rojas
---
v2: Introduce bcm63xx folder in drivers/soc/bcm and update MAINTAINERS.
MAINTAINERS |
SLUB allows runtime changing of page allocation order by writing into the
/sys/kernel/slab//order file. Jann has reported [1] that this interface
allows the order to be set too small, leading to crashes.
While it's possible to fix the immediate issue, closer inspection reveals
potential races.
The attribute reflects the SLAB_RECLAIM_ACCOUNT cache flag. It's not clear why
this attribute was writable in the first place, as it's tied to how the cache
is used by its creator, it's not a user tunable. Furthermore:
- it affects slab merging, but that's not being checked while toggled
- if
There are few places that call kmem_cache_debug(s) (which tests if any of debug
flags are enabled for a cache) immediatelly followed by a test for a specific
flag. The compiler can probably eliminate the extra check, but we can make the
code nicer by introducing kmem_cache_debug_flags() that works
The slub_debug kernel boot parameter can either apply a single set of options
to all caches or a list of caches. There is a use case where debugging is
applied for all caches and then disabled at runtime for specific caches, for
performance and memory consumption reasons [1]. As runtime changes
SLUB_DEBUG creates several files under /sys/kernel/slab// that can be
read to check if the respective debugging options are enabled for given cache.
Some options, namely sanity_checks, trace, and failslab can be also enabled and
disabled at runtime by writing into the files.
The runtime toggling
SLUB_DEBUG creates several files under /sys/kernel/slab// that can be
read to check if the respective debugging options are enabled for given cache.
The options can be also toggled at runtime by writing into the files. Some of
those, namely red_zone, poison, and store_user can be toggled only when
Hi Johan,
On 6/10/20 4:22 PM, Johan Hovold wrote:
> Commit 8e20fc391711 ("serial_core: Move sysrq functions from header
> file") converted the inline sysrq helpers to exported functions which
> are now called for every received character, interrupt and break signal
> also on systems without
Hi Pi-Hsun,
Thank you for your patch. Some few/trivial comments below
On 10/6/20 11:07, Pi-Hsun Shih wrote:
> Add DT binding documentation for cros-ec-regulator, a voltage regulator
> controlled by ChromeOS EC.
>
> Signed-off-by: Pi-Hsun Shih
> ---
> Changes from v2:
> * No change
>
> Changes
On Wed, Jun 10, 2020 at 5:58 PM Nathan Chancellor
wrote:
>
> On Wed, Jun 10, 2020 at 05:55:14PM +0200, Miguel Ojeda wrote:
> > Hi Christian,
> >
> > On Wed, Jun 10, 2020 at 2:51 PM Christian Brauner
> > wrote:
> > >
> > > The provided clang-format file wraps at 80 chars. If no one minds, I'd
>
On Wed, Jun 10, 2020 at 05:22:29PM +0200, Johan Hovold wrote:
> This series fixes a few regressions introduced by the recent sysrq
> rework that went into 5.6.
>
> The fix for the unnecessary per-character overhead probably could have
> been marked for stable but I left that decision to the
On Wed, Jun 10, 2020 at 5:13 PM Michael S. Tsirkin wrote:
>
> On Wed, Jun 10, 2020 at 02:37:50PM +0200, Eugenio Perez Martin wrote:
> > > +/* This function returns a value > 0 if a descriptor was found, or 0 if
> > > none were found.
> > > + * A negative code is returned on error. */
> > >
On 6/10/20 9:44 AM, Paolo Bonzini wrote:
According to the TAP specification, a skipped test must be marked as "ok"
and annotated with the SKIP directive, for example
ok 23 # skip Insufficient flogiston pressure.
(https://testanything.org/tap-specification.html)
Fix the runner script to
On 6/10/2020 04:49, Palmer Dabbelt wrote:
From: Palmer Dabbelt
e1000e_check_me is only used under CONFIG_PM_SLEEP but exists
unconditionally, which triggers a warning.
Signed-off-by: Palmer Dabbelt
---
drivers/net/ethernet/intel/e1000e/netdev.c | 2 ++
1 file changed, 2 insertions(+)
My Dear in the lord
My name is Mrs. Mina A. Brunel I am a Norway Citizen who is living in Burkina
Faso, I am married to Mr. Brunel Patrice, a politicians who owns a small gold
company in Burkina Faso; He died of Leprosy and Radesyge, in year February
2010, During his lifetime he deposited
This patch-set is originated from one of the patches that have been
posted earlier as a part of "Task_isolation" mode [1] patch series
by Alex Belits . There are only a couple of
changes that I am proposing in this patch-set compared to what Alex
has posted earlier.
Context
===
On a broad
From: Alex Belits
The current implementation of cpumask_local_spread() does not
respect the isolated CPUs, i.e., even if a CPU has been isolated
for Real-Time task, it will return it to the caller for pinning
of its IRQ threads. Having these unwanted IRQ threads on an
isolated CPU adds up to a
From: Alex Belits
pci_call_probe() prevents the nesting of work_on_cpu()
for a scenario where a VF device is probed from work_on_cpu()
of the Physical device.
This patch replaces the cpumask used in pci_call_probe()
from all online CPUs to only housekeeping CPUs. This is to
ensure that there are
From: Alex Belits
With the existing implementation of store_rps_map() packets are
queued in the receive path on the backlog queues of other
CPUs irrespective of whether they are isolated or not. This could
add a latency overhead to any RT workload that is running on
the same CPU.
This patch
[I am sorry to come here so late. The series has been already merged so I
am not going to add my acks to separate patches.]
On Fri 08-05-20 14:30:52, Johannes Weiner wrote:
> The try/commit/cancel protocol that memcg uses dates back to when
> pages used to be uncharged upon removal from the page
From: Abhishek Sahu
The deinit issues reset_control_assert for PCI twice and does not contain
phy reset.
Signed-off-by: Abhishek Sahu
Signed-off-by: Ansuel Smith
Reviewed-by: Rob Herring
---
drivers/pci/controller/dwc/pcie-qcom.c | 18 --
1 file changed, 8 insertions(+), 10
Document ext reset used in ipq8064 SoC by qcom PCIe driver.
Signed-off-by: Ansuel Smith
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
Set some specific value for Tx De-Emphasis, Tx Swing and Rx equalization
needed on some ipq8064 based device (Netgear R7800 for example). Without
this the system locks on kernel load.
Fixes: 82a823833f4e ("PCI: qcom: Add Qualcomm PCIe controller driver")
Signed-off-by: Ansuel Smith
Cc:
Rework 2.1.0 revision to use bulk clk api and fix missing assert on
reset_control_deassert error.
Signed-off-by: Ansuel Smith
Reviewed-by: Rob Herring
---
drivers/pci/controller/dwc/pcie-qcom.c | 131 +
1 file changed, 46 insertions(+), 85 deletions(-)
diff --git
Ipq8064-v2 have tx term offset set to 0. Introduce this variant to permit
different offset based on the revision.
Signed-off-by: Ansuel Smith
---
drivers/pci/controller/dwc/pcie-qcom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/controller/dwc/pcie-qcom.c
Document qcom,pcie-ipq8064-v2 needed to use different phy_tx0_term_offset.
In ipq8064 phy_tx0_term_offset is 7. In ipq8064 v2 other SoC it's set to 0
by default.
Signed-off-by: Ansuel Smith
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 1 +
1 file changed, 1
Lots of define are actually already defined in pci_regs.h, directly use
the standard defines.
Signed-off-by: Ansuel Smith
---
drivers/pci/controller/dwc/pcie-qcom.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/controller/dwc/pcie-qcom.c
Add tx term offset support to pcie qcom driver need in some revision of
the ipq806x SoC. Ipq8064 needs tx term offset set to 7.
Fixes: 82a823833f4e ("PCI: qcom: Add Qualcomm PCIe controller driver")
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
Cc: sta...@vger.kernel.org # v4.5+
---
Document missing clks used in ipq8064 SoC.
Signed-off-by: Ansuel Smith
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/qcom,pcie.txt | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
From: Sham Muthayyan
Add Force GEN1 support needed in some ipq8064 board that needs to limit
some PCIe line to gen1 for some hardware limitation. This is set by the
max-link-speed binding and needed by some soc based on ipq8064. (for
example Netgear R7800 router)
Signed-off-by: Sham Muthayyan
Add missing ext reset used by ipq8064 SoC in PCIe qcom driver.
Fixes: 82a823833f4e ("PCI: qcom: Add Qualcomm PCIe controller driver")
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
Cc: sta...@vger.kernel.org # v4.5+
Reviewed-by: Rob Herring
Reviewed-by: Philipp Zabel
---
This contains multiple fix for PCIe qcom driver.
Some optional reset and clocks were missing.
Fix a problem with no PARF programming that cause kernel lock on load.
Add support to force gen 1 speed if needed. (due to hardware limitation)
Add ipq8064 rev 2 support that use a different tx
Aux and Ref clk are missing in PCIe qcom driver. Add support for this
optional clks for ipq8064/apq8064 SoC.
Fixes: 82a823833f4e ("PCI: qcom: Add Qualcomm PCIe controller driver")
Signed-off-by: Sham Muthayyan
Signed-off-by: Ansuel Smith
Reviewed-by: Rob Herring
---
Dear Friend,
Have you received your fund since last year? I saw your payment file
that is why I decided to contact you. You have suffered for nothing
without receiving your fund due to over greediness by the officials.
You would have received your fund since last year but your problem is
over
On Wed, Jun 10, 2020 at 05:26:23PM +0200, Matthias Schiffer wrote:
> On Wed, 2020-06-10 at 16:59 +0200, Sam Ravnborg wrote:
> > Hi Matthias.
> >
> > Thanks, a few details you need to fix. See below.
> >
> > Sam
> >
> > On Wed, Jun 10, 2020 at 02:01:30PM +0200, Matthias Schiffer wrote:
> > >
On Wed, Jun 10, 2020 at 05:55:14PM +0200, Miguel Ojeda wrote:
> Hi Christian,
>
> On Wed, Jun 10, 2020 at 2:51 PM Christian Brauner
> wrote:
> >
> > The provided clang-format file wraps at 80 chars. If no one minds, I'd like
> > to adjust this limit to 100 similar to what checkpatch (cf. [1])
Hi Andy,
Thanks for the review.
On Tue, 2020-06-09 at 21:43 +0300, Andy Shevchenko wrote:
> On Tue, Jun 9, 2020 at 8:50 PM Nicolas Saenz Julienne
> wrote:
> > The board doesn't need the quirks to be run, and takes care of its own
> > initialization trough a reset controller device. So let's
On Wed, Jun 10, 2020 at 10:21:19AM -0500, Jassi Brar wrote:
> On Wed, Jun 10, 2020 at 3:23 AM Sudeep Holla wrote:
> >
> > On Sun, Jun 07, 2020 at 02:30:23PM -0500, jassisinghb...@gmail.com wrote:
> > > From: Jassi Brar
> > >
> > > Currently scmi_do_xfer() submits a message to mailbox api and
On 10.6.2020 18.43, Kai-Heng Feng wrote:
>
>
>> On Jun 10, 2020, at 22:32, Alan Stern wrote:
>>
>> On Wed, Jun 10, 2020 at 02:42:30PM +0800, Kai-Heng Feng wrote:
>>> xHCI spec "4.15.1 Port Suspend" states that port can be put to U3 as long
>>> as Enabled bit is set and from U0, U1 or U2 state.
Hi Christian,
On Wed, Jun 10, 2020 at 2:51 PM Christian Brauner
wrote:
>
> The provided clang-format file wraps at 80 chars. If no one minds, I'd like
> to adjust this limit to 100 similar to what checkpatch (cf. [1]) uses now.
Thanks! Picking this up with a few changes to the commit message.
Drop the recently added gpio include from the serial-core header in
favour of a forward declaration and instead include the gpio header only
where needed.
Signed-off-by: Johan Hovold
---
drivers/tty/serial/8250/8250_port.c | 1 +
drivers/tty/serial/serial_core.c| 1 +
On 09.06.2020 21:47, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 04:49:55PM +0300, Alexander Popov wrote:
>> Add 'verbose' plugin parameter for stackleak gcc plugin.
>> It can be used for printing additional info about the kernel code
>> instrumentation.
>>
>> For using it add the following to
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-5.8-rc1-2
with top-most commit ede439be684c54f01147e1f65cc565c6baaca1a4
Merge branch 'acpica'
on top of commit 118d6e98293b30aee378a6b08d27a35320a3e34f
Merge tag 'acpi-5.8-rc1' of
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.8-rc1-2
with top-most commit 50dd154ed7b17a8b3a1983fc32a8e41d4cc4211a
Merge branches 'pm-cpufreq' and 'pm-acpi'
on top of commit 355ba37d756c38962fe9bb616f5f48eb12a7e11e
Merge tag
On Wed, Jun 10, 2020 at 06:33:47AM -0400, Jeff Layton wrote:
> A patch has been merged for v5.8 that changes how syncfs() reports
> errors. Change the sync() manpage accordingly.
>
> Signed-off-by: Jeff Layton
> ---
> man2/sync.2 | 24 +++-
> 1 file changed, 23
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Kai-Heng Feng
> Sent: Wednesday, June 10, 2020 10:38 AM
> To: alex.h...@canonical.com
> Cc: Kai-Heng Feng; Darren Hart; Andy Shevchenko; open list:INTEL HID EVENT
> DRIVER; open list
From: Luis Chamberlain
When UMH_WAIT_PROC is used we call kernel_wait4(). This is
the *only* place in the kernel where we actually inspect the
error code. Prior to this patch we returned the value from the
wait call, and that technically requires us to use wrappers
such as WEXITSTATUS(). We
From: Tiezhu Yang
There exists redundant "be an" in the comment, remove it.
Acked-by: Luis Chamberlain
Signed-off-by: Tiezhu Yang
Signed-off-by: Luis Chamberlain
---
kernel/kmod.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/kmod.c b/kernel/kmod.c
index
From: Tiezhu Yang
Reset the member "test_fs" of the test configuration after a call
of the function "kfree_const" to a null pointer so that a double
memory release will not be performed.
Fixes: d9c6a72d6fa2 ("kmod: add test driver to stress test the module loader")
Acked-by: Luis Chamberlain
From: Luis Chamberlain
Tiezhu Yang had sent out a patch set with a slew of kmod selftest
fixes, and one patch which modified kmod to return 254 when a module
was not found. This opened up pandora's box about why that was being
used for and low and behold its because when UMH_WAIT_PROC is used
we
Hi Florian,
On Tue, 2020-06-09 at 11:13 -0700, Florian Fainelli wrote:
>
> On 6/9/2020 10:49 AM, Nicolas Saenz Julienne wrote:
> > Some atypical users of xhci-pci might need to manually reset their xHCI
> > controller before starting the HCD setup. Check if a reset controller
> > device is
From: Luis Chamberlain
The "odd" 256 value was just an issue with the umh never
wrapping it around with WEXITSTATUS() for us. Now that it
does that, we can use a sane value / name for the selftest,
and this is no longer a oddity.
We add a way to detect this for older kernels, and support
the
From: Tiezhu Yang
Use the variable NAME instead of "\000" directly in kmod_test_0001().
Acked-by: Luis Chamberlain
Signed-off-by: Tiezhu Yang
Signed-off-by: Luis Chamberlain
---
tools/testing/selftests/kmod/kmod.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Wed, Jun 10, 2020 at 08:41:29AM -0700, Casey Schaufler wrote:
>
> On 6/10/2020 12:59 AM, Andrei Vagin wrote:
> > On Tue, Jun 09, 2020 at 06:14:27PM +0200, Christian Brauner wrote:
> >> On Tue, Jun 09, 2020 at 09:06:27AM -0700, Andrei Vagin wrote:
> >>> On Tue, Jun 09, 2020 at 09:44:22AM +0200,
Hi,
Some architectures have their page fault accounting code inside the fault
retry loop, and rely on only going through that code once. Before commit
4064b9827063 ("mm: allow VM_FAULT_RETRY for multiple times"), that was
ensured by testing for and clearing FAULT_FLAG_ALLOW_RETRY.
That commit
On 09.06.2020 21:46, Kees Cook wrote:
> On Thu, Jun 04, 2020 at 04:49:54PM +0300, Alexander Popov wrote:
>> Let's improve the instrumentation to avoid this:
>>
>> 1. Make stackleak_track_stack() save all register that it works with.
>> Use no_caller_saved_registers attribute for that function.
These are used nowhere in the tree (except for some architectures which
define them for their own use) and were already removed for other
architectures in:
commit 6474924e2b5d ("arch: remove unused macro/function thread_saved_pc()")
commit c17c02040bf0 ("arch: remove unused *_segments()
According to the TAP specification, a skipped test must be marked as "ok"
and annotated with the SKIP directive, for example
ok 23 # skip Insufficient flogiston pressure.
(https://testanything.org/tap-specification.html)
Fix the runner script to match this.
Signed-off-by: Paolo Bonzini
> On Jun 10, 2020, at 22:32, Alan Stern wrote:
>
> On Wed, Jun 10, 2020 at 02:42:30PM +0800, Kai-Heng Feng wrote:
>> xHCI spec "4.15.1 Port Suspend" states that port can be put to U3 as long
>> as Enabled bit is set and from U0, U1 or U2 state.
>>
>> Currently only USB_PORT_FEAT_LINK_STATE
Driver allocates DMA memory with dma_alloc_coherent() but frees it with
dma_unmap_single().
This causes DMA warning during system shutdown (with DMA debugging) on
Toradex Colibri VF50 module:
WARNING: CPU: 0 PID: 1 at ../kernel/dma/debug.c:1036 check_unmap+0x3fc/0xb04
DMA-API: fsl-edma
On Tue, Jun 09, 2020 at 10:17:15PM -0700, Ian Rogers wrote:
> This simplifies computing ratios in json expressions.
please put in the comment some usage example and add
a test for this to tests/expr.c
same for the '<>' operators in the other patch
I'll put documentation on this together with
On 6/10/2020 12:59 AM, Andrei Vagin wrote:
> On Tue, Jun 09, 2020 at 06:14:27PM +0200, Christian Brauner wrote:
>> On Tue, Jun 09, 2020 at 09:06:27AM -0700, Andrei Vagin wrote:
>>> On Tue, Jun 09, 2020 at 09:44:22AM +0200, Christian Brauner wrote:
On Mon, Jun 08, 2020 at 08:42:21PM -0700,
Wireless hotkey on HP platforms can trigger two events, if both
hp-wireless and intel-hid are supported. Two events at the same time
renders wireless hotkey useless.
HP confirmed that hp-wireless (HPQ6001) should always be the canonical
source of wireless hotkey event, so skip registering rfkill
On Tue, 2020-06-09 at 11:14 -0700, Florian Fainelli wrote:
>
> On 6/9/2020 10:49 AM, Nicolas Saenz Julienne wrote:
> > Raspberry Pi 4's co-processor controls some of the board's HW
> > initialization process, but it's up to Linux to trigger it when
> > relevant. Introduce a reset controller
Hi Florian, thanks for the review :)
On Tue, 2020-06-09 at 11:07 -0700, Florian Fainelli wrote:
>
> On 6/9/2020 10:49 AM, Nicolas Saenz Julienne wrote:
> > The firmware running on the RPi VideoCore can be used to reset and
> > initialize HW controlled by the firmware.
> >
> > Signed-off-by:
501 - 600 of 1152 matches
Mail list logo
