* Reshetova, Elena wrote:
> > * Reshetova, Elena wrote:
> >
> > > CONFIG_PAGE_TABLE_ISOLATION=n:
> > >
> > > base: Simple syscall: 0.0510 microseconds
> > > get_random_bytes(4096 bytes buffer): Simple syscall: 0.0597 microseconds
> > >
> > > So, pure speed
native_calibrate_tsc() had a data mapping Intel CPU families
and crystal clock speed, but hardcoded tables are not ideal, and this
approach was already problematic at least in the Skylake X case, as
seen in commit b51120309348 ("x86/tsc: Fix erroneous TSC rate on Skylake
Xeon").
By examining
This variable is a period unit (number of clock cycles per jiffy),
not a frequency (which is number of cycles per second).
Give it a more appropriate name.
Suggested-by: Ingo Molnar
Signed-off-by: Daniel Drake
---
arch/x86/include/asm/apic.h| 2 +-
arch/x86/kernel/apic/apic.c| 20
The APIC timer calibration (calibrate_APIC_timer()) can be skipped
in cases where we know the APIC timer frequency. On Intel SoCs,
we believe that the APIC is fed by the crystal clock; this would make
sense, and the crystal clock frequency has been verified against the
APIC timer calibration
When userspace opens a serial port for console, uart_port_startup()
is called. This function assigns the uport->cons->cflag value to
TTY->termios.c_cflag, then it is cleared to 0. When the user space
closes this serial port, the TTY structure will be released, and at
this time uport->cons->cflag
Hello,
syzbot found the following crash on:
HEAD commit:80f23212 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11ab8dd0a0
kernel config: https://syzkaller.appspot.com/x/.config?x=40a58b399941db7e
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
drivers/infiniband/core/umem.c
between commit:
db6c6774af0d ("RDMA/umem: Remove hugetlb flag")
from the rdma tree and commit:
c041ba1a3294 ("mm/gup: replace get_user_pages_longterm() with FOLL_LONGTERM")
from
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/parisc/mm/init.c
between commit:
98429dded340 ("parisc: Enable SPARSEMEM_VMEMMAP")
from the parisc-hd tree and commit:
2e5adbd9e97a ("initramfs: provide a generic free_initrd_mem implementation")
from
Merged into cifs-2.6.git for-next with minor cleanup. I also
(ironically) had to change the patch title since
checkpatch complained about mentioning "checkpatch" in the patch name.
Also FYI - since it didn't merge cleanly, I had to add one of the
changes manually as a distinct patch. See
-Original Message-
From: Sumit Batra
Sent: Thursday, May 9, 2019 10:06 AM
To: Chuanhua Han ; Sascha Hauer
Cc: shawn...@kernel.org; Leo Li ; robh...@kernel.org;
mark.rutl...@arm.com; linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
linux-arm-ker...@lists.infradead.org;
The pull request you sent on Wed, 08 May 2019 16:53:20 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide refs/heads/master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/89c3b37af87ec183b666d83428cb28cc421671a6
Thank you!
--
Deet-doot-dot, I am
This currently generates a warning:
drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr':
drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used
uninitialized in this function [-Wmaybe-uninitialized]
Though the code looks okay and shouldn't ever use the variable
On Tue, May 7, 2019 at 11:42 PM Ralph Campbell wrote:
>
>
> On 5/7/19 6:15 AM, Souptick Joarder wrote:
> > On Tue, May 7, 2019 at 5:00 AM wrote:
> >>
> >> From: Ralph Campbell
> >>
> >> The helper function hmm_vma_fault() calls hmm_range_register() but is
> >> missing a call to
Hi Sascha,
Please check my comment
-Original Message-
From: Chuanhua Han
Sent: Wednesday, May 8, 2019 5:05 PM
To: Sascha Hauer
Cc: shawn...@kernel.org; Leo Li ; robh...@kernel.org;
mark.rutl...@arm.com; linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
On 2019/5/9 3:52, Schmauss, Erik wrote:
>
>
>> -Original Message-
>> From: YueHaibing [mailto:yuehaib...@huawei.com]
>> Sent: Wednesday, May 8, 2019 8:07 AM
>> To: Moore, Robert ; Schmauss, Erik
>> ; Wysocki, Rafael J ;
>> l...@kernel.org
>> Cc: linux-kernel@vger.kernel.org;
On 08-05-19, 15:57, Pierre-Louis Bossart wrote:
>
>
> On 5/8/19 11:59 AM, Greg KH wrote:
> > On Wed, May 08, 2019 at 11:42:15AM -0500, Pierre-Louis Bossart wrote:
> > >
> > >
> > > On 5/8/19 4:16 AM, Greg KH wrote:
> > > > On Wed, May 08, 2019 at 01:16:06PM +0530, Vinod Koul wrote:
> > > > >
On 4/30/19 8:39 AM, Hans de Goede wrote:
>
> Hi,
>
> On 4/25/19 6:38 PM, Robert R. Howell wrote:
>> On 4/24/19 1:20 AM, Rafael J. Wysocki wrote:
>>
>>> On Tue, Apr 23, 2019 at 10:03 PM Robert R. Howell wrote:
On 4/23/19 2:07 AM, Rafael J. Wysocki wrote:
>
> On Sat, Apr 20,
Add multiple byte read-write support for slave mode.
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Srinath Mannam
---
drivers/i2c/busses/i2c-bcm-iproc.c | 117 +
1 file changed, 53 insertions(+), 64 deletions(-)
diff --git
Add multiple byte read-write support for slave mode.
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Srinath Mannam
---
drivers/i2c/busses/i2c-bcm-iproc.c | 117 +
1 file changed, 53 insertions(+), 64 deletions(-)
diff --git
Add initial version of device tree for Facebook YAMP ast2500 BMC.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/Makefile| 1 +
.../arm/boot/dts/aspeed-bmc-facebook-yamp.dts | 160 ++
2 files changed, 161 insertions(+)
create mode 100644
Enable ehci0 and ehci1 USB host controllers on Facebook Backpack CMM BMC.
Signed-off-by: Tao Ren
---
arch/arm/boot/dts/aspeed-bmc-facebook-cmm.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-cmm.dts
I noticed that Linux has been updated on later versions to always
consume the skb in calls to dev_queue_xmit, and may even drop the skb
after returning a return code of NETDEV_TX_OK which seems kind of
broken. I have an application which requires guaranteed skb
transmission and the following code
Greetings
My name is Mr. George Kwame from Odikro Royal Family Bolgatanga Upper
East Region Northern Ghana. We are a group of local gold Miners and end
sellers we are looking for a direct buyer or an agent who will help us
look for buyer on Commission basis.
The Purity of our gold is 93%
On Wed, May 08, 2019 at 06:58:28PM +0200, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> From: Dmitry Vyukov
> Date: Wed, May 8, 2019 at 1:25 PM
> To: Eric Biggers
> Cc: syzbot, KVM list, , David Miller, Artem
> Bityutskiy, , Josh Poimboeuf, LKML,
> , Andy Lutomirski, Ingo Molnar, Peter
> Zijlstra,
On Thu, May 9, 2019 at 3:36 AM Eddie James wrote:
>
> From: Christopher Bostic
>
> Add a manufacturer's suggested workaround to deal with early revisions
> of chip that don't indicate correct temperature. Readings can be in the
> ~60C range when they should be in the ~20's.
>
> Signed-off-by:
In "Y+P" of this line, there are two non-ASCII characters(0xd9 0x8d)
following behind the 'Y'. Shown as a small '=' under the '+' in VIM
and a '賺' in webpage[1].
I think it's a mistake and remove these strange characters.
[1]:
On Wed 08 May 19:25 PDT 2019, Rob Clark wrote:
> On Wed, May 8, 2019 at 7:16 PM Brian Masney wrote:
> >
> > On Mon, May 06, 2019 at 11:39:02PM -0700, Bjorn Andersson wrote:
> > > On Sun 05 May 06:04 PDT 2019, Brian Masney wrote:
> > > > diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
> > > >
On 5/8/19 4:16 PM, Daniel Thompson wrote:
On Wed, May 08, 2019 at 09:52:39AM +0800, Wenlin Kang wrote:
The strncpy() function may leave the destination string buffer
unterminated, better use strlcpy() instead.
This fixes the following warning with gcc 8.2:
kernel/debug/kdb/kdb_io.c: In
There are still some trailing whitespaces under scripts/kconfig/tests/,
but they must be kept. Otherwise, "make testconfig" would break.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/gconf.c | 2 +-
scripts/kconfig/lxdialog/BIG.FAT.WARNING | 2 +-
2 files changed, 2
On 2019/5/8 23:50, Eric Dumazet wrote:
> On Wed, May 8, 2019 at 8:33 AM YueHaibing wrote:
>>
>> kernel BUG at lib/list_debug.c:47!
>> invalid opcode: [#1
>> CPU: 0 PID: 11195 Comm: rmmod Tainted: GW 5.1.0+ #33
>> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
On Tue, 30 Apr 2019 17:49:37 -0500
Parav Pandit wrote:
> In following sequences, child devices created while removing mdev parent
> device can be left out, or it may lead to race of removing half
> initialized child mdev devices.
>
> issue-1:
>
>cpu-0
: 31ccad9b Add linux-next specific files for 20190508
git tree: linux-next
final crash:https://syzkaller.appspot.com/x/report.txt?x=13e40aaca0
console output: https://syzkaller.appspot.com/x/log.txt?x=15e40aaca0
kernel config: https://syzkaller.appspot.com/x/.config?x=63cd766601c6c9fc
Hi all,
Today's linux-next merge of the mfd tree got a conflict in:
MAINTAINERS
between commit:
10b5d3d10759 ("MAINTAINERS: add maintainer for maxbotix ultrasonic driver")
from Linus' tree and commit:
796fad0101d3 ("MAINTAINERS: Add an entry for MAX77650 PMIC driver")
from the mfd
Hi Robin,
On 5/7/19 6:28 PM, Robin Murphy wrote:
On 06/05/2019 16:32, Tom Murphy via iommu wrote:
The AMD driver already solves this problem and uses the generic
iommu_request_dm_for_dev function. It seems like both drivers have the
same problem and could use the same solution. Is there any
On 2019/5/1 17:29, Rasmus Villemoes wrote:
> -Original Message-
> From: Rasmus Villemoes
> Sent: 2019年5月1日 17:29
> To: devicet...@vger.kernel.org; Qiang Zhao ; Leo Li
>
> Cc: linuxppc-...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org; Rob
On Wed, May 08, 2019 at 02:39:32PM -0700, Curtis Malainey wrote:
> Pixelbooks (Samus Chromebook) are the only devices that use this part.
> Realtek has confirmed this. Therefore we only have to worry about
> breaking ourselves. That being said I agree there is likely a better
And there are no
the patch has no impact on the generated binary.
Patch is against 5.1 (localversion-next is next-20190508)
drivers/rtc/rtc-ds2404.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-ds2404.c b/drivers/rtc/rtc-ds2404.c
index 1e9f429..9df0c44 100644
--- a/drivers
On 5/8/19 6:44 PM, Theodore Ts'o wrote:
> On Wed, May 08, 2019 at 05:58:49PM -0700, Frank Rowand wrote:
>>
>> If KUnit is added to the kernel, and a subsystem that I am submitting
>> code for has chosen to use KUnit instead of kselftest, then yes, I do
>> *have* to use KUnit if my submission needs
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: ef75bd71c5d31dc17ae41ff8bec92630a3037d69
commit: a51645f70f6384ae3329551750f7f502cb8de5fc net: ethernet: support
of_get_mac_address new ERR_PTR error
date: 31 hours ago
config: i386-randconfig-c0-05090856
On Wed, May 08, 2019 at 01:49:09PM -0400, Julien Desfossez wrote:
> On 08-May-2019 10:30:09 AM, Aaron Lu wrote:
> > On Mon, May 06, 2019 at 03:39:37PM -0400, Julien Desfossez wrote:
> > > On 29-Apr-2019 11:53:21 AM, Aaron Lu wrote:
> > > > This is what I have used to make sure no two unmatched
On Mon, May 06, 2019 at 11:39:02PM -0700, Bjorn Andersson wrote:
> On Sun 05 May 06:04 PDT 2019, Brian Masney wrote:
> > diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
> > b/arch/arm/boot/dts/qcom-msm8974.dtsi
> [..]
> > + clocks = < MDSS_MDP_CLK>,
> > +
On 5/8/19 6:38 PM, Aubrey Li wrote:
On Thu, May 9, 2019 at 8:29 AM Subhra Mazumdar
wrote:
On 5/8/19 5:01 PM, Aubrey Li wrote:
On Thu, May 9, 2019 at 2:41 AM Subhra Mazumdar
wrote:
On 5/8/19 11:19 AM, Subhra Mazumdar wrote:
On 5/8/19 8:49 AM, Aubrey Li wrote:
Pawan ran an experiment
Hi Scott,
On Wed, May 08, 2019 at 04:39:51PM -0500, Scott Wood wrote:
> On Mon, 2019-04-15 at 14:22 -0500, Alan Tull wrote:
> > On Thu, Apr 11, 2019 at 11:36 AM Moritz Fischer
> > wrote:
> >
> > Hi Scott,
> >
> > Thanks!
> >
> > > Hi Scott,
> > >
> > > good catch!
> > >
> > > On Thu, Apr
if iio_dummy_evgen_create() fails, iio_evgen should be NULL, when call
iio_evgen_release() to cleanup, it throws some warning and could cause
double free.
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
drivers/iio/dummy/iio_dummy_evgen.c | 4
1 file changed, 4 insertions(+)
diff
Darren,
Please, see my comments below...
On 5/8/19 6:06 PM, Darren Hart wrote:
> On Wed, May 08, 2019 at 11:49:34AM -0500, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the
Some platforms may need warm reboot support when kernel crashed
for post mortem analysis instead of cold reboot. So use config
CONFIG_WARM_REBOOT_ON_PANIC and SYSTEM_RESET2 psci command
support for warm reset.
Signed-off-by: Prasad Sodagudi
---
kernel/panic.c| 4
lib/Kconfig.debug |
Ping...
> -Original Message-
> From: Anson Huang [mailto:anson.hu...@nxp.com]
> Sent: Tuesday, April 16, 2019 11:22 AM
> To: robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> catalin.mari...@arm.com;
Ping...
> -Original Message-
> From: Anson Huang
> Sent: Wednesday, April 24, 2019 10:59 AM
> To: thierry.red...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com; li...@armlinux.org.uk;
On Wed, 8 May 2019 at 23:15, Dmitry Osipenko wrote:
>
> 07.05.2019 9:09, Baolin Wang пишет:
> > Since we've introduced one device node parameter for
> > __dma_request_channel(),
> > thus change to the correct function prototype.
> >
> > Signed-off-by: Baolin Wang
> > ---
> >
Ping...
> -Original Message-
> From: Anson Huang
> Sent: Sunday, April 28, 2019 2:27 PM
> To: jassisinghb...@gmail.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Cc:
Ping...
> -Original Message-
> From: Anson Huang
> Sent: Thursday, April 25, 2019 9:50 AM
> To: dmitry.torok...@gmail.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> linux-in...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux-
Ping...
> -Original Message-
> From: Anson Huang
> Sent: Sunday, April 28, 2019 2:30 PM
> To: Mukesh Ojha ; dmitry.torok...@gmail.com;
> shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com; linux-in...@vger.kernel.org; linux-arm-
>
> -Original Message-
> From: Christoph Hellwig
> Sent: Wednesday, May 8, 2019 2:52 PM
> To: Limonciello, Mario
> Cc: kai.heng.f...@canonical.com; kbu...@kernel.org; keith.bu...@intel.com;
> ax...@fb.com; h...@lst.de; s...@grimberg.me; linux-n...@lists.infradead.org;
>
On Thu, May 9, 2019 at 8:29 AM Subhra Mazumdar
wrote:
>
>
> On 5/8/19 5:01 PM, Aubrey Li wrote:
> > On Thu, May 9, 2019 at 2:41 AM Subhra Mazumdar
> > wrote:
> >>
> >> On 5/8/19 11:19 AM, Subhra Mazumdar wrote:
> >>> On 5/8/19 8:49 AM, Aubrey Li wrote:
> > Pawan ran an experiment setting up
On 2019-05-02 02:05, Sudeep Holla wrote:
On Wed, May 01, 2019 at 11:43:00AM -0700, Sodagudi Prasad wrote:
On 2019-05-01 02:49, Sudeep Holla wrote:
> On Tue, Apr 30, 2019 at 05:07:31PM -0700, Sodagudi Prasad wrote:
> > On 2019-04-30 14:44, Sodagudi Prasad wrote:
[...]
> >
> > It would nice
Restrict kdump to only reserve crashkernel below 64TB.
The reaons is that the kdump may jump from 5-level to 4-level, and if
the kdump kernel is put above 64TB, then the jumping will fail. While the
1st kernel reserves crashkernel region during bootup, we don't know yet
which kind of kernel will
This patchset is trying to fix several issues for kexec/kdump when
dynamic switching of paging mode is enabled in x86_64. The current
kernel supports 5-level paging mode, and supports dynamically choosing
paging mode during bootup according to kernel image, hardware and
kernel parameter setting.
If the running kernel has 5-level paging activated, the 5-level paging
mode is preserved across kexec. If the kexec'ed kernel does not contain
support for handling active 5-level paging mode in the decompressor, the
decompressor will crash with #GP.
Prevent this situation at load time. If 5-level
The current kernel supports 5-level paging mode, and supports dynamically
choosing paging mode during bootup according to kernel image, hardware and
kernel parameter setting. This flexibility brings several issues to
kexec/kdump:
1)
Dynamic switching between paging modes requires code change in
Hi Josh,
On Wed, 8 May 2019 13:48:48 -0500
Josh Poimboeuf wrote:
> On Wed, May 08, 2019 at 05:39:07PM +0200, Peter Zijlstra wrote:
> > On Wed, May 08, 2019 at 07:42:48AM -0500, Josh Poimboeuf wrote:
> > > On Wed, May 08, 2019 at 02:04:16PM +0200, Peter Zijlstra wrote:
> >
> > > > Do the x86_64
On Tue, May 07, 2019 at 05:02:47AM +, Dexuan Cui wrote:
From: Adrian Vladu
Sent: Monday, May 6, 2019 10:34 AM
To: linux-kernel@vger.kernel.org
Cc: Adrian Vladu ; KY Srinivasan
; Haiyang Zhang ; Stephen
Hemminger ; Sasha Levin ;
Dexuan Cui ; Alessandro Pilotti
Subject: [PATCH v2] hv: tools:
On Mon, May 06, 2019 at 04:50:58PM +, Adrian Vladu wrote:
HyperV KVP and VSS daemons should exit with 0 when the '--help'
or '-h' flags are used.
Signed-off-by: Adrian Vladu
Cc: "K. Y. Srinivasan"
Cc: Haiyang Zhang
Cc: Stephen Hemminger
Cc: Sasha Levin
Cc: Alessandro Pilotti
Queued
On Mon, May 06, 2019 at 04:51:24PM +, Adrian Vladu wrote:
Fix typos in the HyperV toolchain.
Signed-off-by: Adrian Vladu
Cc: "K. Y. Srinivasan"
Cc: Haiyang Zhang
Cc: Stephen Hemminger
Cc: Sasha Levin
Cc: Alessandro Pilotti
Queued for hyperv-fixes, thanks!
--
Thanks,
Sasha
On Tue, May 07, 2019 at 12:51:51PM +, Michael Kelley wrote:
From: Dexuan Cui Sent: Tuesday, May 7, 2019 12:47 AM
In the case of X86_PAE, unsigned long is u32, but the physical address type
should be u64. Due to the bug here, the netvsc driver can not load
successfully, and sometimes the
This warning was disabled by commit bd664f6b3e37 ("disable new
gcc-7.1.1 warnings for now") just because it was too noisy.
Thanks to Arnd Bergmann, all warnings have been fixed. Now, we are
ready to re-enable it.
Signed-off-by: Masahiro Yamada
Cc: Arnd Bergmann
---
Changes in v2:
- rebase
understanding
that does not change the program logic here.
Patch was compile-tested with: tegra_defconfig (implies I2C_TEGRA=y)
Patch is against 5.1 (localversion-next is next-20190508)
drivers/i2c/busses/i2c-tegra.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers
Thank you so much.
On Wed, 8 May 2019 at 16:56, Peter Zijlstra wrote:
>
> On Mon, May 06, 2019 at 04:19:16PM +0800, Yuyang Du wrote:
> > Hi Peter,
> >
> > Let me post these small bits first while waiting for Frederic's patches
> > to be merged.
> >
>
> They apply nicely and should show up in tip
On Thu, May 9, 2019 at 4:27 AM Nick Desaulniers wrote:
>
> bumping for review, as the merge window is now open.
ia64 is not very active these days.
I applied this to my kbuild tree.
I will send PR for this in the current MW.
Thanks.
> On Tue, Apr 30, 2019 at 1:24 PM Nick Desaulniers
>
Hi Jon,
Today's linux-next merge of the jc_docs tree got a conflict in:
Documentation/x86/x86_64/mm.txt
between commit:
89502a019790 ("x86/mm: Fix the 56-bit addresses memory map in
Documentation/x86/x86_64/mm.txt")
from Linus' tree and commit:
b88679d2f2b9 ("Documentation: x86:
On Thu, May 9, 2019 at 5:13 AM Nick Desaulniers wrote:
>
> bumping for review, as the merge window is now open.
sh is not very active these days.
I applied this to my kbuild tree.
I will send PR for this in the current MW.
Thanks.
> On Tue, Apr 30, 2019 at 1:26 PM Nick Desaulniers
>
On 5/8/19 5:01 PM, Aubrey Li wrote:
On Thu, May 9, 2019 at 2:41 AM Subhra Mazumdar
wrote:
On 5/8/19 11:19 AM, Subhra Mazumdar wrote:
On 5/8/19 8:49 AM, Aubrey Li wrote:
Pawan ran an experiment setting up 2 VMs, with one VM doing a
parallel kernel build and one VM doing sysbench,
limiting
Hello,
syzbot found the following crash on:
HEAD commit:31ccad9b Add linux-next specific files for 20190508
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1082d2aca0
kernel config: https://syzkaller.appspot.com/x/.config?x=63cd766601c6c9fc
On Wed, May 08, 2019 at 05:47:32PM -0400, Paul Moore wrote:
> On Wed, May 8, 2019 at 2:27 AM Nicholas Mc Guire wrote:
> > While the endiannes is being handled properly sparse was unable to verify
> > this due to type inconsistency. So introduce an additional __le32
> > respectively _le64 variable
From: Christoph Hellwig
Date: Tue, 16 Apr 2019 20:23:38 +0200
> this series fixes some long standing bugs in the sparc32 iommu driver,
> mostly the lack of handling of large sglist offsets in the map_sg
> method, but also a few other smaller bits. These now show up all the
> time do some block
On Thu, May 9, 2019 at 2:41 AM Subhra Mazumdar
wrote:
>
>
> On 5/8/19 11:19 AM, Subhra Mazumdar wrote:
> >
> > On 5/8/19 8:49 AM, Aubrey Li wrote:
> >>> Pawan ran an experiment setting up 2 VMs, with one VM doing a
> >>> parallel kernel build and one VM doing sysbench,
> >>> limiting both VMs to
From: Masahiro Yamada
Date: Wed, 3 Apr 2019 17:32:24 +0900
> $(call if_changed,...) must have FORCE as a prerequisite.
>
> Signed-off-by: Masahiro Yamada
Applied.
From: jagdsh.li...@gmail.com
Date: Thu, 28 Mar 2019 02:58:45 +0530
> From: Jagadeesh Pagadala
>
> Remove duplicate header which is included twice.
>
> Signed-off-by: Jagadeesh Pagadala
Applied.
Finally deprecate the legacy IDE layer.
Frankly this is long overdue.
Please pull, thanks a lot!
The following changes since commit ef75bd71c5d31dc17ae41ff8bec92630a3037d69:
Merge tag 'gfs2-for-5.2' of
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2019-05-08
13:16:07
The pull request you sent on Wed, 8 May 2019 21:04:46 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git tags/mips_5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/92fab77b6b309dc219b02da4a69ad5dc76f7ec74
Thank you!
--
Deet-doot-dot, I am a
>> - patches are rebased on top of Arnaldo's perf/core with perf/urgent
>merged in
>>
>> It's also available in here:
>> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
>> perf/fixes
>>
>> thanks,
>> jirka
>>
>
>For the series:
>
>Acked-by: Song Liu
Monday I'll test and
On Wed, May 08, 2019 at 03:55:22PM -0700, Darren Hart wrote:
> On Wed, May 08, 2019 at 11:20:52AM +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 08-05-19 10:42, Andy Shevchenko wrote:
> > > On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote:
> > > > On 07-05-19 22:17, Stephen Boyd wrote:
> > >
On Sat, May 04, 2019 at 07:52:42AM -0700, Shakeel Butt wrote:
> The commit d46eb14b735b ("fs: fsnotify: account fsnotify metadata to
> kmemcg") added remote memcg charging for fanotify and inotify event
> objects. The aim was to charge the memory to the listener who is
> interested in the events
On Wed, May 08, 2019 at 03:29:12PM +0100, Suzuki K Poulose wrote:
>
> On 08/05/2019 03:18, Leo Yan wrote:
> > Since the DT bindings consolidatoins for CoreSight replicator and funnel
> > is ready for kernel v5.2 merge window [1], this patch set is to update
> > the related CoreSight DT bindings
From: Andy Shevchenko
Date: Wed, May 8, 2019 at 2:22 PM
To: Randy Dunlap
Cc: Stephen Rothwell, Linux Next Mailing List, Linux Kernel Mailing
List, Rajat Jain, Platform Driver, Rajneesh Bhardwaj, Vishwanath
Somayaji
> On Wed, May 8, 2019 at 11:45 PM Randy Dunlap wrote:
> >
> > On 5/8/19 12:34
On Wed, May 08, 2019 at 11:49:34AM -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/platform/x86/acer-wmi.c: In function ‘set_u32’:
>
Neil Armstrong writes:
> Add Infrared Decoder support for the Amlogic G12A and enable it on the
> X96 Max and U200 Reference Design boards.
Queued for v5.3 (branch: v5.3/dt64)
Kevin
Neil Armstrong writes:
> Amlogic G12A SoCs uses the exact same IR decoder as previous
> families, add the IR node and the pintctrl setting.
>
> Signed-off-by: Neil Armstrong
> ---
> arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff
On Wed, May 08, 2019 at 11:20:52AM +0200, Hans de Goede wrote:
> Hi,
>
> On 08-05-19 10:42, Andy Shevchenko wrote:
> > On Wed, May 8, 2019 at 10:48 AM Hans de Goede wrote:
> > > On 07-05-19 22:17, Stephen Boyd wrote:
> > > > Quoting Hans de Goede (2019-05-06 08:05:42)
> >
> > > > I guess this
Hi all,
On Wed, May 16, 2018 at 11:18:45AM +0300, Yury Norov wrote:
> This series enables AARCH64 with ILP32 mode.
>
> As supporting work, it introduces ARCH_32BIT_OFF_T configuration
> option that is enabled for existing 32-bit architectures but disabled
> for new arches (so 64-bit off_t
On Wed, May 08, 2019 at 11:42:01PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The variable tad_base is being set to a value that is never read
> and is being over-written on the next iteration of a for-loop.
> This assignment is therefore redundant and can be removed.
>
>
The QCS404 has a PCIe2 PHY and a Qualcomm PCIe controller, define these
to for the platform.
Reviewed-by: Niklas Cassel
Signed-off-by: Bjorn Andersson
---
Changes since v3:
- Split single patch, no functional change
arch/arm64/boot/dts/qcom/qcs404.dtsi | 65
1
From: Colin Ian King
The variable tad_base is being set to a value that is never read
and is being over-written on the next iteration of a for-loop.
This assignment is therefore redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
Enable the PCIe PHY and controller found on the QCS404 EVB.
Signed-off-by: Bjorn Andersson
---
Changes since v3:
- Split single patch, no functional change
arch/arm64/boot/dts/qcom/qcs404-evb.dtsi | 26
1 file changed, 26 insertions(+)
diff --git
This series defines the PCIe PHY and controller on QCS404 and enable them for
EVB. This was 1 commit, but per Vinod's request its split up in its individual
pieces.
Bjorn Andersson (3):
arm64: dts: qcom: qcs404: Make gcc as reset-controller
arm64: dts: qcom: qcs404: Add PCIe related nodes
GCC is a reset-controller, so define #reset-cells.
Signed-off-by: Bjorn Andersson
---
Changes since v3:
- Split single patch, no functional change
arch/arm64/boot/dts/qcom/qcs404.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
Neil Armstrong writes:
> This adds the EE and AO PWM nodes and the possible pinctrl settings.
>
> Signed-off-by: Neil Armstrong
> Reviewed-by: Martin Blumenstingl
Since bindings are acked, and there's no build dependency on the driver
itself, queuing this for v5.3 (branch: v5.3/dt64)
Thanks,
Enabling PCIe requires several of the PCIe related resets from GCC, so
add them all.
Reviewed-by: Niklas Cassel
Acked-by: Stephen Boyd
Acked-by: Rob Herring
Signed-off-by: Bjorn Andersson
---
Changes since v3:
- Fix rebase mistake in v2
Changes since v2:
- Rebase patch
From: Colin Ian King
In the unlikely event that axi_desc_get returns a null desc in the
very first iteration of the while-loop the error exit path ends
up calling axi_desc_put on a null pointer 'first' and this causes
a null pointer dereference. Fix this by adding a null check on
pointer
On 22/03/2019 12.57, Suthikulpanit, Suravee wrote:
> Introduce a helper function for setting lapic parameters when
> activate/deactivate apicv.
>
> Signed-off-by: Suravee Suthikulpanit
> ---
> arch/x86/kvm/lapic.c | 23 ++-
> arch/x86/kvm/lapic.h | 1 +
> 2 files changed,
On Wed, 08 May 2019 14:47:45 PDT (-0700), Stephen Rothwell wrote:
Hi all,
Commits
da8e7c379659 ("riscv: Support BUG() in kernel module")
564bd22ea4e5 ("riscv: Add the support for c.ebreak check in
is_valid_bugaddr()")
67363778b72c ("riscv: support trap-based WARN()")
efd48cf0b393
1 - 100 of 811 matches
Mail list logo
