On Mon, 2019-06-10 at 13:44 -0500, Larry Finger wrote:
> On 6/7/19 11:21 PM, Benjamin Herrenschmidt wrote:
> >
> > > Please try the attached patch. I'm not really pleased with it and I will
> > > continue to determine why the fallback to a 30-bit mask fails, but at
> > > least this
> > > one
Hi Daniel,
On Mon, Jun 10, 2019 at 10:16:09PM +0800, daniel.bal...@nxp.com wrote:
> From: Daniel Baluta
>
> TX doorbell with ACK will allow us to push the doorbell ring button
> (trigger GIR) and also will allow us to handle the response from DSP.
>
> DSP firmware found on i.MX8 boards
On Mon, 2019-06-10 at 09:20 +0100, Marc Zyngier wrote:
> Hi Zeev,
>
> On 07/06/2019 00:17, Zeev Zilberman wrote:
> > The patch adds support for Amazon Graviton custom variant of GICv2m, where
> > hw irq is encoded using the MSI message address, as opposed to standard
> > GICv2m, where hw irq is
This patch initializes the MMU structures for the kernel context. This is
needed before we can configure mappings for the kernel context.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/context.c | 7 +++
drivers/misc/habanalabs/mmu.c | 10 ++
2 files changed, 13
This patch initializes the MMU S/W structures before the VM S/W
structures, instead of doing that as part of the VM S/W initialization.
This is done because we need to configure some MMU mappings for the kernel
context, before the VM is initialized. The VM initialization can't be
moved earlier
This patch changes the order of H/W IP initializations. The MMU needs to
be initialized before the device CPU queues, because the CPU will go
through the ASIC MMU in order to reach the host memory (where the queues
are located).
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/asid.c
On Sat, 2019-06-08 at 11:05 +0200, Borislav Petkov wrote:
> On Sat, Jun 08, 2019 at 10:16:11AM +1000, Benjamin Herrenschmidt wrote:
> > Those IP blocks don't need any SW coordination at runtime. The drivers
> > don't share data nor communicate with each other. There is absolultely
> > no reason to
Add nxp sa56004 chip node for temperature monitor.
Signed-off-by: Yuantian Tang
---
v3:
- sort the node in i2c address
v2:
- change the node name and add vcc-supply
arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 15 +++
This patch configures the Goya CPU to actually go through the MMU for
translation. The configuration is done after the configuration of the
relevant MMU mappings.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c | 23 ---
1 file changed, 20 insertions(+), 3
This patch adds the necessary MMU mappings for the Goya CPU to access the
device DRAM and the host memory.
The first 256MB of the device DRAM is being mapped. That's where the F/W
is running.
The 2MB area located on the host memory for the purpose of communication
between the driver and the
This patch removes the non-standard DMA mask setting for Goya. Now that
the device CPU goes through the MMU, we are not limited to allocating the
CPU accessible memory area in the address space of under 39 bits.
Therefore, we don't need to set the DMA masking twice during
initialization, a
This patch checks if an MMU mapping is erroneous in that the physical
address that is being mapped is NOT divisible by the page size.
If that thing happens, then the H/W will issue a transaction which will be
translated to a wrong address, because part of the address will not be
taken (the
This patch enables support in the driver for 64-bit DMA mask when running
in a POWER9 machine.
POWER9 supports either 32-bit or 64-bit DMA mask. However, our ASICs
support 48-bit DMA mask. To support 64-bit, the driver needs to add a
special configuration to the ASIC's PCIe controller.
The
This patch-set changes the way the Goya internal CPU access memory on the
Host machine. This is needed to prevent the non-standard way the driver
used the PCI DMA set mask kernel API so far.
The DMA set mask should be called only once at the start of the driver.
This is because changing the DMA
Hi,
On 05/24/19 at 03:38pm, Baoquan He wrote:
>
Ping.
Can anyone help do further reviewing on this patchset? Or consider
merging since people have ack-ed?
Thanks
Baoquan
> The v4 cover letter tells the background about this adding, paste the
> link here for reference:
>
On Thu, 2019-06-06 at 09:31 +0300, Andy Shevchenko wrote:
> On Thu, Jun 6, 2019 at 5:53 AM Chunfeng Yun wrote:
> >
> > On Wed, 2019-06-05 at 11:45 +0300, Andy Shevchenko wrote:
> > > On Wed, May 29, 2019 at 10:44 AM Chunfeng Yun
> > > wrote:
> > > >
> > > > Due to the requirement of
On Thu, Jun 6, 2019 at 8:08 PM Valdis Klētnieks wrote:
>
> Compiling kernel/bpf/core.c with W=1 causes a flood of warnings:
>
> kernel/bpf/core.c:1198:65: warning: initialized field overwritten
> [-Woverride-init]
> 1198 | #define BPF_INSN_3_TBL(x, y, z) [BPF_##x | BPF_##y | BPF_##z] = true
>
Adds a PWM driver for PWM chip present in SiFive's HiFive Unleashed SoC.
Signed-off-by: Wesley W. Terpstra
[Atish: Various fixes and code cleanup]
Signed-off-by: Atish Patra
Signed-off-by: Yash Shah
---
drivers/pwm/Kconfig | 11 ++
drivers/pwm/Makefile | 1 +
DT documentation for PWM controller added.
Signed-off-by: Wesley W. Terpstra
[Atish: Compatible string update]
Signed-off-by: Atish Patra
Signed-off-by: Yash Shah
Reviewed-by: Rob Herring
---
.../devicetree/bindings/pwm/pwm-sifive.txt | 33 ++
1 file changed, 33
This patch series adds a PWM driver and DT documentation
for HiFive Unleashed board. The patches are mostly based on
Wesley's patch.
This patchset is based on Linux v5.2-rc1 and tested on HiFive Unleashed
board with additional board related patches needed for testing can be
found at
On Sat, Jun 8, 2019 at 2:46 AM Stephen Boyd wrote:
>
> Quoting Chen-Yu Tsai (2019-06-03 09:38:22)
> > Hi Stephen,
> >
> > On Mon, May 20, 2019 at 5:03 PM Maxime Ripard
> > wrote:
> > >
> > > On Mon, May 20, 2019 at 04:03:56PM +0800, Chen-Yu Tsai wrote:
> > > > From: Chen-Yu Tsai
> > > >
> > >
Hi all,
Today's linux-next merge of the clockevents tree got a conflict in:
drivers/clocksource/timer-tegra.c
between commit:
9c92ab619141 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule
282")
from Linus' tree and commit:
75e9f7c6dca8 ("clocksource/drivers/tegra: Use
Hi Paul,
Le 08/06/2019 à 11:57, Paul Cercueil a écrit :
Hi Christophe,
Le sam. 8 juin 2019 à 9:51, Christophe Leroy a
écrit :
Hi Paul,
Le 07/06/2019 à 18:24, Paul Cercueil a écrit :
This allows the probe function to be dropped after the kernel finished
its initialization, in the case
On 06/11/2019 10:16 AM, Christophe Leroy wrote:
>
>
> Le 10/06/2019 à 04:39, Anshuman Khandual a écrit :
>>
>>
>> On 06/07/2019 09:01 PM, Christophe Leroy wrote:
>>>
>>>
>>> Le 07/06/2019 à 12:34, Anshuman Khandual a écrit :
Very similar definitions for notify_page_fault() are being used
On 06/10/2019 08:57 PM, Leonardo Bras wrote:
> On Mon, 2019-06-10 at 08:09 +0530, Anshuman Khandual wrote:
+/*
+ * To be potentially processing a kprobe fault and to be allowed
+ * to call kprobe_running(), we have to be non-preemptible.
+ */
+if
On Fri, Jun 07, 2019 at 06:37:23PM +0200, Borislav Petkov wrote:
> On Fri, Jun 07, 2019 at 02:49:42PM +, Ghannam, Yazen wrote:
> > Would you mind if the function name stayed the same? The reason is
> > that MCA_CTL is written here, which is the "init" part, and MCA_STATUS
> > is cleared.
> >
>
Hello dear,
We are in the market for your products after meeting at your stand during last
expo.
Please kindly send us your latest catalog and price list so as to start a new
project/order as promised during the exhibition.
I would appreciate your response about the above details required
Hi Finn,
IIRC I'd tested that change as well - didn't change broken target
behaviour but no regressions in other respects. Add my tested-by if needed.
Cheers,
Michael
Am 09.06.2019 um 13:19 schrieb Finn Thain:
The reselection interrupt gets disabled during selection and must be
Hi Finn,
Thanks - can't test this on my hardware but looks good to me.
Cheers,
Michael
Am 11.06.2019 um 15:25 schrieb Finn Thain:
My understanding is that support for chained scatterlists is to
become mandatory for LLDs.
Cc: Michael Schmitz
Signed-off-by: Finn Thain
---
Hi all,
After merging the tpmdd tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/firmware/efi/tpm.c: In function 'efi_tpm_eventlog_init':
drivers/firmware/efi/tpm.c:80:10: warning: passing argument 1 of
'tpm2_calc_event_log_size' makes pointer from integer
On Mon, Jun 10, 2019 at 3:17 PM Kent Overstreet
wrote:
>
>
> > Why does the regular page lock (at a finer granularity) not suffice?
>
> Because the lock needs to prevent pages from being _added_ to the page cache -
> to do it with a page granularity lock it'd have to be part of the radix tree,
From: Darrick J. Wong
Create a generic checking function for the incoming FS_IOC_FSSETXATTR
fsxattr values so that we can standardize some of the implementation
behaviors.
Signed-off-by: Darrick J. Wong
---
fs/btrfs/ioctl.c | 21 +---
fs/ext4/ioctl.c| 27
Hi all,
The chattr(1) manpage has this to say about the immutable bit that
system administrators can set on files:
"A file with the 'i' attribute cannot be modified: it cannot be deleted
or renamed, no link can be created to this file, most of the file's
metadata can not be modified, and the
Le 10/06/2019 à 04:39, Anshuman Khandual a écrit :
On 06/07/2019 09:01 PM, Christophe Leroy wrote:
Le 07/06/2019 à 12:34, Anshuman Khandual a écrit :
Very similar definitions for notify_page_fault() are being used by multiple
architectures duplicating much of the same code. This
On 11-06-19, 03:04, Robin Gong wrote:
> On 2019-06-10 at 12:55 +, Vinod Koul wrote:
> > On 10-06-19, 16:17, yibin.g...@nxp.com wrote:
> > >
> > > From: Robin Gong
> > >
> > > For the compatibility of NXP internal legacy kernel before 4.19
> > > which
> > > is based on uart ram script and
Hi Rob,
On 10/06/19 11:13 PM, Rob Herring wrote:
> On Tue, Jun 4, 2019 at 7:19 AM Kishon Vijay Abraham I wrote:
>>
>> Export of_platform_device_create_pdata() to be used by drivers to
>> create child devices with the given platform data. This can be used
>> by platform specific driver to send
On Mon, Jun 10, 2019 at 6:11 PM Dave Chinner wrote:
>
> Please, no, let's not make the rwsems even more fragile than they
> already are. I'm tired of the ongoing XFS customer escalations that
> end up being root caused to yet another rwsem memory barrier bug.
>
> > Have you talked to Waiman Long
+
Hi Peter, Jen,
As we are not taking pi_lock here , is there possibility of same task dead
call comes as this point of time for current thread, bcoz of which we have
seen earlier issue after this commit 0619317ff8ba
[T114538] do_task_dead+0xf0/0xf8
[T114538] do_exit+0xd5c/0x10fc
On Mon, Jun 10, 2019 at 09:17:37PM -0400, Kent Overstreet wrote:
> On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote:
> > On Mon, Jun 10, 2019 at 9:14 AM Kent Overstreet
> > wrote:
> > That lock is somewhat questionable in the first place, and no, we
> > don't do those hacky
On Mon, Jun 10, 2019 at 10:16:08PM +0800, daniel.bal...@nxp.com wrote:
> From: Daniel Baluta
>
> GIEn is enabled at startup for RX doorbell mailboxes so
> we need to clear the bit at shutdown in order to avoid
> leaving the interrupt line enabled.
>
> Signed-off-by: Daniel Baluta
Please send
On 2019/6/11 上午11:23, Hui Wang wrote:
On 2019/6/11 上午11:05, Xiaoxiao Liu wrote:
Hi Pali,
I discussed with our FW team about this problem.
We think the V8 method means a touchpad feature and does not fit the
CS19 trackpoint device.
CS19 TrackPoint needn't use any Absolute (Raw) mode and is
Hi all,
Today's linux-next merge of the mfd tree got a conflict in:
include/linux/mfd/cros_ec_commands.h
between commit:
9c92ab619141 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule
282")
from Linus' tree and commit:
2769bd79a915 ("mfd: cros_ec: Update license term")
Hi Alex,
On 2019/3/29 23:20, Alex Kogan wrote:
> In CNA, spinning threads are organized in two queues, a main queue for
> threads running on the same node as the current lock holder, and a
> secondary queue for threads running on other nodes. At the unlock time,
> the lock holder scans the main
On Mon, Jun 10, 2019 at 03:47:54PM -0300, Arnaldo Carvalho de Melo wrote:
[...]
> > > I tested with the lastest perf/core branch which contains the patch:
> > > 'perf augmented_raw_syscalls: Tell which args are filenames and how
> > > many bytes to copy' and got the error as below:
> > >
> > >
On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote:
> I also get the feeling that the "intent" part of the six-locks could
> just be done as a slight extension of the rwsem, where an "intent" is
> the same as a write-lock, but without waiting for existing readers,
> and then the
Hello,
syzbot found the following crash on:
HEAD commit:d1fdb6d8 Linux 5.2-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b30acaa0
kernel config: https://syzkaller.appspot.com/x/.config?x=fa9f7e1b6a8bb586
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:d1fdb6d8 Linux 5.2-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=117e0f71a0
kernel config: https://syzkaller.appspot.com/x/.config?x=cb38d33cd06d8d48
dashboard link:
The dht11 driver uses a single gpio to make measurements. It was
using the older global gpio numberspace. The patch replaces the
old gpio api with the new gpio descriptor based api.
Removed header files "linux/gpio.h" and "linux/of_gpio.h"
Signed-off-by: Shobhit Kukreti
---
Powerpc hw triggers watchpoint before executing the instruction. To
make trigger-after-execute behavior, kernel emulates the instruction.
If the instruction is 'load something into non-volatile register',
exception handler should restore emulated register state while
returning back, otherwise
My understanding is that support for chained scatterlists is to
become mandatory for LLDs.
Cc: Michael Schmitz
Signed-off-by: Finn Thain
---
drivers/scsi/NCR5380.c | 41 ++---
1 file changed, 18 insertions(+), 23 deletions(-)
diff --git
On 2019/6/11 上午11:05, Xiaoxiao Liu wrote:
Hi Pali,
I discussed with our FW team about this problem.
We think the V8 method means a touchpad feature and does not fit the CS19
trackpoint device.
CS19 TrackPoint needn't use any Absolute (Raw) mode and is usually use
standard mouse data.
CS19
Hi Alex,
> -Original Message-
> From: Cornelia Huck
> Sent: Tuesday, June 4, 2019 11:18 AM
> To: Parav Pandit
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> kwankh...@nvidia.com; alex.william...@redhat.com; c...@nvidia.com
> Subject: Re: [PATCHv6 3/3] vfio/mdev: Synchronize
Hi Pali,
I discussed with our FW team about this problem.
We think the V8 method means a touchpad feature and does not fit the CS19
trackpoint device.
CS19 TrackPoint needn't use any Absolute (Raw) mode and is usually use
standard mouse data.
CS19 TrackPoint device is a completely different
On Mon, Jun 10, 2019 at 04:20:28PM -0400, Paul Moore wrote:
> On Fri, Jun 7, 2019 at 4:41 AM Ondrej Mosnacek wrote:
> >
> > On Thu, Jun 6, 2019 at 10:55 AM Gen Zhang wrote:
> > > In selinux_sb_eat_lsm_opts(), 'arg' is allocated by kmemdup_nul(). It
> > > returns NULL when fails. So 'arg' should
On Mon, Jun 10, 2019 at 03:31:50PM -0400, Paul Moore wrote:
> On Fri, Jun 7, 2019 at 8:11 AM Gen Zhang wrote:
> >
> > On Fri, Jun 07, 2019 at 10:39:05AM +0200, Ondrej Mosnacek wrote:
> > > On Thu, Jun 6, 2019 at 11:23 AM Gen Zhang
> > > wrote:
> > > > In selinux_add_mnt_opt(), 'val' is
On 2019-06-10 at 12:55 +, Vinod Koul wrote:
> On 10-06-19, 16:17, yibin.g...@nxp.com wrote:
> >
> > From: Robin Gong
> >
> > For the compatibility of NXP internal legacy kernel before 4.19
> > which
> > is based on uart ram script and upstreaming kernel based on uart
> > rom
> > script, add
'perf version' on powerpc segfaults when used with non-supported
option:
# perf version -a
Segmentation fault (core dumped)
Fix this.
Signed-off-by: Ravi Bangoria
Reviewed-by: Kamalesh babulal
Tested-by: Mamatha Inamdar
---
tools/perf/builtin-version.c | 1 +
1 file changed, 1
On 2019/6/11 10:42, Gao Xiang wrote:
> There are some backward incompatible features pending
> for months, mainly due to on-disk format expensions.
>
> However, we should ensure that it cannot be mounted with
> old kernels. Otherwise, it will causes unexpected behaviors.
>
> Fixes: ba2b77a82022
Hi all,
Friendly ping...
On 2019/5/25 22:09, YueHaibing wrote:
> We should return 'retval' as the correct return value
> instead of always zero.
>
> Fixes: 74808f9115ce ("HID: logitech-dj: add support for non unifying
> receivers")
> Signed-off-by: YueHaibing
> ---
>
CHECK: spaces preferred around that '|' (ctx:VxV)
CHECK: spaces preferred around that '|' (ctx:VxV)
CHECK: spaces preferred around that '+' (ctx:VxV)
Signed-off-by: Hariprasad Kelam
---
drivers/staging/rtl8723bs/os_dep/rtw_proc.c | 24
1 file changed, 12 insertions(+),
This patch fixes below issues reported by checkpatch
CHECK: Comparison to NULL could be written "rtw_proc"
CHECK: Comparison to NULL could be written "!rtw_proc"
CHECK: Comparison to NULL could be written "!rtw_proc"
Signed-off-by: Hariprasad Kelam
---
Hi Rafael/Thomas,
On Mon, Jun 3, 2019 at 10:03 AM Pavankumar Kondeti
wrote:
>
> When "deep" suspend is enabled, all CPUs except the primary CPU
> are hotplugged out. Since CPU hotplug is a costly operation,
> check if we have to abort the suspend in between each CPU
> hotplug. This would improve
On 6/8/2019 7:41 PM, Jin, Yao wrote:
On 6/5/2019 7:44 PM, Jiri Olsa wrote:
On Mon, Jun 03, 2019 at 10:36:14PM +0800, Jin Yao wrote:
SNIP
diff --git a/tools/perf/util/sort.h b/tools/perf/util/sort.h
index 43623fa..d1641da 100644
--- a/tools/perf/util/sort.h
+++ b/tools/perf/util/sort.h
On Mon, Jun 10, 2019 at 03:48:24PM +0800, Hao Xu wrote:
> remove inb_p and outb_p to call readq/writeq directly.
>
> Signed-off-by: Hao Xu
> ---
> Changes in v2:
> - remove the macros inb_p/outb_p and use readq/writeq directly, per
>
On 6/10/19 8:46 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jun 10, 2019 at 12:15:17PM +0530, Anju T Sudhakar escreveu:
>> 'perf kvm record' uses 'cycles'(if the user did not specify any event) as
>> the default event to profile the guest.
>> This will not provide any proper samples from the
On 6/10/19 5:08 PM, Rob Herring wrote:
> On Thu, May 30, 2019 at 9:53 PM Alex Elder wrote:
>>
>> Add the binding definitions for the "qcom,ipa" device tree node.
>>
>> Signed-off-by: Alex Elder
>> ---
>> .../devicetree/bindings/net/qcom,ipa.yaml | 180 ++
>> 1 file changed,
Hi all,
Today's linux-next merge of the crypto tree got conflicts in:
drivers/crypto/vmx/aes.c
drivers/crypto/vmx/aes_cbc.c
drivers/crypto/vmx/aes_ctr.c
drivers/crypto/vmx/aes_xts.c
drivers/crypto/vmx/vmx.c
between commits:
64d85cc99980 ("treewide: Replace GPLv2
Hi, Stephen
> -Original Message-
> From: Stephen Boyd
> Sent: Monday, June 10, 2019 11:14 PM
> To: bjorn.anders...@linaro.org; catalin.mari...@arm.com;
> devicet...@vger.kernel.org; dingu...@kernel.org;
> enric.balle...@collabora.com; feste...@gmail.com;
> horms+rene...@verge.net.au;
From: Huang Ying
Via commit 4b3ef9daa4fc ("mm/swap: split swap cache into 64MB trunks") on,
after swapoff, the address_space associated with the swap device will be
freed. So swap_address_space() users which touch the address_space need
some kind of mechanism to prevent the address_space from
ocfs2 file system uses locking_state file under debugfs to dump
each ocfs2 file system's dlm lock resources, but the dlm lock
resources in memory are becoming more and more after the files
were touched by the user. it will become a bit difficult to analyze
these dlm lock resource records in
Add locking filter debugfs file, which is used to filter lock
resources dump from locking_state debugfs file.
We use d_filter_secs field to filter lock resources dump,
the default d_filter_secs(0) value filters nothing,
otherwise, only dump the last N seconds active lock resources.
This
ocfs2 file system uses locking_state file under debugfs to dump
each ocfs2 file system's dlm lock resources, but the users ever
encountered some hang(deadlock) problems in ocfs2 file system.
I'd like to add first lock wait time in locking_state file, which
can help the upper scripts detect these
> On Jun 10, 2019, at 6:45 PM, Wanpeng Li wrote:
>
> On Tue, 11 Jun 2019 at 09:11, Sean Christopherson
> wrote:
>> On Mon, Jun 10, 2019 at 04:34:20PM +0200, Radim Krčmář wrote:
>>> 2019-05-30 09:05+0800, Wanpeng Li:
The idea is from Xen, when sending a call-function IPI-many to vCPUs,
This patch add support for Fintek PCIE to 2 CAN controller support
Signed-off-by: Ji-Ze Hong (Peter Hong)
---
drivers/net/can/sja1000/Kconfig | 8 ++
drivers/net/can/sja1000/Makefile | 1 +
drivers/net/can/sja1000/f81601.c | 223 +++
3 files changed, 232
On Tue, 11 Jun 2019 at 09:11, Sean Christopherson
wrote:
>
> On Mon, Jun 10, 2019 at 04:34:20PM +0200, Radim Krčmář wrote:
> > 2019-05-30 09:05+0800, Wanpeng Li:
> > > The idea is from Xen, when sending a call-function IPI-many to vCPUs,
> > > yield if any of the IPI target vCPUs was preempted.
On Tue, 11 Jun 2019 at 09:21, Sean Christopherson
wrote:
>
> On Fri, May 31, 2019 at 02:40:13PM +0800, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > Advance lapic timer tries to hidden the hypervisor overhead between the
> > host emulated timer fires and the guest awares the timer is fired.
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
kernel/bpf/verifier.c
between commit:
983695fa6765 ("bpf: fix unconnected udp hooks")
from the net tree and commit:
5cf1e9145630 ("bpf: cgroup inet skb programs can return 0 to 3")
from the net-next tree.
I
Yes, This patch fixes the Oops.
xue
在 2019/6/11 8:45, dann frazier wrote:
On Mon, May 27, 2019 at 10:10:05PM +, Xue Chaojing wrote:
in set_rx_mode, __dev_mc_sync and netdev_for_each_mc_addr will
repeatedly set the multicast mac address. so we delete this loop.
fyi, I'm told this fixes
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
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/cmd.c
between commit:
6a6fabbfa3e8 ("net/mlx5: Update pci error handler entries and command
translation")
from the net tree and commit:
cd56f929e6a5 ("net/mlx5: E-Switch,
The variable 'status' in __packet_lookup_frame_in_block() is never used since
introduction in commit f6fb8f100b80 ("af-packet: TPACKET_V3 flexible buffer
implementation."), we can remove it.
Signed-off-by: Mao Wenan
---
v2: don't change parameter from 0 to TP_STATUS_KERNEL when calls
Christophe Leroy writes:
> On 06/03/2019 11:50 PM, Daniel Axtens wrote:
>> Christophe Leroy writes:
>>
>>> Hi,
>>>
>>> Ok, can you share your .config ?
>>
>> Sure! This one is with kasan off as the last build I did was testing to
>> see if the code reorgisation was the cause of the issues.
On Fri, May 31, 2019 at 02:40:13PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Advance lapic timer tries to hidden the hypervisor overhead between the
> host emulated timer fires and the guest awares the timer is fired. However,
> even though after more sustaining optimizations,
>
On Mon, Jun 10, 2019 at 10:46:35AM -1000, Linus Torvalds wrote:
> On Mon, Jun 10, 2019 at 9:14 AM Kent Overstreet
> wrote:
> >
> > So. Here's my bcachefs-for-review branch - this has the minimal set of
> > patches
> > outside of fs/bcachefs/. My master branch has some performance
> >
On Mon, 10 Jun 2019 14:11:57 -0700
Cong Wang wrote:
> On Sat, May 25, 2019 at 3:37 PM Steven Rostedt wrote:
> > Hi Cong,
> >
> > Thanks for sending these patches, but I just want to let you know that
> > it's currently a US holiday, and then afterward I'll be doing quite a
> > bit of traveling
On Mon, Jun 10, 2019 at 04:34:20PM +0200, Radim Krčmář wrote:
> 2019-05-30 09:05+0800, Wanpeng Li:
> > The idea is from Xen, when sending a call-function IPI-many to vCPUs,
> > yield if any of the IPI target vCPUs was preempted. 17% performance
> > increasement of ebizzy benchmark can be
On Mon, Jun 10, 2019 at 03:30:55PM -0700, Eric Biggers wrote:
> Any progress on this patch?
I have no had time yet; sorry. If anyone else would like to take a stab
at it, I'd appreciate it. :)
--
Kees Cook
On Tue, May 28, 2019 at 11:28:05AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:cd6c84d8 Linux 5.2-rc2
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=132bd44aa0
> kernel config:
On Mon, Jun 10, 2019 at 05:19:45PM -0700, Mike Kravetz wrote:
> On 6/10/19 1:18 AM, Naoya Horiguchi wrote:
> > The pass/fail of soft offline should be judged by checking whether the
> > raw error page was finally contained or not (i.e. the result of
> > set_hwpoison_free_buddy_page()), but current
"Huang, Ying" writes:
> Hi, Josef,
>
> kernel test robot writes:
>
>> Greeting,
>>
>> FYI, we noticed a -11.7% regression of aim7.jobs-per-min due to commit:
>>
>>
>> commit: c8eaeac7b734347c3afba7008b7af62f37b9c140 ("btrfs: reserve
>> delalloc metadata differently")
>>
On Mon, May 27, 2019 at 10:10:05PM +, Xue Chaojing wrote:
> in set_rx_mode, __dev_mc_sync and netdev_for_each_mc_addr will
> repeatedly set the multicast mac address. so we delete this loop.
fyi, I'm told this fixes the following Oops (in case it makes sense to
queue it for stable):
[
Hi Bartlomiej,
After merging the fbdev tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/video/fbdev/pvr2fb.c:726:12: warning: 'pvr2_get_param_val' defined but
not used [-Wunused-function]
static int pvr2_get_param_val(const struct pvr2_params *p, const char
Hi all,
Today's linux-next merge of the fbdev tree got a conflict in:
drivers/video/fbdev/mxsfb.c
between commit:
c942fddf8793 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule
157")
from Linus' tree and commit:
f225f1393f03 ("video: fbdev: mxsfb: Remove driver")
from
On Mon, Jun 10, 2019 at 5:31 PM Frank Lee wrote:
>
> On Tue, Jun 11, 2019 at 7:29 AM Vasily Khoruzhick wrote:
> >
> > On Sat, May 25, 2019 at 11:17 AM Yangtao Li wrote:
> > >
> > > This patch adds the support for allwinner thermal sensor, within
> > > allwinner SoC. It will register sensors for
On Tue, Jun 11, 2019 at 7:29 AM Vasily Khoruzhick wrote:
>
> On Sat, May 25, 2019 at 11:17 AM Yangtao Li wrote:
> >
> > This patch adds the support for allwinner thermal sensor, within
> > allwinner SoC. It will register sensors for thermal framework
> > and use device tree to bind cooling
Hi Wolfram,
After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/media/dvb-frontends/tua6100.c: In function 'tua6100_set_params':
drivers/media/dvb-frontends/tua6100.c:71: warning: "_P" redefined
#define _P 32
In file included from
On 6/10/19 1:18 AM, Naoya Horiguchi wrote:
> The pass/fail of soft offline should be judged by checking whether the
> raw error page was finally contained or not (i.e. the result of
> set_hwpoison_free_buddy_page()), but current code do not work like that.
> So this patch is suggesting to fix it.
From: Greg Hackmann
By traversing /proc/*/fd and /proc/*/map_files, processes with CAP_ADMIN
can get a lot of fine-grained data about how shmem buffers are shared
among processes. stat(2) on each entry gives the caller a unique
ID (st_ino), the buffer's size (st_size), and even the number of
syzbot has bisected this bug to:
commit 5ec8c48a6235175f7ff59ed1acbe91d4d0398026
Author: Thierry Reding
Date: Thu Jul 6 15:16:47 2017 +
Merge branch 'for-4.13/drivers' into for-next
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ef22daa0
start commit: d1fdb6d8
24.05.2019 20:23, Dmitry Osipenko пишет:
> Hello,
>
> This series introduces driver for the External Memory Controller (EMC)
> found on Tegra30 chips, it controls the external DRAM on the board. The
> purpose of this driver is to program memory timing for external memory on
> the EMC clock rate
1 - 100 of 863 matches
Mail list logo
