On Tue, 18 Jun 2019, Linus Torvalds wrote:
> On Tue, Jun 18, 2019 at 1:16 AM Lee Jones wrote:
> >
> > > Reported-by: Linus Torvalds
> >
> > Ideally we can get a review too.
>
> Looks fine to me, but obviously somebody should actually _test_ it too.
Amelie, would you be so kind?
--
Lee Jones
Really sorry about that, my connection is weird this morning, I'll retry
tomorrow.
Sorry again,
Alex
On 6/19/19 1:42 AM, Alexandre Ghiti wrote:
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
On Mon, Jun 17, 2019 at 01:51:02PM +0100, Lee Jones wrote:
> When booting with ACPI as the active set of configuration tables,
> all; clocks, regulators, pin functions ect are expected to be at
> their ideal values/levels/rates, thus the associated frameworks
> are unavailable. Ensure calls to
From: Anson Huang
For i.MX clock drivers probe fail case, clks should be unregistered
in the return path, this patch adds a common API for i.MX clock
drivers to unregister clocks when fail.
Signed-off-by: Anson Huang
---
New patch.
---
drivers/clk/imx/clk.c | 8
drivers/clk/imx/clk.h
From: Anson Huang
This patch adds i.MX8MN clock driver support.
Signed-off-by: Anson Huang
---
Changes since V4:
- use dev_err instead of pr_err;
- unregister clocks when probe failed.
---
drivers/clk/imx/Kconfig | 6 +
drivers/clk/imx/Makefile | 1 +
From: Anson Huang
Add the clock binding doc for i.MX8MN.
Signed-off-by: Anson Huang
Reviewed-by: Maxime Ripard
---
No changes.
---
.../devicetree/bindings/clock/imx8mn-clock.yaml| 112 +++
include/dt-bindings/clock/imx8mn-clock.h | 215 +
2 files
From: Anson Huang
Enable CONFIG_CLK_IMX8MN to support i.MX8MN clock driver.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 7a21159..29f7768 100644
From: Anson Huang
1416X/1443X PLL are used on i.MX8MM and i.MX8MN and maybe
other i.MX8M series SoC later, the macro definitions of
these PLLs' initialization should be common for usage.
Signed-off-by: Anson Huang
---
No changes.
---
drivers/clk/imx/clk-imx8mm.c | 17 -
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
On Wed 12 Jun 07:26 PDT 2019, Lee Jones wrote:
> When booting with ACPI as the active set of configuration tables,
> all; clocks, regulators, pin functions ect are expected to be at
> their ideal values/levels/rates, thus the associated frameworks
> are unavailable. Ensure calls to these APIs
Ard, Martin,
On Tue, 18 Jun 2019, Martin K. Petersen wrote:
> > New Qualcomm AArch64 based laptops are now available which use UFS
> > as their primary data storage medium. These devices are supplied
> > with ACPI support out of the box. This patch ensures the Qualcomm
> > UFS driver will be
This series fixes the fallback of the top-down mmap: in case of
failure, a bottom-up scheme can be tried as a last resort between
the top-down mmap base and the stack, hoping for a large unused stack
limit.
Lots of architectures and even mm code start this fallback
at TASK_UNMAPPED_BASE, which is
,,
On 2019-06-18 11:32 p.m., Dan Carpenter wrote:
> We already verified that the "nm->isr_ctx" allocation succeeded so there
> is no need to check again here.
>
> Fixes: a6bed7a54165 ("NTB: Introduce NTB MSI Test Client")
> Signed-off-by: Dan Carpenter
Hmm, yup, not sure how that slipped
(Sorry for the previous interrupted series)
This series fixes the fallback of the top-down mmap: in case of
failure, a bottom-up scheme can be tried as a last resort between
the top-down mmap base and the stack, hoping for a large unused stack
limit.
Lots of architectures and even mm code start
On Wed, 19 Jun 2019 01:05:58 +0200,
Randy Dunlap wrote:
>
> On 6/18/19 1:34 PM, Takashi Iwai wrote:
> > We have a nice macro, and the check of emptiness of the font table can
> > be done in a simpler way.
> >
> > Signed-off-by: Takashi Iwai
>
> Hi,
>
> Looks good to me.
> Acked-by: Randy
We already verified that the "nm->isr_ctx" allocation succeeded so there
is no need to check again here.
Fixes: a6bed7a54165 ("NTB: Introduce NTB MSI Test Client")
Signed-off-by: Dan Carpenter
---
Hey Logan, can pick a patch prefix when you're introducing a new module?
"[PATCH] NTB/test:
On Tue, Jun 18, 2019 at 04:39:24PM +0100, Colin King wrote:
> diff --git a/drivers/platform/chrome/wilco_ec/event.c
> b/drivers/platform/chrome/wilco_ec/event.c
> index c975b76e6255..e251a989b152 100644
> --- a/drivers/platform/chrome/wilco_ec/event.c
> +++
On Fri, Jun 14, 2019 at 4:14 PM Lorenzo Pieralisi
wrote:
>
> On Fri, Jun 14, 2019 at 12:38:51PM +0530, Karthikeyan Mitran wrote:
> > Hi Lorenzo and Hou Zhiqiang
> > PAB_INTP_AMBA_MISC_STAT does have other status in the higher bits, it
> > should have been masked before checking for the status
>
On Tue 18-06-19 14:13:16, Yang Shi wrote:
[...]
> > > > > Change migrate_page_add() to check if the page is movable or not, if
> > > > > it
> > > > > is unmovable, just return -EIO. We don't have to check non-LRU
> > > > > movable
> > > > > pages since just zsmalloc and virtio-baloon support
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
Hi Naveen,
Sorry I meant to reply to this earlier .. :/
"Naveen N. Rao" writes:
> With -mprofile-kernel, gcc emits 'mflr r0', followed by 'bl _mcount' to
> enable function tracing and profiling. So far, with dynamic ftrace, we
> used to only patch out the branch to _mcount(). However, mflr is
>
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
Hi Colin,
> Currently the call to device_property_read_u32_array is not error checked
> leading to potential garbage values in the delays array that are then used
> in msleep delays. Add a sanity check to the property fetching.
>
> Addresses-Coverity: ("Uninitialized scalar variable")
>
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
Hi Lorenzo,
On 18/06/19 7:58 PM, Lorenzo Pieralisi wrote:
> On Tue, Jun 18, 2019 at 04:21:17PM +0530, Vidya Sagar wrote:
>
> [...]
>
>>> 2) It is not related to this patch but I fail to see the reasoning
>>> behind the __ in __dw_pci_read_dbi(), there is no no-underscore
>>> equivalent
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
In case of mmap failure in top-down mode, there is no need to go through
the whole address space again for the bottom-up fallback: the goal of this
fallback is to find, as a last resort, space between the top-down mmap base
and the stack, which is the only place not covered by the top-down mmap.
This series fixes the fallback of the top-down mmap: in case of
failure, a bottom-up scheme can be tried as a last resort between
the top-down mmap base and the stack, hoping for a large unused stack
limit.
Lots of architectures and even mm code start this fallback
at TASK_UNMAPPED_BASE, which is
On Mon, Jan 28, 2019 at 10:27:39AM +0100, Miquel Raynal wrote:
Hi Miquel,
> Hi Naga,
>
> Naga Sureshkumar Relli wrote on Mon, 28 Jan 2019
> 06:04:53 +:
>
> > Hi Boris & Miquel,
> >
> > Could you please provide your thoughts on this driver to support HW-ECC?
> > As I said previously, there
The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:
Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
tags/drivers_soc_for_5.3
for you to fetch changes up to
On Tue, 18 Jun 2019 at 19:05, Greg Kroah-Hartman
wrote:
>
> On Tue, Jun 18, 2019 at 06:04:25PM +0530, Naresh Kamboju wrote:
> > On Tue, 18 Jun 2019 at 02:50, Greg Kroah-Hartman
> > wrote:
> > >
> > > This is the start of the stable review cycle for the 5.1.12 release.
> > > There are 115 patches
On 6/17/19 11:41 AM, Suman Anna wrote:
On 6/15/19 7:50 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/firmware/ti_sci.c: In function ti_sci_cmd_ring_config:
drivers/firmware/ti_sci.c:2035:17: warning: variable dev set but not used
[-Wunused-but-set-variable]
On 6/14/19 6:57 AM, Nishad Kamdar wrote:
This patch corrects the SPDX License Identifier style
in header file related to Firmware Drivers for Texas
Instruments SCI Protocol.
For C header files Documentation/process/license-rules.rst
mandates C-like comments (opposed to C source files where
C++
Abhishek Goel's on June 17, 2019 7:56 pm:
> Currently, the cpuidle governors determine what idle state a idling CPU
> should enter into based on heuristics that depend on the idle history on
> that CPU. Given that no predictive heuristic is perfect, there are cases
> where the governor predicts a
Hi Greg,
please take this cleanup patch.
It's been on the list but somehow fell through the cracks.
Thanks,
Moritz
Enrico Weigelt (1):
drivers: fpga: Kconfig: pedantic cleanups
drivers/fpga/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.22.0
From: Enrico Weigelt
Formatting of Kconfig files doesn't look so pretty, so just
take damp cloth and clean it up.
Signed-off-by: Enrico Weigelt
Signed-off-by: Moritz Fischer
---
drivers/fpga/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Memory hot remove uses get_nid_for_pfn() while tearing down linked sysfs
entries between memory block and node. It first checks pfn validity with
pfn_valid_within() before fetching nid. With CONFIG_HOLES_IN_ZONE config
(arm64 has this enabled) pfn_valid_within() calls pfn_valid().
pfn_valid() is
The arch code for hot-remove must tear down portions of the linear map and
vmemmap corresponding to memory being removed. In both cases the page
tables mapping these regions must be freed, and when sparse vmemmap is in
use the memory backing the vmemmap must also be freed.
This patch adds a new
The arm64 page table dump code can race with concurrent modification of the
kernel page tables. When a leaf entries are modified concurrently, the dump
code may log stale or inconsistent information for a VA range, but this is
otherwise not harmful.
When intermediate levels of table are freed,
This series enables memory hot remove on arm64 after fixing a memblock
removal ordering problem in generic try_remove_memory() and a possible
arm64 platform specific kernel page table race condition. This series
is based on linux-next (next-20190613).
Concurrent vmalloc() and hot-remove conflict:
On Wed, Jun 19, 2019 at 1:02 PM Masahiro Yamada
wrote:
>
> Hi.
>
>
> On Wed, Jun 19, 2019 at 12:23 PM Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the net-next tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from
Hi.
On Wed, Jun 19, 2019 at 12:23 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from usr/include/linux/tc_act/tc_ctinfo.hdrtest.c:1:
>
On Mon, Jun 17, 2019 at 6:42 PM Wei Yang wrote:
>
> On Wed, Jun 05, 2019 at 02:58:04PM -0700, Dan Williams wrote:
> >Sub-section hotplug support reduces the unit of operation of hotplug
> >from section-sized-units (PAGES_PER_SECTION) to sub-section-sized units
> >(PAGES_PER_SUBSECTION). Teach
Marcos,
> WWID composed from VPD data from device, specifically page 0x83. So,
> when a device does not have VPD support, for example USB storage
> devices where VPD is specifically disabled, a read into device>/device/wwid file will always return ENXIO. To avoid this,
> change the
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from usr/include/linux/tc_act/tc_ctinfo.hdrtest.c:1:
./usr/include/linux/tc_act/tc_ctinfo.h:30:21: error: implicit declaration of
function 'BIT'
Marcos,
> Currently, all USB devices skip VPD pages, even when the device
> supports them (SPC-3 and later), but some of them support VPD, like
> Cruzer Blade.
What's your confidence level wrt. all Cruzer Blades handling this
correctly? How many devices have you tested this change with?
--
On Mon, Jun 17, 2019 at 3:32 PM Dan Williams wrote:
>
> On Mon, Jun 17, 2019 at 3:22 PM Wei Yang wrote:
> >
> > On Wed, Jun 05, 2019 at 02:57:59PM -0700, Dan Williams wrote:
> > >Prepare for hot{plug,remove} of sub-ranges of a section by tracking a
> > >sub-section active bitmask, each bit
Arnd,
> Move the common support outside of the SCSI_LOWLEVEL section.
> Alternatively, we could move all of SCSI_LOWLEVEL_PCMCIA into
> SCSI_LOWLEVEL. This would be more sensible, but might cause surprises
> for users that have SCSI_LOWLEVEL disabled.
It seems messy to me that PCMCIA lives
On Tue, Jun 18, 2019 at 05:43:04PM -0400, Qian Cai wrote:
> Booting linux-next on both arm64 and powerpc triggers SLUB_DEBUG errors
> below. Reverted the whole series “mm: reparent slab memory on cgroup removal”
> [1] fixed the issue.
Hi Qian!
Thank you for the report!
Didn't you try to
On Wed, Jun 19, 2019 at 05:36:14AM +0800, Voon Weifeng wrote:
Hi Voon
> +static int est_poll_srwo(void *ioaddr)
> +{
> + /* Poll until the EST GCL Control[SRWO] bit clears.
> + * Total wait = 12 x 50ms ~= 0.6s.
> + */
> + unsigned int retries = 12;
> + unsigned int value;
>
On 6/17/19 3:55 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
Xenhost type xenhost_r0 does not support standard GNTTABOP_map_grant_ref
semantics (map a gref onto a specified host_addr). That's because
since the hypervisor is local (same address space as the caller of
On 6/17/19 3:14 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
For the most part, we now pass xenhost_t * as a parameter.
Co-developed-by: Joao Martins
Signed-off-by: Ankur Arora
I don't see how this can be a patch on its own.
Yes, the reason this was separate was that
On 6/17/19 3:07 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
Mechanical changes, now most of these calls take xenhost_t *
as parameter.
Co-developed-by: Joao Martins
Signed-off-by: Ankur Arora
---
drivers/xen/cpu_hotplug.c | 14 ++---
drivers/xen/gntalloc.c
Lee,
> New Qualcomm AArch64 based laptops are now available which use UFS
> as their primary data storage medium. These devices are supplied
> with ACPI support out of the box. This patch ensures the Qualcomm
> UFS driver will be bound when the "QCOM24A5" H/W device is
> advertised as
Frederic Weisbecker's on June 18, 2019 5:05 am:
> On Mon, Jun 17, 2019 at 05:59:31PM +0200, Peter Zijlstra wrote:
>> On Mon, Jun 10, 2019 at 05:24:32PM +1000, Nicholas Piggin wrote:
>> > Nicholas Piggin's on June 1, 2019 9:39 pm:
>> > > With the change to allow the boot CPU0 to be isolated, it is
Gustavo,
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct MR_PD_CFG_SEQ_NUM_SYNC {
> ...
> struct
Finn,
> Among other improvements, this patch series fixes a data corruption bug
> in the mac_scsi driver and a bug in the EH abort routine in the core
> 5380 driver.
>
> For consistency I have ignored certain checkpatch.pl complaints about
> the indentation in mac_scsi.c. The remaining
On 6/17/19 2:50 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
As part of xenbus init, both frontend, backend interfaces need to talk
on the correct xenbus. This might be a local xenstore (backend) or might
be a XS_PV/XS_HVM interface (frontend) which needs to talk over
From: Nathan Huckleberry
Date: Tue, 18 Jun 2019 09:09:10 -0700
> + ddebugfs_create_file("pmap", 0444, prs_entry_dir, entry,
drivers/net/ethernet/marvell/mvpp2/mvpp2_debugfs.c: In function
‘mvpp2_dbgfs_prs_entry_init’:
drivers/net/ethernet/marvell/mvpp2/mvpp2_debugfs.c:569:2: error:
From: Colin King
Date: Tue, 18 Jun 2019 16:15:10 +0100
> From: Colin Ian King
>
> Function mlx5_devlink_alloc is missing a void argument, add it
> to clean up the non-ANSI function declaration.
>
> Signed-off-by: Colin Ian King
Applied.
this patch fixes below issue reported by checkpatch.pl
CHECK: Lines should not end with a '('
CHECK: Lines should not end with a '('
Signed-off-by: Hariprasad Kelam
---
drivers/staging/rtl8723bs/hal/odm_RegConfig8723B.h | 61 ++
1 file changed, 28 insertions(+), 33
On Tue, 18 Jun 2019 17:11:15 -0400
Steven Rostedt wrote:
> On Tue, 18 Jun 2019 12:23:22 -0400
> Steven Rostedt wrote:
>
> > > Oops, good catch!
> > > This part is related to caller (ftrace/perf) so should be more careful.
> > > Usually, kprobe enablement should not fail. If one of them has
> >
On 2019/6/18 21:48, Jessica Yu wrote:
+++ Yang Yingliang [17/06/19 14:59 +0800]:
When loading a module with rodata=n, it causes an executing
NX-protected page BUG.
[ 32.379191] kernel tried to execute NX-protected page - exploit
attempt? (uid: 0)
[ 32.382917] BUG: unable to handle page
From: Maxime Chevallier
Date: Tue, 18 Jun 2019 16:55:15 +0200
> The PPv2 classifier can perform flow steering based on keys extracted
> from the VLAN tag. This series adds support for using the vlan id and
> the vlan prio as keys, using the ethtool interface.
>
> Patch 1 is a preparatory patch
On 6/17/19 2:36 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
Largely mechanical changes: the exported grant table symbols now take
xenhost_t * as a parameter. Also, move the grant table global state
inside xenhost_t.
If there's more than one xenhost, then initialize both.
On 6/17/19 2:28 AM, Juergen Gross wrote:
On 09.05.19 19:25, Ankur Arora wrote:
Xen ballooning uses hollow struct pages (with the underlying GFNs being
populated/unpopulated via hypercalls) which are used by the grant logic
to map grants from other domains.
This patch allows the default
Subject/Topic: Turritopsis Dohrnii Teo En Ming’s Infocomm Technology (ICT)
Skillset (Nov 2017 to Jun 2019)
This list is prepared on 19th Jun 2019 Wednesday 10:14 AM Singapore Time.
This list is NOT exhaustive and could be incomplete. More ICT skills will be
added in the future.
Section A:
From: Anson Huang
This patch adds the soc & board binding for i.MX8MQ.
Signed-off-by: Anson Huang
Reviewed-by: Rob Herring
---
No changes.
---
Documentation/devicetree/bindings/arm/fsl.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git
From: Anson Huang
The i.MX8M Nano Media Applications Processor is a new SoC of the i.MX8M
family, it is a 14nm FinFET product of the growing mScale family targeting
the consumer market. It is built in Samsung 14LPP to achieve both high
performance and low power consumption and relies on a
From: Anson Huang
This patch adds basic i.MM8MN DDR4 EVK board support.
Signed-off-by: Anson Huang
---
No change.
---
arch/arm64/boot/dts/freescale/Makefile| 1 +
arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts | 221 ++
2 files changed, 222 insertions(+)
From: Anson Huang
This patch adds the soc & board binding for i.MX8MN.
Signed-off-by: Anson Huang
Reviewed-by: Rob Herring
---
No change.
---
Documentation/devicetree/bindings/arm/fsl.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Tue, Jun 18, 2019 at 02:56:09PM -0700, Dan Williams wrote:
>On Sun, Jun 16, 2019 at 6:11 AM Wei Yang wrote:
>>
>> On Wed, Jun 05, 2019 at 02:57:54PM -0700, Dan Williams wrote:
>> >Towards enabling memory hotplug to track partial population of a
>> >section, introduce 'struct
On Fri, Jun 07, 2019 at 03:27:01PM +0200, Paolo Bonzini wrote:
> On 06/06/19 17:28, Yang Weijiang wrote:
> > EPT-Based Sub-Page write Protection(SPP)is a HW capability which
> > allows Virtual Machine Monitor(VMM) to specify write-permission for
> > guest physical memory at a sub-page(128 byte)
From: Yang Weijiang
Sub-Page Permission(SPP) is to protect finer granularity subpages
(128Byte each) within a 4KB page.
There're three specific ioctls for the feature in KVM:
KVM_INIT_SPP - initialize SPP runtime environment
KVM_SUBPAGES_SET_ACCESS - set SPP protection for guest page
From: Yang Weijiang
Sub-Page Permission(SPP) is to protect finer granularity subpages
(128Byte each) within a 4KB page. It's not enabled in KVM by default,
the test first initializes the SPP runtime environment with
KVM_INIT_SPP ioctl, then sets protection with KVM_SUBPAGES_SET_ACCESS
for the
From: Yash Shah
Date: Tue, 18 Jun 2019 13:26:06 +0530
> On FU540, the management IP block is tightly coupled with the Cadence
> MACB IP block. It manages many of the boundary signals from the MACB IP
> This patchset controls the tx_clk input signal to the MACB IP. It
> switches between the local
On Tue, Jun 18, 2019 at 4:22 PM Matthias Kaehlcke wrote:
>
> On Tue, Jun 18, 2019 at 04:04:20PM -0700, Nathan Chancellor wrote:
> > On Tue, Jun 18, 2019 at 02:14:40PM -0700, Matthias Kaehlcke wrote:
> > > empty_child_inc/dec() use the ternary operator for conditional
> > > operations. The
This patch is a cleanup which replaces rtw_malloc(wep_total_len) with
kzalloc() and removes the memset().
The rtw_malloc() does GFP_ATOMIC allocations when in_atomic() is true.
But as the comments for in_atomic() describe, the in_atomic() check
should not be used in driver code. The in_atomic()
On Tue, Jun 18, 2019 at 09:08:59PM -0400, Martin K. Petersen wrote:
>
> Branden,
>
> > Adding functionality to allow the SCSI queue depth to be changed, by
> > utilizing the "scsi_change_queue_depth" function.
>
> Applied to 5.3/scsi-queue. Please run checkpatch before submission. I
> fixed it
From: Xue Chaojing
Date: Tue, 18 Jun 2019 06:20:50 +
> This series add rss support for HINIC driver and implement the ethtool
> interface related to rss parameter configuration. user can use ethtool
> configure rss parameters or show rss parameters.
Series applied, thanks.
>-Original Message-
>From: Shawn Guo
>Sent: 2019年6月18日 21:13
>To: Peng Ma
>Cc: vk...@kernel.org; robh...@kernel.org; mark.rutl...@arm.com; Leo Li
>; dan.j.willi...@intel.com; dmaeng...@vger.kernel.org;
>devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
Martin,
On 19/06/19 12:47 PM, Martin K. Petersen wrote:
Michael,
No matter - patch applied cleanly to what I'm running on my Falcon,
and works just fine for now (stresstest will take a few hours to
complete). And that'll thoroughly exercise the reselection code path,
from what we've seen
Ondrej,
> Host reset oopses because it calls wd719x_chip_init, which calls
> request_firmware, under a spinlock. Stop the RISC first, then flush
> active SCBs under a spinlock. Finally call wd719x_chip_init unlocked.
Applied to 5.3/scsi-queue. Thank you!
--
Martin K. Petersen Oracle
Hi Linus,
Can you please pull the following bug fixes for apparmor
Thanks!
- John
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
From: Sunil Muthuswamy
Date: Mon, 17 Jun 2019 19:26:25 +
> Currently, hvsock can enter into a state where epoll_wait on EPOLLOUT will
> not return even when the hvsock socket is writable, under some race
> condition. This can happen under the following sequence:
...
> Now, the EPOLLOUT will
Cleaned Up code to fix brace style issues reported by checkpatch:
-space required before the open brace '{'
-Unbalanced braces around if/else statements
Signed-off-by: Shobhit Kukreti
---
drivers/staging/rtl8723bs/hal/hal_btcoex.c | 25 +++--
1 file changed, 11
From: Fred Klassen
Date: Mon, 17 Jun 2019 12:05:07 -0700
> Fixes an issue where TX Timestamps are not arriving on the error queue
> when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING.
> This can be illustrated with an updated updgso_bench_tx program which
> includes the '-T'
Without this, rcu_note_context_switch() will complain if an RCU read
lock is held when migrate_enable() calls stop_one_cpu().
Signed-off-by: Scott Wood
---
include/linux/sched.h| 4 ++--
kernel/rcu/tree_plugin.h | 2 +-
kernel/sched/core.c | 2 ++
3 files changed, 5 insertions(+), 3
A plain local_bh_disable() is documented as creating an RCU critical
section, and (at least) rcutorture expects this to be the case. However,
in_softirq() doesn't block a grace period on PREEMPT_RT, since RCU checks
preempt_count() directly. Even if RCU were changed to check
in_softirq(), that
[Note: Just before posting this I noticed that the invoke_rcu_core stuff
is part of the latest RCU pull request, and it has a patch that
addresses this in a more complicated way that appears to deal with the
bare irq-disabled sequence as well.
Assuming we need/want to support such sequences,
With these patches, rcutorture mostly works on PREEMPT_RT_FULL. I still
once in a while get forward progress complaints (particularly,
rcu_torture_fwd_prog_cr) when a grace period is held up for a few seconds
after which point so many callbacks have been enqueued that even making
reasonable
rcutorture was generating some nesting scenarios that are not
reasonable. Constrain the state selection to avoid them.
Example #1:
1. preempt_disable()
2. local_bh_disable()
3. preempt_enable()
4. local_bh_enable()
On PREEMPT_RT, BH disabling takes a local lock only when called in
non-atomic
Removing comparisons to True/False in if statements.
Checkpatch reported:
CHECK: Using comparison to true is error prone
Signed-off-by: Shobhit Kukreti
---
drivers/staging/rtl8723bs/hal/HalBtc8723b1Ant.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Quoting Dmitry Osipenko (2019-06-16 16:35:42)
> A proper External Memory Controller clock rounding and parent selection
> functionality is required by the EMC drivers. It is not available using
> the generic clock implementation, hence add a custom one.
Why isn't it available? Please add this
Quoting Thierry Reding (2019-06-18 05:21:08)
> On Mon, Jun 17, 2019 at 02:35:42AM +0300, Dmitry Osipenko wrote:
> > A proper External Memory Controller clock rounding and parent selection
> > functionality is required by the EMC drivers. It is not available using
> > the generic clock
On Tue, 18 Jun 2019 12:23:22 -0400
Steven Rostedt wrote:
> On Wed, 19 Jun 2019 01:14:09 +0900
> Masami Hiramatsu wrote:
>
> > On Mon, 17 Jun 2019 21:56:43 -0400
> > Steven Rostedt wrote:
> >
>
> > > > +static nokprobe_inline struct trace_kprobe *
> > > >
Christophe,
> Use 'kasprintf()' instead of:
>- snprintf(NULL, 0...
>- kmalloc(...
>- snprintf(...
>
> This is less verbose and saves 7 bytes (i.e. the space for '/(null)') if
> 'udev->dev_config' is NULL.
Applied to 5.3/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux
Branden,
> Adding functionality to allow the SCSI queue depth to be changed, by
> utilizing the "scsi_change_queue_depth" function.
Applied to 5.3/scsi-queue. Please run checkpatch before submission. I
fixed it up this time.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Hi, Shawn
> -Original Message-
> From: Shawn Guo
> Sent: Tuesday, June 18, 2019 8:59 PM
> To: Anson Huang
> Cc: s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> Leonard Crestez ; viresh.ku...@linaro.org;
> Abel Vesa ; linux-arm-ker...@lists.infradead.org;
>
From: Anson Huang
This patch adds i.MX8MN SoC driver support:
root@imx8mnevk:~# cat /sys/devices/soc0/family
Freescale i.MX
root@imx8mnevk:~# cat /sys/devices/soc0/machine
NXP i.MX8MNano DDR4 EVK board
root@imx8mnevk:~# cat /sys/devices/soc0/soc_id
i.MX8MN
root@imx8mnevk:~# cat
1 - 100 of 976 matches
Mail list logo
