On (08/21/19 07:46), John Ogness wrote:
[..]
> The labels are necessary for the technical documentation of the
> barriers. And, after spending much time in this, I find them very
> useful. But I agree that there needs to be a better way to assign label
> names.
[..]
> > Where dp stands for
On Thu, 2019-08-22 at 15:39 -0700, David Miller wrote:
> From: Haiyang Zhang
> Date: Thu, 22 Aug 2019 22:37:13 +
>
> > The v5 is pretty much the same as v4, except Eran had a fix to
> patch #3 in response to
> > Leon Romanovsky .
>
> Well you now have to send me a patch relative to v4 in
Add YAML schemas for the reset controller on Intel
Lightening Mountain (LGM) SoC.
Signed-off-by: Dilip Kota
---
Changes on v2:
Address review comments
Update the compatible property definition
Add description for reset-cells
Add 'additionalProperties: false' property
Add driver for the reset controller present on Intel
Lightening Mountain (LGM) SoC for performing reset
management of the devices present on the SoC. Driver also
registers a reset handler to peform the entire device reset.
Signed-off-by: Dilip Kota
---
Changes on v2:
No changes
On Thu, Aug 22, 2019 at 01:02:05PM -0700, 'Nick Desaulniers' via Clang Built
Linux wrote:
> On Thu, Aug 22, 2019 at 11:30 AM Nathan Huckleberry wrote:
> >
> > The stackframe setup when compiled with clang is different.
> > Since the stack unwinder expects the gcc stackframe setup it
> > fails to
As 4k pages check was removed from cpa [1], set_kernel_text_rw() leads to
split_large_page() for all kernel text pages. This means a single kprobe
will put all kernel text in 4k pages:
root@ ~# grep 8100- /sys/kernel/debug/page_tables/kernel
0x8100-0x8240
Hi Rob,
On 8/23/2019 1:54 AM, Rob Herring wrote:
On Thu, Aug 22, 2019 at 2:32 AM Dilip Kota wrote:
Add YAML schemas for the reset controller on Intel
Lightening Mountain (LGM) SoC.
Signed-off-by: Dilip Kota
---
.../bindings/reset/intel,syscon-reset.yaml | 50 ++
Hi Vignesh,
On 22/8/2019 5:03 PM, Vignesh Raghavendra wrote:
Hi,
On 19/08/19 5:24 PM, Ramuthevar, Vadivel MuruganX wrote:
From: Ramuthevar Vadivel Murugan
On Intel Lightening Mountain(LGM) SoCs QSPI controller do not use
s/Lightening/Lightning
Thank you so much for the review comments
On Fri, 2019-07-26 at 22:18 +0800, YueHaibing wrote:
> There expect the 'static' keyword to come first in a
> declaration, and we get a warning for this with "make W=1":
>
> drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:427:1: warning:
> 'static' is not at beginning of declaration
> On Thu, 2019-08-22 at 06:43 -0400, Pankaj Gupta wrote:
> > > This series provides an asynchronous means of reporting to a hypervisor
> > > that a guest page is no longer in use and can have the data associated
> > > with it dropped. To do this I have implemented functionality that allows
> > >
Hi Dmitry
On 2019/08/17 2:24, Dmitry Torokhov wrote:
On Fri, Aug 16, 2019 at 05:34:58PM +0900, Jiada Wang wrote:
From: Kautuk Consul
The upstream Atmel mXT driver implementation seems to handle the
T19 GPIO/PWM object as a key pad. Keys can be defined in the
device tree ("linux,gpio-keymap")
On Thu, 2019-08-01 at 17:44 +0100, Colin King wrote:
> From: Colin Ian King
>
> The variable bufsz is being initialized with a value that is never
> read and it is being updated later with a new value. The
> initialization is redundant and can be removed.
>
> Addresses-Coverity: ("Unused
On Wed, 2019-07-24 at 19:27 +0800, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan
> ---
This patch is not relevant anymore because we have removed all
D0i3/runtime PM code.
Thanks anyway!
--
On 8/23/2019 1:43 AM, Haiyang Zhang wrote:
>
>
>> -Original Message-
>> From: David Miller
>> Sent: Thursday, August 22, 2019 3:39 PM
>> To: Haiyang Zhang
>> Cc: sas...@kernel.org; sae...@mellanox.com; l...@kernel.org;
>> era...@mellanox.com; lorenzo.pieral...@arm.com;
On Fri, 2019-08-23 at 08:11 +0530, Kishon Vijay Abraham I wrote:
>
> On 22/07/19 12:53 PM, Neil Armstrong wrote:
> > On 10/07/2019 07:04, Joe Perches wrote:
> > > Arguments are supposed to be ordered high then low.
> > >
> > > Signed-off-by: Joe Perches
> > > ---
> > >
On Fri, Aug 23, 2019 at 01:20:37PM +0900, boojin.kim wrote:
>
> If yes, I think the following API needs to be added to skcipher:
> - _set(): BIO submitter (dm-crypt, f2fs, ext4) sets cipher to BIO.
> - _mergeable(): Block layer checks if two BIOs have the same cipher.
> - _get(): Storage driver
On Wed, Aug 21, 2019 at 17:19:41PM +0900, Herbert Xu wrote:
> On Wed, Aug 21, 2019 at 04:57:41PM +0900, boojin.kim wrote:
> >
> > Can you tell me which patch you mentioned? Is this?
> > https://patches.linaro.org/project/linux-crypto/list/?series=22762
> >
>
> Yes this is the one.
>
> Cheers,
I
> -Original Message-
> From: Kishon Vijay Abraham I
> Sent: 2019年8月23日 11:40
> To: Xiaowei Bao ; bhelg...@google.com;
> robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; Leo Li
> ; lorenzo.pieral...@arm.co
> ; a...@arndb.de; gre...@linuxfoundation.org;
> M.h. Lian ; Mingkai
syzbot found that a thread can stall for minutes inside read_mem() or
write_mem() after that thread was killed by SIGKILL [1]. Reading 2GB at
one read() is legal, but delaying termination of killed thread for minutes
is bad. Let's insert cond_resched() and SIGKILL check into iteration loop
of
From: Rob Clark
I'm sure there is plenty more to remove.. this is just some of the ones
I noticed.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 19 ---
.../drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 3 ---
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c| 2 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 2 +-
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 3 +--
3 files changed, 3 insertions(+), 4 deletions(-)
diff --git
On Thu, 2019-08-22 at 19:52 -0700, Sagi Grimberg wrote:
> > > I'll fix it. Note that I'm going to take it out of the tree soon
> > > because it will have conflicts with Jens for-5.4/block, so we
> > > will send it to Jens after the initial merge window, after he
> > > rebases off of Linus.
> >
>
While tracing a program that calls isatty(3), I noticed that strace reported
TCGETS for the request argument of the underlying ioctl(2) syscall while perf
trace reported TCSETS. strace is corrrect. The bug in perf was due to the tty
ioctl beauty table starting at 0x5400 rather than 0x5401.
Fixes:
Some pmics don't need backup interrupt settings, so we change to use
pm notifier for the pmics which are necessary to store settings.
Acked-for-mfd-by: Lee Jones
Signed-off-by: Hsin-Hsiung Wang
---
drivers/mfd/mt6397-core.c | 89 +
This patchset including refactoring interrupt add support to MT6358 PMIC.
MT6358 is the primary PMIC for MT8183 platform.
changes since v4:
- fix some comments for mfd driver.
- fix some coding style issues for regulator driver.
- merge the same voltage tables and index tables for regulator
refine some variable name for more readable
Acked-for-mfd-by: Lee Jones
Signed-off-by: Hsin-Hsiung Wang
---
drivers/mfd/mt6397-core.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
index
add dt-binding document for MediaTek MT6358 PMIC
Reviewed-by: Rob Herring
Signed-off-by: Hsin-Hsiung Wang
---
.../bindings/regulator/mt6358-regulator.txt| 358 +
1 file changed, 358 insertions(+)
create mode 100644
From: Ran Bi
Alarm registers high byte was reserved for other functions.
This add mask in alarm registers operation functions.
This also fix error condition in interrupt handler.
Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC driver")
Acked-by: Alexandre Belloni
Signed-off-by: Ran Bi
The MT6358 is a regulator found on boards based on MediaTek MT8183 and
probably other SoCs. It is a so called pmic and connects as a slave to
SoC using SPI, wrapped inside the pmic-wrapper.
Signed-off-by: Hsin-Hsiung Wang
---
drivers/regulator/Kconfig | 9 +
In order to support different types of irq design, we decide to add
separate irq drivers for different design and keep mt6397 mfd core
simple and reusable to all generations of PMICs so far.
Acked-for-mfd-by: Lee Jones
Signed-off-by: Hsin-Hsiung Wang
---
drivers/mfd/Makefile| 3
This adds compatible for the MediaTek MT6358 PMIC.
Acked-for-mfd-by: Lee Jones
Reviewed-by: Rob Herring
Signed-off-by: Hsin-Hsiung Wang
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git
This adds support for the MediaTek MT6358 PMIC. This is a
multifunction device with the following sub modules:
- Regulator
- RTC
- Codec
- Interrupt
It is interfaced to the host controller using SPI interface
by a proprietary hardware called PMIC wrapper or pwrap.
MT6358 MFD is a child device of
From: Ran Bi
This add support for the MediaTek MT6358 RTC. Driver using
compatible data to store different RTC_WRTGR address offset.
Signed-off-by: Ran Bi
---
drivers/rtc/rtc-mt6397.c | 38 ++
1 file changed, 30 insertions(+), 8 deletions(-)
diff --git
add PMIC MT6358 related nodes which is for MT8183 platform
Signed-off-by: Hsin-Hsiung Wang
---
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 361 +++
1 file changed, 361 insertions(+)
create mode 100644 arch/arm64/boot/dts/mediatek/mt6358.dtsi
diff --git
From: Sha Zhang
After the commit 334031219a84 ("bonding/802.3ad: fix slave link
initialization transition states") merged,
the slave's link status will be changed to BOND_LINK_FAIL
from BOND_LINK_DOWN in the following scenario:
- Driver reports loss of carrier and
bonding driver receives
Hi,
(Fixed Lorenzo's email address. All the patches in the series have wrong email
id)
On 23/08/19 8:09 AM, Xiaowei Bao wrote:
>
>
>> -Original Message-
>> From: Kishon Vijay Abraham I
>> Sent: 2019年8月22日 19:44
>> To: Xiaowei Bao ; bhelg...@google.com;
>> robh...@kernel.org;
> > endmenu
> > diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
> > index 09829e15d4a0..c9c63a4033cd 100644
> > --- a/drivers/hv/connection.c
> > +++ b/drivers/hv/connection.c
> > @@ -357,6 +357,9 @@ void vmbus_on_event(unsigned long data)
> >
> >
Hi Andy,
On 22/8/2019 9:04 PM, Andy Shevchenko wrote:
On Thu, Aug 22, 2019 at 05:26:33PM +0800, Tanwar, Rahul wrote:
On 22/8/2019 5:02 PM, Andy Shevchenko wrote:
On Thu, Aug 22, 2019 at 03:44:03PM +0800, Rahul Tanwar wrote:
Use a newly introduced optional "status" property of
LGTM, sorry for the mid air collision. Thanks for resolving, Stephen!
On Thu, Aug 22, 2019 at 8:08 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Today's linux-next merge of the crypto tree got a conflict in:
>
> arch/x86/purgatory/Makefile
>
> between commit:
>
> 4ce97317f41d ("x86/purgatory:
On Wed, Aug 21, 2019 at 01:44:21PM -0700, Ira Weiny wrote:
> On Wed, Aug 21, 2019 at 04:48:10PM -0300, Jason Gunthorpe wrote:
> > On Wed, Aug 21, 2019 at 11:57:03AM -0700, Ira Weiny wrote:
> >
> > > > Oh, I didn't think we were talking about that. Hanging the close of
> > > > the datafile fd
On Thu, 2019-08-22 at 09:39 -0400, Joel Fernandes wrote:
> On Wed, Aug 21, 2019 at 04:33:58PM -0700, Paul E. McKenney wrote:
> > On Wed, Aug 21, 2019 at 06:19:04PM -0500, Scott Wood wrote:
> > > Signed-off-by: Scott Wood
> > > ---
> > > Another question is whether non-raw spinlocks are intended
On Tue, Aug 20, 2019 at 10:33:38AM -0700, Sagi Grimberg wrote:
>
> > From: Long Li
> >
> > When a NVMe hardware queue is mapped to several CPU queues, it is possible
> > that the CPU this hardware queue is bound to is flooded by returning I/O for
> > other CPUs.
> >
> > For example, consider
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/mediatek/mtk_drm_drv.c
between commit:
4c6f3196e6ea ("drm/mediatek: use correct device to import PRIME buffers")
from the drm-fixes tree and commit:
3baeeb21983a ("drm/mtk: Drop
On Thu, Aug 15, 2019 at 09:11:51AM -0700, Ayush Ranjan wrote:
> This commit aims to fix the following issues in ext4 documentation:
> - Flexible block group docs said that the aim was to group block
> metadata together instead of block group metadata.
> - The documentation consistly uses
Hi all,
After merging the crypto tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: modpost: missing MODULE_LICENSE() in lib/crypto/libsha256.o
see include/linux/module.h for more information
Presumably introduced by commit
01d3aee86625 ("crypto: sha256 -
Hi all,
Today's linux-next merge of the crypto tree got a conflict in:
arch/x86/purgatory/Makefile
between commit:
4ce97317f41d ("x86/purgatory: Do not use __builtin_memcpy and
__builtin_memset")
from Linus' tree and commit:
ad767ee858b3 ("crypto: sha256 - Move lib/sha256.c to
On 2019/7/12 16:55, Chao Yu wrote:
> Wrap merge condition into function for readability, no logic change.
>
> Signed-off-by: Chao Yu
> ---
> v2: remove bio validation check in page_is_mergeable().
> fs/f2fs/data.c | 40 +---
> 1 file changed, 33
Hi Dmitry
On 2019/08/17 2:29, Dmitry Torokhov wrote:
On Fri, Aug 16, 2019 at 05:34:19PM +0900, Jiada Wang wrote:
From: Nick Dyer
Atmel maXTouch chips can be addressed via an "Object Based Protocol" which
defines how i2c registers are mapped to different functions within the
chips. This
is only generated and included by
arch/arm/mach-omap2/, so it does not need to reside in the globally
visible include/generated/.
I renamed it to arch/arm/mach-omap2/pm-asm-offsets.h since the prefix
'ti-' is just redundant in mach-omap2/.
My main motivation of this change is to avoid the race
On Thu, Aug 22, 2019 at 09:36:21PM -0500, Scott Wood wrote:
> On Wed, 2019-08-21 at 16:33 -0700, Paul E. McKenney wrote:
> > On Wed, Aug 21, 2019 at 06:19:04PM -0500, Scott Wood wrote:
> > > diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> > > index 388ace315f32..d6e357378732
On Wed, Aug 14, 2019 at 12:54:08PM +0300, Rakesh Pandit wrote:
> Really enable warning when CONFIG_EXT4_DEBUG is set and fix missing
> first argument. This was introduced in commit ff95ec22cd7f ("ext4:
> add warning to ext4_convert_unwritten_extents_endio") and splitting
> extents inside endio
I'll fix it. Note that I'm going to take it out of the tree soon
because it will have conflicts with Jens for-5.4/block, so we
will send it to Jens after the initial merge window, after he
rebases off of Linus.
Conflicts too hard to fixup at merge time ? Otherwise I could just
rebase on top
From: Yang Guo
@es_stats_cache_hits and @es_stats_cache_misses are accessed frequently in
ext4_es_lookup_extent function, it would influence the ext4 read/write
performance in NUMA system.
Let's optimize it using percpu_counter, it is profitable for the
performance.
The test command is as
Hi Andy,
On 22/8/2019 9:08 PM, Andy Shevchenko wrote:
On Thu, Aug 22, 2019 at 06:28:43PM +0800, Ramuthevar,Vadivel MuruganX wrote:
From: Ramuthevar Vadivel Murugan
Add support for eMMC PHY on Intel's Lightning Mountain SoC.
Thanks for an update!
One minor comment below. After addressing it
Hi Rob,
On 22/8/2019 8:49 PM, Rob Herring wrote:
On Thu, Aug 22, 2019 at 5:28 AM Ramuthevar,Vadivel MuruganX
wrote:
From: Ramuthevar Vadivel Murugan
Add a YAML schema to use the host controller driver with the
eMMC PHY on Intel's Lightning Mountain SoC.
Signed-off-by: Ramuthevar Vadivel
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 146dc303630aff5fdf006614a67704539c519c33
Gitweb:
https://git.kernel.org/tip/146dc303630aff5fdf006614a67704539c519c33
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 11:11:30
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 3c84e65a533dbaa1a29bfd847deca73704b675eb
Gitweb:
https://git.kernel.org/tip/3c84e65a533dbaa1a29bfd847deca73704b675eb
Author:Adrian Hunter
AuthorDate:Mon, 12 Aug 2019 12:09:35 +03:00
is only generated and included by
arch/arm/mach-at91/, so it does not need to reside in the globally
visible include/generated/.
I renamed it to arch/arm/mach-at91/pm_data-offsets.h since the prefix
'at91_' is just redundant in mach-at91/.
My main motivation of this change is to avoid the race
The following commit has been merged into the perf/core branch of tip:
Commit-ID: b658911731d41a91b9de5458d6f38d6e1c90a453
Gitweb:
https://git.kernel.org/tip/b658911731d41a91b9de5458d6f38d6e1c90a453
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 11:14:28
The following commit has been merged into the perf/core branch of tip:
Commit-ID: aaa6ef8aa85f33c6dd593e139b7f7d901bbde0e2
Gitweb:
https://git.kernel.org/tip/aaa6ef8aa85f33c6dd593e139b7f7d901bbde0e2
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 11:00:54
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 6e98bc349ea4219e21785d85809b10bd49e722df
Gitweb:
https://git.kernel.org/tip/6e98bc349ea4219e21785d85809b10bd49e722df
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 20 Aug 2019 12:01:38
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 0ac10d87a571ae7d68c7f70f1c2229388f1dce9e
Gitweb:
https://git.kernel.org/tip/0ac10d87a571ae7d68c7f70f1c2229388f1dce9e
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 10:53:20
On 22/07/19 12:53 PM, Neil Armstrong wrote:
> On 10/07/2019 07:04, Joe Perches wrote:
>> Arguments are supposed to be ordered high then low.
>>
>> Signed-off-by: Joe Perches
>> ---
>> drivers/phy/amlogic/phy-meson-g12a-usb2.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff
> -Original Message-
> From: Kishon Vijay Abraham I
> Sent: 2019年8月22日 19:44
> To: Xiaowei Bao ; bhelg...@google.com;
> robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; Leo Li
> ; lorenzo.pieral...@arm.co; a...@arndb.de;
> gre...@linuxfoundation.org; M.h. Lian ; Mingkai
>
On 27/07/19 5:34 PM, Martin Blumenstingl wrote:
> Various Lantiq (now Intel) SoCs contain one or more PCIe controllers
> and PHYs.
> This adds a driver for the PCIe PHYs found on the Lantiq VRX200 and
> ARX300 SoCs. GRX390 should also be supported as far as I can tell,
> but I don't have any of
On Wed, 2019-08-21 at 16:33 -0700, Paul E. McKenney wrote:
> On Wed, Aug 21, 2019 at 06:19:04PM -0500, Scott Wood wrote:
> > diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
> > index 388ace315f32..d6e357378732 100644
> > --- a/include/linux/rcupdate.h
> > +++
Hi all,
Today's linux-next merge of the net-next tree got conflicts in:
drivers/pci/Kconfig
drivers/pci/controller/pci-hyperv.c
between commit:
f58ba5e3f686 ("PCI: pci-hyperv: Fix build errors on non-SYSFS config")
44b1ece783ff ("PCI: hv: Detect and fix Hyper-V PCI domain number
On Wed, Aug 21, 2019 at 5:10 AM Jens Axboe wrote:
>
> On 8/21/19 12:42 AM, boojin.kim wrote:
> > This patch supports crypto information to be maintained via BIO
> > and passed to the storage driver.
> >
> > To do this, 'bi_aux_private', 'REQ_CYPTE' and 'bi_dun' are added
> > to the block layer.
>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: d2720c3dad58def723f9617f7cf2a48c752ef50a
Gitweb:
https://git.kernel.org/tip/d2720c3dad58def723f9617f7cf2a48c752ef50a
Author:Alexey Budankov
AuthorDate:Fri, 09 Aug 2019 18:26:30 +03:00
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 9e79ff77e4195e40e7a47a2001132db66e25d541
Gitweb:
https://git.kernel.org/tip/9e79ff77e4195e40e7a47a2001132db66e25d541
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 16:09:50
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 10ccbc1cc0b8a05a5c8491630d36d1e2672036c1
Gitweb:
https://git.kernel.org/tip/10ccbc1cc0b8a05a5c8491630d36d1e2672036c1
Author:Alexey Budankov
AuthorDate:Fri, 09 Aug 2019 18:31:28 +03:00
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 42fc2e9ef9603a7948aaa4ffd8dfb94b30294ad8
Gitweb:
https://git.kernel.org/tip/42fc2e9ef9603a7948aaa4ffd8dfb94b30294ad8
Author:Arnaldo Carvalho de Melo
AuthorDate:Tue, 20 Aug 2019 11:45:17
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 2284cf8074ff12b6304665618f81ced3aa0b41de
Gitweb:
https://git.kernel.org/tip/2284cf8074ff12b6304665618f81ced3aa0b41de
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 16:43:58
The following commit has been merged into the perf/core branch of tip:
Commit-ID: a4973d8f7bea98a0795ba853e7bd2cef11363824
Gitweb:
https://git.kernel.org/tip/a4973d8f7bea98a0795ba853e7bd2cef11363824
Author:Leo Yan
AuthorDate:Thu, 15 Aug 2019 16:28:54 +08:00
Committer:
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 2566349648b40aa3f5edf6af8f7f893ccd6e4eae
Gitweb:
https://git.kernel.org/tip/2566349648b40aa3f5edf6af8f7f893ccd6e4eae
Author:Alexey Budankov
AuthorDate:Fri, 09 Aug 2019 18:23:58 +03:00
Hello,
syzbot found the following crash on:
HEAD commit:bb7ba806 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1272e01260
kernel config: https://syzkaller.appspot.com/x/.config?x=6919752cc1b760b4
From: Ben Wei
Date: Wed, 21 Aug 2019 22:08:49 +
> Update response packet length for the following commands per NC-SI spec
> - Get Controller Packet Statistics
> - Get NC-SI Statistics
> - Get NC-SI Pass-through Statistics command
>
> Signed-off-by: Ben Wei
Applied, thanks Ben.
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 5c959b6d8f9369e42a3cb0423bcce9ac069cee55
Gitweb:
https://git.kernel.org/tip/5c959b6d8f9369e42a3cb0423bcce9ac069cee55
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 16:48:25
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 9b01611934c045ac7ca71aebf5ee1906951d6bce
Gitweb:
https://git.kernel.org/tip/9b01611934c045ac7ca71aebf5ee1906951d6bce
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 19 Aug 2019 16:38:24
From:
Date: Wed, 21 Aug 2019 21:24:52 +
> The request coming from Netlink should use the OEM generic handler.
>
> The standard command handler expects payload in bytes/words/dwords
> but the actual payload is stored in data if the request is coming from
> Netlink.
>
> Signed-off-by:
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
drivers/infiniband/hw/mlx5/mlx5_ib.h
between commit:
0e6613b41edd ("IB/mlx5: Consolidate use_umr checks into single function")
from the rdma-fixes tree and commit:
3e1f000ff746 ("IB/mlx5: Support per device q counters
The following commit has been merged into the perf/core branch of tip:
Commit-ID: b81d39c7a1efb83caa3f4419939a46e96191abb6
Gitweb:
https://git.kernel.org/tip/b81d39c7a1efb83caa3f4419939a46e96191abb6
Author:Jiri Olsa
AuthorDate:Tue, 20 Aug 2019 14:46:24 +02:00
Committer:
On Fri, Aug 23, 2019 at 9:54 AM ndrw wrote:
> That's obviously a lot better than hard freezes but I wouldn't call such
> system lock-ups an excellent result. PSI-triggered OOM killer would have
> indeed been very useful as an emergency brake, and IMHO such mechanism
> should be built in the
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 00452ba9fdb5bf6fb5fea1dae5227b4bbed44fc4
Gitweb:
https://git.kernel.org/tip/00452ba9fdb5bf6fb5fea1dae5227b4bbed44fc4
Author:Hans de Goede
AuthorDate:Mon, 12 Aug 2019 12:21:13 +02:00
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: c84b82dd3e593db217f23c60f7edae02c76a3c4c
Gitweb:
https://git.kernel.org/tip/c84b82dd3e593db217f23c60f7edae02c76a3c4c
Author:Cao jin
AuthorDate:Fri, 09 Aug 2019 19:46:12 +08:00
Committer:
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 0bee3b601b77dbe7981b5474ae8758d6bf60177a
Gitweb:
https://git.kernel.org/tip/0bee3b601b77dbe7981b5474ae8758d6bf60177a
Author:Frederic Weisbecker
AuthorDate:Tue, 20 Aug 2019 15:12:23 +02:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: dce3e8fd039cc1b62760b3ad6822cf04c262cd0e
Gitweb:
https://git.kernel.org/tip/dce3e8fd039cc1b62760b3ad6822cf04c262cd0e
Author:Thomas Gleixner
AuthorDate:Mon, 19 Aug 2019 16:31:47 +02:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 3758b0f86ef502e2f342055caef6d2232c2558b7
Gitweb:
https://git.kernel.org/tip/3758b0f86ef502e2f342055caef6d2232c2558b7
Author:Thomas Gleixner
AuthorDate:Mon, 19 Aug 2019 16:31:43 +02:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: ce03f613461642669d6150c405dd28f4bfd54bbb
Gitweb:
https://git.kernel.org/tip/ce03f613461642669d6150c405dd28f4bfd54bbb
Author:Thomas Gleixner
AuthorDate:Mon, 19 Aug 2019 16:31:42 +02:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 68b2c8c1e421096f4b46ac2ac502d25ca067a2a6
Gitweb:
https://git.kernel.org/tip/68b2c8c1e421096f4b46ac2ac502d25ca067a2a6
Author:Julien Grall
AuthorDate:Wed, 21 Aug 2019 10:24:09 +01:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: dd2261ed45aaeddeb77768f291d604179bcab096
Gitweb:
https://git.kernel.org/tip/dd2261ed45aaeddeb77768f291d604179bcab096
Author:Julien Grall
AuthorDate:Wed, 21 Aug 2019 10:24:07 +01:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: ec8f954a40da8cd3d159713b608e901f0cd909a9
Gitweb:
https://git.kernel.org/tip/ec8f954a40da8cd3d159713b608e901f0cd909a9
Author:Thomas Gleixner
AuthorDate:Fri, 02 Aug 2019 07:35:59 +02:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 692117c1f7a6770ed41dd8f277cd9fed1dfb16f1
Gitweb:
https://git.kernel.org/tip/692117c1f7a6770ed41dd8f277cd9fed1dfb16f1
Author:Thomas Gleixner
AuthorDate:Mon, 19 Aug 2019 16:31:46 +02:00
On Thu, Aug 22, 2019 at 09:50:09PM -0400, Joel Fernandes wrote:
> On Thu, Aug 22, 2019 at 08:27:06AM -0700, Paul E. McKenney wrote:
> > On Thu, Aug 22, 2019 at 09:39:55AM -0400, Joel Fernandes wrote:
> > > On Wed, Aug 21, 2019 at 04:33:58PM -0700, Paul E. McKenney wrote:
> > > > On Wed, Aug 21,
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 7cb9a94c158b956f46cf093ed966d0c1e996dddb
Gitweb:
https://git.kernel.org/tip/7cb9a94c158b956f46cf093ed966d0c1e996dddb
Author:Thomas Gleixner
AuthorDate:Mon, 19 Aug 2019 16:31:45 +02:00
On 22/08/2019 18:05, Sasha Levin wrote:
>
> This is the start of the stable review cycle for the 5.2.10 release.
> There are 135 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 22/08/2019 18:18, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.68 release.
> There are 85 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 22/08/2019 18:18, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.140 release.
> There are 71 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 22/08/2019 18:17, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.190 release.
> There are 103 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 22/08/2019 18:18, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.190 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
1 - 100 of 1598 matches
Mail list logo
