于 2019年10月8日 GMT+08:00 上午12:07:05, Chen-Yu Tsai 写到:
>Hi,
>
>On Wed, Oct 2, 2019 at 7:27 PM Icenowy Zheng wrote:
>>
>> AXP813 PMIC has two Vbus maximum value settings -- one is the default
>> value, which is currently the only supported one; the other is the
>> really applied value, which is se
Confirmed the patch works well on Dell XPS 7390 2-in-1 machine.
Tested-by: AceLan Kao
Tuowen Zhao 於 2019年10月8日 週二 上午2:43寫道：
>
> Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> in MTRR. This will cause the system to hang during boot. If possible,
> this bug could be corr
On 10/7/19 6:49 PM, Sasha Levin wrote:
On Mon, Oct 07, 2019 at 04:16:51PM -0700, Guenter Roeck wrote:
On 10/7/19 4:07 PM, Sasha Levin wrote:
On Mon, Oct 07, 2019 at 04:49:51PM +0200, Greg Kroah-Hartman wrote:
On Mon, Oct 07, 2019 at 05:53:55AM -0700, Guenter Roeck wrote:
On 10/6/19 10:18 AM,
On Tue, Oct 8, 2019 at 11:09 AM Icenowy Zheng wrote:
> 于 2019年10月8日 GMT+08:00 上午12:07:05, Chen-Yu Tsai 写到:
> >Hi,
> >
> >On Wed, Oct 2, 2019 at 7:27 PM Icenowy Zheng wrote:
> >>
> >> AXP813 PMIC has two Vbus maximum value settings -- one is the default
> >> value, which is currently the only sup
Jagan Teki writes:
> Hi Heiko,
>
> On Mon, Sep 30, 2019 at 2:51 AM Heiko Stuebner wrote:
>>
>> Hi Jagan,
>>
>> Am Donnerstag, 19. September 2019, 07:28:17 CEST schrieb Jagan Teki:
>> > ROC-PC is not able to boot linux console if PWM2_d is
>> > unattached to any pinctrl logic.
>> >
>> > To be pre
On 19-10-07 15:46:06, Igor Opaniuk wrote:
> From: Igor Opaniuk
>
> After enters one specific role, notify usb phy driver.
>
> Signed-off-by: Li Jun
> Signed-off-by: Igor Opaniuk
> ---
>
> drivers/usb/chipidea/ci.h | 21 ++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
On Mon, Oct 07, 2019 at 11:26:35AM -0700, Linus Torvalds wrote:
> But on x86, if we move the STAC/CLAC out of the low-level copy
> routines and into the callers, we'll have a _lot_ of churn. I thought
> it would be mostly a "teach objtool" thing, but we have lots of
> different versions of it. Not
Hi Jonas,
On Tue, Oct 8, 2019 at 3:33 AM Jonas Karlman wrote:
>
> On 2019-10-07 19:45, Ezequiel Garcia wrote:
> > From: Francois Buergisser
> >
> > The setting of the motion vectors usage and the setting of motion
> > vectors address are currently done under different conditions.
> >
> > When de
On Mon, Oct 07, 2019 at 02:36:33PM -0700, David Gow wrote:
> +config LIST_TEST
> + bool "KUnit Test for Kernel Linked-list stuctures"
I missed this the first time through: typo of "structures"
--
Kees Cook
Hi all,
Today's linux-next merge of the akpm tree got a conflict in:
lib/Kconfig.debug
between commit:
54dc8d00a0be ("drivers: hv: vmbus: Introduce latency testing")
from the hyperv tree and patch:
"kernel-hacking: create submenu for arch special debugging options"
from the akpm tree.
MSI-X vector control's bit 0 is the mask bit, which masks the
corresponding interrupt request, or not. Other reserved bits might be
used for other purpose by device vendors. For example, the values of
Kingston NVMe SSD's MSI-X vector control are neither 0, nor 1, but other
values [1].
The original
On Fri, Oct 04, 2019 at 12:28:12PM -0700, Matthew Wilcox wrote:
> On Wed, Sep 25, 2019 at 06:36:50PM +1000, Dave Chinner wrote:
> > I'm actually working on abstrcting this code from both block size
> > and page size via the helpers below. We ahve need to support block
> > size > page size, and so t
On 10/7/19 10:19 AM, Chen-Yu Tsai wrote:
> On Sun, Aug 25, 2019 at 1:50 AM Samuel Holland wrote:
>>
>> The RSB controller has two registers for controlling interrupt inputs:
>> RSB_INTE, which has bits for each possible interrupt, and the global
>> interrupt enable bit in RSB_CTRL.
>>
>> Currently
Hi,
When I run checkpatch.pl with a patch doing reverting operation, it
reports a false positive error, Should I ignore the error or it's a bug?
0001-Revert-KVM-X86-Fix-setup-the-virt_spin_lock_key-befo.patch
---
ERROR: Please use git
On Fri, Oct 04, 2019 at 11:45:13AM +0200, Borislav Petkov wrote:
> On Tue, Sep 03, 2019 at 05:26:38PM +0300, Jarkko Sakkinen wrote:
> > +/**
> > + * ENCLS_FAULT_FLAG - flag signifying an ENCLS return code is a trapnr
> > + *
> > + * ENCLS has its own (positive value) error codes and also generates
On Fri, Oct 04, 2019 at 03:11:04PM -0700, Roman Gushchin wrote:
> This is a RFC patch, which is not intended to be merged as is,
> but hopefully will start a discussion which can result in a good
> solution for the described problem.
>
> --
>
> We've noticed that the number of dying cgroups on ou
Hi all,
Changes since 20191004:
My fixes tree is empty again.
The hid tree lost its build failure.
The net-next tree gained a semantic conflict against the net tree.
The bpf-next tree gained a conflict against the bpf tree.
The drm-misc tree gained a semantic conflict against the v4l-dvb tree
> -Original Message-
> From: Shawn Guo
> Sent: 2019年10月7日 20:35
> To: Wen He
> Cc: linux-de...@linux.nxdi.nxp.com; Leo Li ; Rob Herring
> ; Mark Rutland ;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org
> Subject: [EXT] Re: [v2 2/2] arm
On Mon, Oct 7, 2019 at 8:29 PM Al Viro wrote:
>
> For x86? Sure, why not... Note, BTW, that for short constant-sized
> copies we *do* STAC/CLAC at the call site - see those
> __uaccess_begin_nospec();
> in raw_copy_{from,to}_user() in the switches...
Yeah, an that code almost ne
Fixes checkpatch.pl warning: do not add new typedefs in
drivers/staging/octeon/octeon-stubs.h:41
Signed-off-by: Wambui Karuga
---
drivers/staging/octeon/octeon-stubs.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/octeon/octeon-stubs.h
b/drivers/stagi
On Mon, Oct 7, 2019 at 9:09 PM Linus Torvalds
wrote:
>
> Try the attached patch, and then count the number of "rorx"
> instructions in the kernel. Hint: not many. On my personal config,
> this triggers 15 times in the whole kernel build (not counting
> modules).
So here's a serious patch that doe
On Mon, Oct 7, 2019 at 9:09 PM Linus Torvalds
wrote:
>
> Try the attached patch, and then count the number of "rorx"
> instructions in the kernel. Hint: not many. On my personal config,
> this triggers 15 times in the whole kernel build (not counting
> modules).
.. and four of them are in perf_ca
On 10/07/2019 07:47 PM, Catalin Marinas wrote:
> On Mon, Sep 23, 2019 at 11:13:45AM +0530, Anshuman Khandual wrote:
>> 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 regio
Some pins crept in that weren't ordered in the list.
Signed-off-by: Andrew Jeffery
---
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c
b/drivers/pinctrl/aspeed/pinc
Hello,
This series resolves several issues found in testing by Johnny Huang from
ASPEED, who also contributed the patches to fix them. We'll have more patches
from him in the near future (which I'm pretty happy about).
The major issue resolved is the way I grouped the eMMC pins. What I had was
ug
Rename SD3 functions and groups to EMMC to better reflect their intended
use before the binding escapes too far into the wild. Also clean up the
SD3 pin groups to eliminate some silliness that slipped through the
cracks (SD3DAT[4-7]) by unifying them into three new groups: EMMCG1,
EMMCG4 and EMMCG8
The I2C function the pin participated in was incorrectly named SDA14
which lead to a failure to mux:
[6.884344] No function I2C14 found on pin 7 (7). Found signal(s) MACLINK4,
SDA14, GPIOA7 for function(s) MACLINK4, SDA14, GPIOA7
Fixes: 58dc52ad00a0 ("pinctrl: aspeed: Add AST2600 pinmux supp
From: Johnny Huang
AST2600 EMMC support 3 types DAT bus sizes (1, 4 and 8-bit),
corresponding to 3 groups: EMMCG1, EMMCG4 and EMMCG8
Fixes: 58dc52ad00a0 ("pinctrl: aspeed: Add AST2600 pinmux support")
Signed-off-by: Johnny Huang
Signed-off-by: Andrew Jeffery
---
drivers/pinctrl/aspeed/pinctrl
From: Johnny Huang
The documentation to configure I3C3/FSI1 and I3C4/FSI2 was initially
unclear.
Fixes: 58dc52ad00a0 ("pinctrl: aspeed: Add AST2600 pinmux support")
Signed-off-by: Johnny Huang
[AJ: Tweak commit message, resolve rebase conflicts]
Signed-off-by: Andrew Jeffery
---
drivers/pinct
Signal descriptors can represent multi-bit bitfields and so have
explicit "enable" and "disable" states. However many descriptor
instances only describe a single bit, and so the SIG_DESC_SET() macro is
provides an abstraction for the single-bit cases: Its expansion
configures the "enable" state to
From: Johnny Huang
When UART13G1 is set the pinmux configuration in SCU4B8 for UART13G0
should be cleared.
Fixes: 58dc52ad00a0 ("pinctrl: aspeed: Add AST2600 pinmux support")
Signed-off-by: Johnny Huang
[AJ: Tweak commit message]
Signed-off-by: Andrew Jeffery
---
drivers/pinctrl/aspeed/pinctr
On Mon, Oct 07, 2019 at 03:04:12PM +0300, Jarkko Sakkinen wrote:
> On Mon, Oct 07, 2019 at 11:10:24AM +0300, Jarkko Sakkinen wrote:
> > Actually, maybe like this:
> >
> > struct sgx_enclave_add_page_desc {
> > __u64 addr;
> > __u64 offset;
> > __u64 secinfo;
> > __u16 mrmas
On Tue, 8 Oct 2019 at 04:41, Andrew Jeffery wrote:
>
> Hello,
>
> This series resolves several issues found in testing by Johnny Huang from
> ASPEED, who also contributed the patches to fix them. We'll have more patches
> from him in the near future (which I'm pretty happy about).
For the series:
On Mon, Oct 07, 2019 at 09:09:14PM -0700, Linus Torvalds wrote:
> > 1) cross-architecture user_access_begin_dont_use(): on everything
> > except x86 it's empty, on x86 - __uaccess_begin_nospec().
>
> No, just do a proper range check, and use user_access_begin()
>
> Stop trying to optimize that r
"mask_ofl_ipi" is used for iterate CPUs which IPIs are needed to send
to, however in the IPI sending loop, "mask_ofl_ipi" along with another
variable "mask_ofl_test" might also get modified to record which CPU's
quiesent state can be reported by sync_rcu_exp_select_node_cpus(). Two
variables seems
On Mon, Oct 07, 2019 at 09:14:51PM -0700, Linus Torvalds wrote:
> On Mon, Oct 7, 2019 at 9:09 PM Linus Torvalds
> wrote:
> >
> > Try the attached patch, and then count the number of "rorx"
> > instructions in the kernel. Hint: not many. On my personal config,
> > this triggers 15 times in the whol
On Mon, Oct 07, 2019 at 03:36:46PM -0700, Guenter Roeck wrote:
> On 10/7/19 7:49 AM, Greg Kroah-Hartman wrote:
> > On Mon, Oct 07, 2019 at 05:53:55AM -0700, Guenter Roeck wrote:
> > > On 10/6/19 10:18 AM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 4.4.196
Hi Ezequiel, Jonas,
On Tue, Oct 8, 2019 at 2:46 AM Ezequiel Garcia wrote:
>
> From: Jonas Karlman
>
> TRM specify supported image size 48x48 to 4096x2304 at step size 16 pixels,
> change frmsize max_width/max_height to match TRM.
>
> Fixes: 760327930e10 ("media: hantro: Enable H264 decoding on r
On Mon, Oct 7, 2019 at 9:53 PM Colin King wrote:
>
> From: Colin Ian King
>
> Don't populate const arrays on the stack but instead make them
> static. Makes the object code smaller by 60 bytes.
>
> Before:
>textdata bss dec hex filename
> 151338768 0 239015d5
On Tue, Oct 08, 2019 at 03:06:31PM +1100, Dave Chinner wrote:
> On Fri, Oct 04, 2019 at 03:11:04PM -0700, Roman Gushchin wrote:
> > This is a RFC patch, which is not intended to be merged as is,
> > but hopefully will start a discussion which can result in a good
> > solution for the described prob
HI,
On 07-10-2019 23:52, Arvind Sankar wrote:
On Mon, Oct 07, 2019 at 10:31:49PM +0200, Hans de Goede wrote:
HI,
On 07-10-2019 22:05, Nathan Chancellor wrote:
On Mon, Oct 07, 2019 at 07:55:46PM +0200, Hans de Goede wrote:
Since we link purgatory.ro with -r aka we enable "incremental linking"
On Mon, Oct 07, 2019 at 10:31:50PM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> (Re-send for Maxime, with already applied patches dropped. Nothing new.)
>
> This series implements bluetooth support for Xunlong Orange Pi 3 board.
>
> The board uses AP6256 WiFi/BT 5.0 chip.
>
> Summary
On 2019/10/4 21:46, James Clark wrote:
> Hi Xiaojun,
>
> I wanted to ask if you are still working on this?
>
> I've noticed that it doesn't apply cleanly to perf/core anymore and I was
> working on re-basing it.
> Would you be interested in me posting my progress?
>
> I was also interested in d
On 19-10-07 19:29, Mark Brown wrote:
> On Mon, Oct 07, 2019 at 11:34:29AM +0200, Marco Felsch wrote:
>
> > Sorry that won't fix my problem. If I drop the regulator-boot-on state
> > the fixed-regulator will disable this regulator but disable/enable this
> > regulator is only valid during suspend/r
Follow-up for commit fddbfeece9c7 ("iwlwifi: fw: don't send
GEO_TX_POWER_LIMIT command to FW version 36"). There is no
GEO_TX_POWER_LIMIT command support for all revisions of FW version
29, either.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204151
Signed-off-by: You-Sheng Yang
---
dri
On Mon, 07 Oct 2019, Krzysztof Kozlowski wrote:
> On Mon, 7 Oct 2019 at 18:09, Alex Deucher wrote:
>>
>> On Mon, Oct 7, 2019 at 7:39 AM Jani Nikula
>> wrote:
>> >
>> > On Fri, 04 Oct 2019, Krzysztof Kozlowski wrote:
>> > > drivers/gpu/drm/i915/Kconfig | 12 +-
>> > > drivers/gpu/
On Tue, Oct 08, 2019 at 08:59:44AM +1100, Dave Chinner wrote:
> On Sun, Oct 06, 2019 at 05:46:06PM +0200, Christoph Hellwig wrote:
> > In preparation for moving the writeback code to iomap.c, replace the
> > XFS-specific COW fork concept with the iomap IOMAP_F_SHARED flag.
>
> "In preparation for
On 10/07/19 11:14, Dietmar Eggemann wrote:
> On 23/09/2019 13:52, Qais Yousef wrote:
> > On 09/20/19 14:52, Dietmar Eggemann wrote:
> >>> 2. The fallback mechanism means we either have to call cpupri_find()
> >>> twice once to find filtered lowest_rq and the other to return the
> >>> no
On Mon, 2019-10-07 at 15:33 +0200, Dmitry Vyukov wrote:
> On Mon, Oct 7, 2019 at 2:33 PM Walter Wu wrote:
> > On Mon, 2019-10-07 at 14:19 +0200, Dmitry Vyukov wrote:
> > > On Mon, Oct 7, 2019 at 2:03 PM Walter Wu
> > > wrote:
> > > My idea was just to always print "heap-out-of-bounds" and don't
On 2019.10.06 08:34 Rafael J. Wysocki wrote:
> On Sun, Oct 6, 2019 at 4:46 PM Doug Smythies wrote:
>> On 2019.10.01 02:32 Rafael J. Wysocki wrote:
>>> On Sun, Sep 29, 2019 at 6:05 PM Doug Smythies wrote:
On 2019.09.26 09:32 Doug Smythies wrote:
> If the deepest idle state is disable
On Mon, 07 Oct 2019 10:17:20 +0200
Peter Zijlstra wrote:
> Provide a simple helper function to create common instruction
> encodings.
Thanks for using correct INSN_OPCODE:)
This looks good to me.
Reviewed-by: Masami Hiramatsu
Thanks,
>
> Signed-off-by: Peter Zijlstra (Intel)
> Cc: Steven R
On 2019-10-08 05:29, Tomasz Figa wrote:
> Hi Jonas,
>
> On Tue, Oct 8, 2019 at 3:33 AM Jonas Karlman wrote:
>> On 2019-10-07 19:45, Ezequiel Garcia wrote:
>>> From: Francois Buergisser
>>>
>>> The setting of the motion vectors usage and the setting of motion
>>> vectors address are currently done
From: Guo Ren
We should give some necessary check for initrd just like other
architectures and it seems that setup_initrd() could be a common
code for all architectures.
Signed-off-by: Guo Ren
---
arch/csky/kernel/setup.c | 3 ---
arch/csky/mm/init.c | 44
On Tue, Oct 8, 2019 at 1:30 AM Guenter Roeck wrote:
> m68k:
>
> c2p_iplan2.c:(.text+0x98): undefined reference to `c2p_unsupported'
>
> I don't know the status.
Fall-out from the (non)inline optimization. Patch available:
https://lore.kernel.org/lkml/20190927094708.11563-1-ge...@linux-m68k.org/
On 2019-10-08 07:27, Tomasz Figa wrote:
> Hi Ezequiel, Jonas,
>
> On Tue, Oct 8, 2019 at 2:46 AM Ezequiel Garcia wrote:
>> From: Jonas Karlman
>>
>> TRM specify supported image size 48x48 to 4096x2304 at step size 16 pixels,
>> change frmsize max_width/max_height to match TRM.
>>
>> Fixes: 760327
On Tue, Oct 08, 2019 at 08:43:53AM +1100, Dave Chinner wrote:
> > +static int
> > +iomap_ioend_compare(void *priv, struct list_head *a, struct list_head *b)
> > +{
> > + struct iomap_ioend *ia, *ib;
> > +
> > + ia = container_of(a, struct iomap_ioend, io_list);
> > + ib = container_of(b, stru
On 07. 10. 19 20:15, Saurav Girepunje wrote:
> Use true/false assignment for below bool variables in udc-xilinx.c:
>
> bool buffer0ready;
> bool buffer1ready;
> bool is_in;
> bool is_iso;
>
> Signed-off-by: Saurav Girepunje
> ---
> drivers/usb/gadget/udc/udc-xilinx.c | 36 ++
I'm announcing the release of the 4.4.196 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 721fa569a680..9eaf50527883 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 195
+SUBLEVEL = 196
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
index 0d20cd594017..7
I'm announcing the release of the 4.9.196 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.148 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Makefile b/Makefile
index bee0218e3fb5..194c35eff19c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 195
+SUBLEVEL = 196
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
index 5ca207ada852..253
diff --git a/Makefile b/Makefile
index d6f1a056b233..feecefa13ca6 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 147
+SUBLEVEL = 148
EXTRAVERSION =
NAME = Petit Gorille
diff --git a/arch/arm/mm/fault.c b/arch/ar
diff --git a/Makefile b/Makefile
index aeabc6459acc..440c5b5c4f4b 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 77
+SUBLEVEL = 78
EXTRAVERSION =
NAME = "People's Front"
diff --git a/arch/arm/Kconfig b/arch/arm/
I'm announcing the release of the 5.2.20 kernel.
All users of the 5.2 kernel series must upgrade.
Note, this is the LAST 5.2 kernel to be released, it is now end-of-life.
You must move to the 5.3.y kernel series at this point in time.
The updated 5.2.y git tree can be found at:
git://git
I'm announcing the release of the 4.19.78 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 5.3.5 kernel.
All users of the 5.3 kernel series must upgrade.
The updated 5.3.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.3.y
and can be browsed at the normal kernel.org git web browser:
Hi all,
On 2019/10/2 16:55, Petr Mladek wrote:
> Linus,
>
> On Fri 2019-09-20 14:25:12, Kefeng Wang wrote:
>> There are pr_warning and pr_warng to show WARNING level message,
>> most of the code using pr_warn, number based on next-20190919,
>>
>> pr_warn: 5189 pr_warning: 546 (tools: 398, other
On Tue, Oct 08, 2019 at 08:54:24AM +1100, Dave Chinner wrote:
> > + if (whichfork == XFS_COW_FORK)
> > + flags |= IOMAP_F_SHARED;
>
> That seems out of place - I don't see anywhere in this patch that
> moves/removes setting the IOMAP_F_SHARED flag. i.e this looks like a
> change of beh
On 2019/9/4 20:20, David Howells wrote:
> Thanks, I've folded that in.
This issue still occur in linux-next 20191008 :
drivers/misc/watch_queue.c: In function ‘watch_queue_account_mem’:
drivers/misc/watch_queue.c:315:38: error: ‘struct user_struct’ has no member
named ‘locked_vm’; did you mean ‘
Add suitable additional cc's as Andrew Morton suggested.
Get cc list from get_maintainer script:
[root@localhost mm]# ./scripts/get_maintainer.pl
0001-proc-fix-confusing-macro-arg-name.patch
Alexey Dobriyan (reviewer:PROC FILESYSTEM)
linux-kernel@vger.kernel.org (open list:PROC FILESYSTEM)
linux
From: Guo Ren
Add mailing list and it's convenient for maintain C-SKY
subsystem.
Signed-off-by: Guo Ren
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 55199ef..d8fc16d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3556,6 +3556,7 @@ F:
On Mon, 2019-10-07 at 15:40 +0530, Manivannan Sadhasivam wrote:
> [External]
>
Hey,
Comments inline.
I thought I sent an initial review, but seems to have gotten lost [maybe in
my email client].
Oh well. I managed to re-do it anyway.
I tried to group them this time.
The more prominent part is
On Mon, 2019-10-07 at 22:16 +0100, Jonathan Cameron wrote:
> On Sun, 6 Oct 2019 10:12:01 +0100
> Jonathan Cameron wrote:
>
> > On Thu, 26 Sep 2019 14:18:04 +0300
> > Alexandru Ardelean wrote:
> >
> > > This will allow more flexible control to group reads & writes into a
> > > single
> > > lock
On 07/10/19 21:54, Sean Christopherson wrote:
>> For QEMU, we're defining a feature as supported if a feature can be
>> turned both on and off. Since msr_low and msr_high can be defined
>> respectively as must-be-one and can-be-one, the features become
>> "msr_high & ~msr_low".
>
> That makes sen
On 07/10/19 21:56, Sean Christopherson wrote:
> On Mon, Oct 07, 2019 at 07:12:37PM +0200, Paolo Bonzini wrote:
>> On 04/10/19 23:56, Sean Christopherson wrote:
>>> diff --git a/arch/x86/kernel/cpu/proc.c b/arch/x86/kernel/cpu/proc.c
>>> index cb2e49810d68..4eec8889b0ff 100644
>>> --- a/arch/x86/ker
On 19-10-07 07:39:11, Pawel Laszczak wrote:
> Patch fixes issue with Halt Endnpoint Test observed
%s/Endnpoint/Endpoint
>
> during using g_zero
> driver as DUT. Bug occurred only on some testing board.
g_zero is legacy, please use configfs function source_sink or loopback
instead.
>
> Endpoint
On Mon, Oct 07, 2019 at 10:17:03AM -0500, Benoit Parrot wrote:
> Sakari Ailus wrote on Mon [2019-Oct-07
> 11:03:20 +0300]:
> > On Fri, Oct 04, 2019 at 12:24:16PM -0500, Benoit Parrot wrote:
> > > @@ -2657,6 +2669,12 @@ static int ov5640_init_controls(struct ov5640_dev
> > > *sensor)
> > > /* w
On Mon, Oct 07, 2019 at 07:07:38AM +0100, Chris Clayton wrote:
> Just built and installed -rc2 and get the following when depmod is run.
>
> depmod: WARNING: /lib/modules/5.4.0-rc2/kernel/drivers/usb/storage/uas.ko
> needs unknown symbol usb_stor_sense_invalidCDB
> depmod: WARNING: /lib/modules/
slow_copyfile() opens the file by name, so "write" permissions must not
be removed in copyfile_mode_ns() before calling slow_copyfile().
Example:
Before:
$ sudo chmod +r /proc/kcore
$ sudo setcap "cap_sys_admin,cap_sys_ptrace,cap_syslog,cap_sys_rawio=ep"
tools/perf/perf
$ tools/perf/perf
On Fri, 4 Oct 2019 at 17:00, Krzysztof Kozlowski wrote:
>
> Sync with exynos_defconfig and enable following options for Samsung
> Exynos SoC based boards:
> 1. NFC_S3FWRN5_I2C (with NFC stack): Samsung S3FWRN5 NCI NFC Controller,
>used for example on Exynos5433 (if booted in 32-bit mode),
> 2.
Add missing configuration for mt7629 gmii mode support
Fixes: 7e538372694b ("net: ethernet: mediatek: Re-add support SGMII")
Signed-off-by: MarkLee
--
v1->v2:
* no change
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/medi
* Removes mediatek,physpeed property from dtsi that is useless in PHYLINK
* Use the fixed-link property speed = <2500> to set the phy in 2.5Gbit.
* Set gmac1 to gmii mode that connect to a internal gphy
Signed-off-by: MarkLee
--
v1->v2:
* SGMII port only support BASE-X at 2.5Gbit.
---
arch/arm/b
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204793
Kdump kernel will reuse the first 640k region because of some reasons,
for example: the trampline and conventional PC system BIOS region may
require to allocate memory in this area. Obviously, kdump kernel will
also overwrite the first 6
This patch target to update mt7629 eth driver and dts to support PHYLINK
MarkLee (2):
net: ethernet: mediatek: Fix MT7629 missing GMII mode support
arm: dts: mediatek: Fix mt7629 dts to reflect the latest dt-binding
arch/arm/boot/dts/mt7629-rfb.dts| 13 -
arch/arm/boo
Add an interface for other driver to query VPD value.
This will be used for ASoC machine driver to query calibration
data stored in VPD for smart amplifier speaker resistor
calibration.
Signed-off-by: Cheng-Yi Chiang
---
drivers/firmware/google/vpd.c | 16
include/l
Below is the list of build error/warning regressions/improvements in
v5.4-rc2[1] compared to v5.3[2].
Summarized:
- build errors: +10/-3
- build warnings: +152/-143
JFYI, when comparing v5.4-rc2[1] to v5.4-rc1[3], the summaries are:
- build errors: +5/-10
- build warnings: +44/-133
Note
Hi,
I bisected an issue down to commit f7fac17ca925 "xhci: Convert
xhci_handshake() to use readl_poll_timeout_atomic()".
Setup:
XPS 9370 + Thunderbolt dock Dell TB16
Issue:
The laptop is unable to go to sleep. It never really goes to sleep and
after a few seconds the USB dies.
Log:
https://
From: Frieder Schrempf
Later versions of the QSPI controller (e.g. in i.MX6UL/ULL and i.MX7)
seem to have an additional TDH setting in the FLSHCR register, that
needs to be set in accordance with the access mode that is used (DDR
or SDR).
Previous bootstages such as BootROM or bootloader might h
On Mon, Oct 7, 2019 at 5:23 AM Walter Wu wrote:
> > > > > > "out-of-bounds" is the _least_ frequent KASAN bug type. So saying
> > > > > > "out-of-bounds" has downsides of both approaches and won't prevent
> > > > > > duplicate reports by syzbot...
> > > > > >
> > > > > maybe i should add your comm
Hi Chris,
CC MarcZ
On Thu, Oct 3, 2019 at 2:03 AM Chris Packham
wrote:
> Use the dev_name(dev) for the irqc->name so that we get unique names
> when we have multiple instances of this driver.
>
> Signed-off-by: Chris Packham
A while ago, Marc Zyngier pointed out that the irq_chip .name field
s
On 10/5/19 7:30 PM, William Breathitt Gray wrote:
> On Wed, Sep 25, 2019 at 10:51:26AM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> There is an if statement that is indented one level too deeply,
>> remove the extraneous tabs.
>>
>> Signed-off-by: Colin Ian King
>> ---
>> drivers/count
On Mon, Oct 7, 2019 at 1:52 AM Christian Brauner
wrote:
>
> When assiging and testing taskstats in taskstats_exit() there's a race
> when writing and reading sig->stats when a thread-group with more than
> one thread exits:
>
> cpu0:
> thread catches fatal signal and whole thread-group gets taken
On Mon, Oct 7, 2019 at 9:20 AM Geert Uytterhoeven wrote:
> JFYI, when comparing v5.4-rc2[1] to v5.4-rc1[3], the summaries are:
> - build errors: +5/-10
+ /kisskb/src/drivers/staging/octeon/ethernet-defines.h: error:
'CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE' undeclared (first use in this
function):
Hi Adrian,
On 3/10/2019 3:46 PM, Ramuthevar, Vadivel MuruganX wrote:
Hi Adrian,
Thank you for the comments.
On 3/10/2019 3:02 PM, Adrian Hunter wrote:
On 3/10/19 7:00 AM, Ramuthevar,Vadivel MuruganX wrote:
From: Ramuthevar Vadivel Murugan
The current arasan sdhci PHY configuration isn't
Hi Arvind,
can you try the patch below?
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index 3f974919d3bd..52b709bf2b55 100644
--- a/drivers/iommu/intel-iommu.c
+++ b/drivers/iommu/intel-iommu.c
@@ -3775,6 +3775,13 @@ static int intel_map_sg(struct device *dev, struct
sc
If the rproc driver is probed before the mailbox driver and if the rproc
Device Tree node has some mailbox properties, the rproc driver probe
shall be deferred instead of being probed without mailbox support.
Signed-off-by: Fabien Dessenne
---
Changes since v1: test IS_ERR() before checking PTR_E
Hi Rob,
On 18/9/2019 10:23 AM, Ramuthevar, Vadivel MuruganX wrote:
Hi Rob,
Thank you for the review comments.
On 17/9/2019 10:23 PM, Rob Herring wrote:
On Wed, Sep 04, 2019 at 01:53:43PM +0800, Ramuthevar,Vadivel MuruganX
wrote:
From: Ramuthevar Vadivel Murugan
Add a YAML schema to use th
On Sun, Oct 06, 2019 at 03:45:13PM -0300, jcfara...@gmail.com wrote:
> From: Julio Faracco
>
> Driver virtio_net is not handling error events for TX provided by
> dev_watchdog. This event is reached when transmission queue is having
> problems to transmit packets. To enable it, driver should ha
On Sun, Oct 06, 2019 at 03:45:15PM -0300, jcfara...@gmail.com wrote:
> From: Julio Faracco
>
> To enable dev_watchdog, virtio_net should have a tx_timeout defined
> (.ndo_tx_timeout). This is only a skeleton to throw a warn message. It
> notifies the event in some specific queue of device. This
301 - 400 of 1238 matches
Mail list logo
