On Sun, 13 Jan 2019 at 20:58, Paweł Chmiel
wrote:
>
> There is possibility, that when probing driver, regulators are not yet
> initialized. In this case we should return EPROBE_DEFER and wait till
> they're initialized, since they're required currently for cpufreq driver
> to work. Also move
y...@hpe.com:
550 5.1.1 User Unknown
You are sending e-mails/patches from a non-existant address?
On 14. 01. 19, 7:56, y...@hpe.com wrote:
> From: Li RongQing
>
> when fail to open tty, tty is not in open status and not need
> to call close
But tty drivers are special and expect close even
Hi Pingfan,
On Fri, Jan 11, 2019 at 01:12:53PM +0800, Pingfan Liu wrote:
> During boot time, there is requirement to tell whether a series of func
> call will consume memory or not. For some reason, a temporary memory
> resource can be loan to those func through memblock allocator, but at a
>
On Mon, Jan 14, 2019 at 09:14:59AM +0200, Joel Nider wrote:
> While using this guide to learn the new documentation method, I saw
> a few phrases that I felt could be improved. These small changes
> improve the grammar and choice of words to further enhance the
> installation instructions.
>
>
Hello,
The file “/proc/sys/kernel/random/uuid” provides a bit of useful data.
The formal definition of the string representation for universally unique
identifiers requires the use of four dashes for the concatenation of fields.
https://tools.ietf.org/html/rfc4122#page-4
On Fri, Jan 11, 2019 at 11:16:38PM +0100, Daniel Vetter wrote:
> On Fri, Jan 11, 2019 at 11:06:20PM +0100, Daniel Vetter wrote:
> > On Fri, Jan 11, 2019 at 09:02:34AM -0500, Rob Clark wrote:
> > > This fixes an '*ERROR* connector VGA-2 leaked!' splat at driver unload.
> > >
> > > Signed-off-by:
From d6892f54a81bf85ad011bfb8822567690713d575 Mon Sep 17 00:00:00 2001
When the return code of "-ENOENT" was printed inside
of the debug message, which could be hardcoded simply.
Signed-off-by: John Zhao
---
drivers/base/firmware_loader/main.c | 8
1 file changed, 4 insertions(+), 4
Joe Lawrence writes:
> On Fri, Jan 11, 2019 at 08:51:54AM +0100, Nicolai Stange wrote:
>> Joe Lawrence writes:
>>
>> > On Fri, Jan 11, 2019 at 01:00:38AM +0100, Nicolai Stange wrote:
>
> [ ... snip ... ]
>
>> >> For testing, could you try whether clearing the word at STACK_FRAME_MARKER
>> >>
Hello,
syzbot found the following crash on:
HEAD commit:4b3c31c8d4dd Merge branch 'i2c/for-current' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=144cb81740
kernel config: https://syzkaller.appspot.com/x/.config?x=b05cfdb4ee8ab9b2
Hello,
syzbot found the following crash on:
HEAD commit:8d008e64a2eb mISDN: hfcsusb: Use struct_size() in kzalloc()
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=164f010740
kernel config: https://syzkaller.appspot.com/x/.config?x=7308e68273924137
On Mon, 14 Jan 2019, Pavel Machek wrote:
> On Wed 2019-01-09 07:20:18, Lee Jones wrote:
> > Good morning Linus,
> >
> > Please accept my apologies for the lateness.
>
> I'd say that for 5.1, you are pretty early :-).
Ha ha! Yes, indeed. It seems sending late messes with the brain!
Ideally
On Wed, 09 Jan 2019, Lee Jones wrote:
> Good morning Linus,
>
> Please accept my apologies for the lateness.
This should be v5.0 of course.
Sending late seems to mess with the brain.
> Christmas holidays, yada yada yada! :)
>
> The following changes since commit
Hi Dan,
On 12-Jan-19 5:29 AM, Dan Williams wrote:
The _DSM function number validation only happens to succeed when the
generic Linux command number translation corresponds with a
DSM-family-specific function number. This breaks NVDIMM-N
implementations that correctly implement _LSR, _LSW, and
On 14. 01. 19, 7:56, y...@hpe.com wrote:
> From: Li RongQing
>
> when fail to open tty, tty is not in open status and not need
> to call close
But tty drivers are special and expect close even on failed open, right?
See tty_open.
> Signed-off-by: Li RongQing
> ---
>
> > Until you have images (and hence host page cache) shared between
> > multiple guests. People will want to do this, because it means they
> > only need a single set of pages in host memory for executable
> > binaries rather than a set of pages per guest. Then you have
> > multiple guests
While using this guide to learn the new documentation method, I saw
a few phrases that I felt could be improved. These small changes
improve the grammar and choice of words to further enhance the
installation instructions.
Signed-off-by: Joel Nider
Acked-by: Matthew Wilcox
---
v2: address
On Mon 14-01-19 09:30:55, Anshuman Khandual wrote:
>
>
> On 01/13/2019 11:05 PM, Michal Hocko wrote:
> > On Sat 12-01-19 15:56:38, Anshuman Khandual wrote:
> >> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL |
> >> __GFP_ZERO) and using it for allocating page table
Hi Matthias,
Gentle ping about this and the other mtk-smi part in this patchset.
The memory part don't have its specific maintainer, normally we need
SoC maintain's help. Thus, For this file(memory/mtk-smi.c), your review
is needed before Joerg accept it.
Appreciate in advance.
On
From: Li RongQing
when fail to open tty, tty is not in open status and not need
to call close
Signed-off-by: Li RongQing
---
drivers/tty/serdev/serdev-ttyport.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/tty/serdev/serdev-ttyport.c
On Mon, Jan 14, 2019 at 7:52 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1492759f40
> kernel config:
On Sat, Dec 29, 2018 at 10:35:14AM -0800, Deepa Dinamani wrote:
> The usec part of the timeval is defined as
> __kernel_suseconds_t tv_usec; /* microseconds */
>
> Arnd noticed that sparc64 is the only architecture
> that defines __kernel_suseconds_t as int rather than long.
>
> This breaks the
On Sat, Jan 05, 2019 at 10:39:07AM +0530, Brajeswar Ghosh wrote:
> Remove linux/kernel.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Applied, thank you.
> ---
> drivers/input/keyboard/mtk-pmic-keys.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
Hello,
syzbot found the following crash on:
HEAD commit:b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1492759f40
kernel config: https://syzkaller.appspot.com/x/.config?x=b03c5892bb940c76
We have a supercomputer site testing nohz_full to reduce jitter with
good results, but they want CPU0 to be nohz_full. That happens to be
the boot CPU, which is disallowed by the nohz_full code.
They have existing job scheduling code which wants this, I don't know
too much detail beyond that, but
On Sun, Jan 13, 2019 at 7:32 PM Olof Johansson wrote:
>
> Since we now build with -Wvla, any use of VLA throws a warning.
> Including this test, so... maybe we should just remove the test?
>
> lib/test_ubsan.c: In function 'test_ubsan_vla_bound_not_positive':
> lib/test_ubsan.c:48:2: warning: ISO
On Thursday 03 January 2019 07:17 PM, Christian Hohnstaedt wrote:
> These options apply to all regulators in this chip.
>
> ti,strict-supply-voltage-supervision:
> Set STRICT flag in CONFIG1
> ti,under-voltage-limit-microvolt:
> Select 2.75, 2.95, 3.25 or 3.35 V UVLO in CONFIG1
>
On Tue, Jan 08, 2019 at 03:15:56PM -0600, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for some number of elements for that array. For example:
>
> struct
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 11:52 PM, Douglas Gilbert
wrote:
> On 2019-01-13 10:59 p.m., Esme wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Sunday, January 13, 2019 10:52 PM, Douglas Gilbert dgilb...@interlog.com
> > wrote:
> >
> > > On 2019-01-13 10:07
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-pci-idio-16.c | 75 -
1 file changed, 28 insertions(+), 47
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-pcie-idio-24.c | 111 ---
1 file changed, 42 insertions(+), 69
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-ws16c48.c | 72 +++--
1 file changed, 20 insertions(+), 52
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-gpio-mm.c | 73 +++--
1 file changed, 22 insertions(+), 51
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-104-dio-48e.c | 73 ++---
1 file changed, 22 insertions(+), 51
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump8 macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-104-idi-48.c | 37 --
1 file changed, 8 insertions(+), 29
The introduction of the for_each_set_clump8 macro warrants test cases to
verify the implementation. This patch adds test case checks for whether
an out-of-bounds clump index is returned, a zero clump is returned, or
the returned clump value differs from the expected clump value.
Cc: Andy
This macro iterates for each 8-bit group of bits (clump) with set bits,
within a bitmap memory region. For each iteration, "start" is set to the
bit offset of the found clump, while the respective clump value is
stored to the location pointed by "clump". Additionally, the
bitmap_get_value8 and
Ping...
BR
Jacky Bai
> -Original Message-
> From: Jacky Bai
> Sent: 2018年12月12日 13:28
> To: daniel.lezc...@linaro.org; t...@linutronix.de; robh...@kernel.org;
> shawn...@kernel.org; mark.rutl...@arm.com; Aisheng Dong
>
> Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org;
Changes in v8:
- Return unsigned long for bitmap_get_value8 for consistency
- Add clobbering risk warning to bitmap_set_value8 documentation
- Reimplement bitmap_get_value8 and bitmap_set_value8 to account for
clumps that fall across bitmap word boundaries
- Add a bitmap size argument
On 1/8/2019 2:34 AM, Stephen Boyd wrote:
Quoting Taniya Das (2019-01-06 22:26:00)
Hello Stephen,
On 12/21/2018 2:34 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-12-20 03:46:25)
The LPASS clocks has a dependency on the GCC lpass clocks to be enabled
before accessing them and that was
This shows up in the index of https://www.kernel.org/doc/html/latest/ so
I figured it should be updated.
Fixes: bfeffd15528 ("Linux 5.0-rc1")
Signed-off-by: Joel Stanley
--
We could also remove the version number instead of applying this patch.
---
Documentation/admin-guide/README.rst | 5 +++--
On 11-01-19, 11:58, Matthias Kaehlcke wrote:
> On Fri, Jan 11, 2019 at 09:16:53AM +0530, Viresh Kumar wrote:
> Just to gain a better understanding: is cpuidle cooling already
> available for arm64 (or is there a patch set)? I came across the
> relatively new idle injecting framework but it seems
On (01/11/19 17:20), Petr Mladek wrote:
> The commit 97f5f0cd8cd0a0544 ("Input: implement SysRq as a separate input
> handler") added pr_fmt() definition. It caused a duplicated message
> prefix in the sysrq header messages, for example:
>
> [ 177.053931] sysrq: SysRq : Show backtrace of all
Hi Jae,
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
>
> This commit adds PECI bus/adapter node of AST24xx/AST25xx into
> aspeed-g4 and aspeed-g5.
This looks good, aside from the alias.
It will go via my aspeed tree once the bindings are merged. Send them
to linux-asp...@lists.ozlabs.org
Thanks Stephen's help.
Ching Huang
Stephen Rothwell 於 2019年1月14日 週一 上午10:48寫道：
>
> Hi all,
>
> Today's linux-next merge of the scsi tree got a conflict in:
>
> drivers/scsi/arcmsr/arcmsr_hba.c
>
> between commit:
>
> 750afb08ca71 ("cross-tree: phase out dma_zalloc_coherent()")
>
> from
On (01/11/19 16:32), Petr Mladek wrote:
> The same problem is with the sysrq header line. It uses the trick
> with console_loglevel by intention. We want to show it but
> it is not really an error message
May be.
I usually see it as an "error".
My case:
systemd sets sysrq on every boot to
ping?
also adding Mr. Corbet.
On 11/1/18 4:41 PM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kernel-doc warning for missing struct member description:
>
> ../include/linux/w1.h:281: warning: Function parameter or member
> 'of_match_table' not described in 'w1_family'
>
>
On Tue, 8 Jan 2019 at 08:11, Jae Hyun Yoo wrote:
>
> This commit adds a document of generic PECI bus, adapter and client
> driver.
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Andrew Jeffery
> Cc: Joel Stanley
> Signed-off-by: Jae Hyun Yoo
> Reviewed-by: Haiyue Wang
> Reviewed-by: James
Hi Joerg,
Thanks for reviewing my patch.
On 1/11/19 7:16 PM, Joerg Roedel wrote:
Hi,
this looks a bit confusing to me because I can see no checking whether
the device actually supports scalable mode.
Yes. I should put some checking there. Device scalable mode capability
is exposed in PCI
在 2019年01月11日 22:56, Borislav Petkov 写道:
> On Thu, Jan 10, 2019 at 08:19:43PM +0800, Lianbo Jiang wrote:
>> This document lists some variables that export to vmcoreinfo, and briefly
>> describles what these variables indicate. It should be instructive for
>> many people who do not know the
cpu_possible(cpu) will always return true when cpu parameter
is from cpumask_next().
Check for nr_cpu_ids rather than !cpu_possible(cpu).
Signed-off-by: Bharat Bhushan
---
drivers/soc/fsl/dpio/dpio-driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This updates bindings for the MT7629 SPI-NOR controller.
Signed-off-by: Ryder Lee
Reviewed-by: Rob Herring
---
Changes since v1: add a Reviewed-by tag.
---
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Guochun Mao
SNOR_HWCAPS_READ is a basic read mode for both flash and controller,
it should be supported, so add the capcity for mtk-quadspi.
Signed-off-by: Guochun Mao
---
Changes since v1: none.
---
drivers/mtd/spi-nor/mtk-quadspi.c | 3 ++-
1 file changed, 2 insertions(+), 1
The quadspi is a generic communication interface which could be shared
with other MediaTek SoCs. Hence rename it to a common one.
Signed-off-by: Ryder Lee
---
Changes since v1: rebase to v5.0-rc1.
---
drivers/mtd/spi-nor/Kconfig | 16
drivers/mtd/spi-nor/Makefile | 2 +-
2
On Fri, Jan 11, 2019 at 10:50:11AM -0500, Alan Stern wrote:
> On Fri, 11 Jan 2019, Paul Elder wrote:
>
> > On Wed, Jan 09, 2019 at 02:06:31PM -0500, Alan Stern wrote:
> > > On Wed, 9 Jan 2019, Paul Elder wrote:
> > >
> > > > A usb gadget function driver may or may not want to delay the status
>
Hi all,
Changes since 20190111:
The vfs tree still had its build failure for which I applied a patch.
It also gained conflicts against the vfs-fixes tree.
The mali-dp tree gained a build failure so I used the version from
next-20190111.
The scsi tree gained conflicts against Linus' and the
Hi Tom,
On Fri, Jan 11, 2019 at 10:25:40AM -0600, Tom Zanussi wrote:
> Hi Namhyung,
>
> On Fri, 2019-01-11 at 15:07 +0900, Namhyung Kim wrote:
> > On Wed, Jan 09, 2019 at 01:49:17PM -0600, Tom Zanussi wrote:
> > > From: Tom Zanussi
> > >
> > > Add a 'trace(synthetic_event_name, params)'
On Sun, Jan 13, 2019 at 08:54:35PM -0800, Bart Van Assche wrote:
> On 1/13/19 8:42 PM, Nathan Chancellor wrote:
> > @@ -1292,7 +1292,7 @@ int esas2r_ioctl_handler(void *hostdata, int cmd,
> > void __user *arg)
> > ioctl = memdup_user(arg, sizeof(struct atto_express_ioctl));
> > if
On 1/13/19 8:42 PM, Nathan Chancellor wrote:
@@ -1292,7 +1292,7 @@ int esas2r_ioctl_handler(void *hostdata, int cmd, void
__user *arg)
ioctl = memdup_user(arg, sizeof(struct atto_express_ioctl));
if (IS_ERR(ioctl)) {
esas2r_log(ESAS2R_LOG_WARN,
-
On 2019-01-13 10:59 p.m., Esme wrote:
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 10:52 PM, Douglas Gilbert
wrote:
On 2019-01-13 10:07 p.m., Esme wrote:
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 9:33 PM, Qian Cai c...@lca.pw wrote:
On 1/13/19 9:20 PM,
Clang warns several times in the scsi subsystem (trimmed for brevity):
drivers/scsi/hpsa.c:6209:7: warning: overflow converting case value to
switch condition type (2147762695 to 18446744071562347015) [-Wswitch]
case CCISS_GETBUSTYPES:
^
drivers/scsi/hpsa.c:6208:7: warning:
> On Dec 29, 2018, at 10:35 AM, Deepa Dinamani wrote:
>
> The usec part of the timeval is defined as
> __kernel_suseconds_ttv_usec; /* microseconds */
>
> Arnd noticed that sparc64 is the only architecture
> that defines __kernel_suseconds_t as int rather than long.
>
> This breaks the
On Sat, Jan 5, 2019 at 12:50 AM Souptick Joarder wrote:
>
> This code is converted to use vmf_error().
>
> Signed-off-by: Souptick Joarder
Any comment on this patch ?
> ---
> fs/dax.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index
On 01/12/2019 09:19 PM, Matthew Wilcox wrote:
> On Sat, Jan 12, 2019 at 02:49:29PM +0100, Christophe Leroy wrote:
>> As far as I can see,
>>
>> #define GFP_KERNEL_ACCOUNT (GFP_KERNEL | __GFP_ACCOUNT)
>>
>> So what's the difference between:
>>
>> (GFP_KERNEL_ACCOUNT | __GFP_ZERO) &
Hi,
Just fix a few of the commit log comments...
On 1/13/19 7:15 PM, Pingfan Liu wrote:
> People reported a bug on a high end server with many pcie devices, where
> kernel bootup with crashkernel=384M, and kaslr is enabled. Even
> though we still see much memory under 896 MB, the finding still
Hi all,
After merging the net tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
ld: warning: orphan section `.bpfilter_umh' from
`net/bpfilter/bpfilter_umh_blob.o' being placed in section `.bpfilter_umh'
Introduced by commit
61fbf5933d42 ("net: bpfilter: restart
On 01/12/2019 10:18 PM, Shakeel Butt wrote:
>> --- a/arch/x86/kernel/espfix_64.c
>> +++ b/arch/x86/kernel/espfix_64.c
>> @@ -57,8 +57,6 @@
>> # error "Need more virtual address space for the ESPFIX hack"
>> #endif
>>
>> -#define PGALLOC_GFP (GFP_KERNEL | __GFP_ZERO)
>> -
>> /* This contains
Powerpc hw does not have inbuilt latency filter (--ldlat) for mem-load
event and, perf_mem_events by default includes ldlat=30 which is
causing failure on powerpc. Refactor code to support perf mem/c2c on
powerpc.
This patch depends on kernel side changes done my Madhavan:
On Fri, Jan 11, 2019 at 08:51:54AM +0100, Nicolai Stange wrote:
> Joe Lawrence writes:
>
> > On Fri, Jan 11, 2019 at 01:00:38AM +0100, Nicolai Stange wrote:
[ ... snip ... ]
> >> For testing, could you try whether clearing the word at STACK_FRAME_MARKER
> >> from _switch() helps?
> >>
> >>
Hi Sebastien,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v5.0-rc2 next-20190111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 01/13/2019 11:05 PM, Michal Hocko wrote:
> On Sat 12-01-19 15:56:38, Anshuman Khandual wrote:
>> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL |
>> __GFP_ZERO) and using it for allocating page table pages. This causes some
>> code duplication which can be easily
Hi Arnd,
Arnd Bergmann writes:
> The IPC system call handling is highly inconsistent across architectures,
> some use sys_ipc, some use separate calls, and some use both. We also
> have some architectures that require passing IPC_64 in the flags, and
> others that set it implicitly.
>
> For the
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 10:52 PM, Douglas Gilbert
wrote:
> On 2019-01-13 10:07 p.m., Esme wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Sunday, January 13, 2019 9:33 PM, Qian Cai c...@lca.pw wrote:
> >
> > > On 1/13/19 9:20 PM, David Lechner wrote:
>
On 2019-01-13 10:07 p.m., Esme wrote:
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 9:33 PM, Qian Cai wrote:
On 1/13/19 9:20 PM, David Lechner wrote:
On 1/11/19 8:58 PM, Michel Lespinasse wrote:
On Fri, Jan 11, 2019 at 3:47 PM David Lechner da...@lechnology.com wrote:
On
Hi Arnd,
Arnd Bergmann writes:
> The IPC system call handling is highly inconsistent across architectures,
> some use sys_ipc, some use separate calls, and some use both. We also
> have some architectures that require passing IPC_64 in the flags, and
> others that set it implicitly.
>
> For the
The top Makefile does not need to export KBUILD_VMLINUX_INIT and
KBUILD_VMLINUX_MAIN separately.
Put every built-in.a into KBUILD_VMLINUX_OBJS. The order of
$(head-y), $(init-y), $(core-y), ... is still retained.
Signed-off-by: Masahiro Yamada
---
Makefile| 6 +++---
From: Randy Dunlap
Fix Sphinx warning in coding-style.rst:
Documentation/process/coding-style.rst:446: WARNING: Inline interpreted text or
phrase reference start-string without end-string.
Signed-off-by: Randy Dunlap
---
Documentation/process/coding-style.rst |2 +-
1 file changed, 1
The symbol table in the final archive is unneeded because it is passed
to the linker after the --whole-archive option. Every object file in
the archive is included in the link anyway.
Pass thin archives from subdirectories directly to the linker, and
remove the final archiving step.
Hi, Mimi, Dave
I checked the previous patches:
https://www.spinics.net/lists/keyrings/msg03518.html
https://www.spinics.net/lists/keyrings/msg03517.html
https://www.spinics.net/lists/keyrings/msg03516.html
That the latest patched I could found that placed the platform keyring in certs/
However
Hey all,
I think there are two different issues:
1. clk_gating's state(including state's trace event) and is_suspended is not
wrapped by ufshcd_is_clkgating_allowed which Hisilicon's kirin platoform
soc does not need but is set and checked in a regular path.
2. I think SCSI is
From: Randy Dunlap
Fix Sphinx warnings in ibmvmc.rst, add an index.rst file in
Documentation/misc-devices/, and insert that index file into the
top-level index file.
Documentation/misc-devices/ibmvmc.rst:2: WARNING: Explicit markup ends without
a blank line; unexpected unindent.
static checker warning:
drivers/xen/pvcalls-front.c:373 alloc_active_ring()
error: we previously assumed 'map->active.ring' could be null
(see line 357)
drivers/xen/pvcalls-front.c
351 static int alloc_active_ring(struct sock_mapping *map)
352 {
353 void
People reported a bug on a high end server with many pcie devices, where
kernel bootup with crashkernel=384M, and kaslr is enabled. Even
though we still see much memory under 896 MB, the finding still failed
intermittently. Because currently we can only find region under 896 MB,
if w/0 ',high'
Commit eea199b445f6 ("kbuild: remove unnecessary LEX_PREFIX and
YACC_PREFIX") removed the last users of this macro.
Signed-off-by: Masahiro Yamada
---
scripts/Kbuild.include | 4
1 file changed, 4 deletions(-)
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index
> -邮件原件-
> 发件人: Kohli, Gaurav [mailto:gko...@codeaurora.org]
> 发送时间: 2019年1月11日 21:57
> 收件人: Li,Rongqing ; linux-kernel@vger.kernel.org;
> jsl...@suse.com; gre...@linuxfoundation.org; a...@linux.intel.com
> 主题: Re: [PATCH][v2] tty: fix race between flush_to_ldisc and tty_open
>
> Hi,
>
>
‐‐‐ Original Message ‐‐‐
On Sunday, January 13, 2019 9:33 PM, Qian Cai wrote:
> On 1/13/19 9:20 PM, David Lechner wrote:
>
> > On 1/11/19 8:58 PM, Michel Lespinasse wrote:
> >
> > > On Fri, Jan 11, 2019 at 3:47 PM David Lechner da...@lechnology.com wrote:
> > >
> > > > On 1/11/19 2:58
Hi all,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
between commit:
7bb25a89aad2 ("scsi: hisi_sas: Set protection parameters prior to adding SCSI
host")
from the scsi-fixes tree and commit:
ef63464bcf8f ("scsi: hisi_sas: Create
On Sun, Jan 13, 2019 at 03:38:21PM -0800, Matthew Wilcox wrote:
> On Mon, Jan 14, 2019 at 10:29:02AM +1100, Dave Chinner wrote:
> > Until you have images (and hence host page cache) shared between
> > multiple guests. People will want to do this, because it means they
> > only need a single set of
Hi all,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/arcmsr/arcmsr_hba.c
between commit:
750afb08ca71 ("cross-tree: phase out dma_zalloc_coherent()")
from Linus' tree and commit:
381d66da7212 ("scsi: arcmsr: Rename acb structure member roundup_ccbsize to
On 1/13/19 6:31 PM, H. Peter Anvin wrote:
>
> static cpumask_t text_poke_cpumask;
>
> static void text_poke_sync(void)
> {
> smp_wmb();
> text_poke_cpumask = cpu_online_mask;
> smp_wmb(); /* Should be optional on x86 */
> cpumask_clear_cpu(_poke_cpumask,
Default NMI handling code prints the same into the kernel log.
Signed-off-by: Ivan Mironov
---
drivers/watchdog/hpwdt.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index e2958df46c69..95d002b5b120
Existing code disables watchdog on NMI right before completely hanging
the system.
There are two problems here:
* First, watchdog is expected to reset the system in a case of such
failure, no matter what.
* Second, this code has no effect if there are more than one watchdog.
Signed-off-by:
Currently, hpwdt unconditionally panics on foreign NMIs in some cases.
This goes against the default kernel behaviour (which is configured by
unknown_nmi_panic and panic_on_unrecovered_nmi).
With this patch, hpwdt will simply ignore NMI unless one of "mynmi"
flags is set by iLO.
Signed-off-by:
Hi,
I found out that hpwdt alters NMI behaviour unexpectedly if compiled
with enabled CONFIG_HPWDT_NMI_DECODING:
* System starts to panic on any NMI with misleading message.
* Watchdog provided by hpwdt is not working after such panic.
Here are the patches that should fix this.
This is an
This adds an option to not panic on NMI even if it was caused by iLO.
Signed-off-by: Ivan Mironov
---
drivers/watchdog/hpwdt.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index
On 1/13/19 9:20 PM, David Lechner wrote:
> On 1/11/19 8:58 PM, Michel Lespinasse wrote:
>> On Fri, Jan 11, 2019 at 3:47 PM David Lechner wrote:
>>>
>>> On 1/11/19 2:58 PM, Qian Cai wrote:
A GPF was reported,
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by
On 1/11/19 11:39 AM, Jiri Kosina wrote:
> On Fri, 11 Jan 2019, h...@zytor.com wrote:
>
>> I still don't see why can't simply spin in the #BP handler until the
>> patch is complete.
>
> I think this brings us to the already discussed possible deadlock, when
> one CPU#0 is in the middle of
On 1/11/19 8:58 PM, Michel Lespinasse wrote:
On Fri, Jan 11, 2019 at 3:47 PM David Lechner wrote:
On 1/11/19 2:58 PM, Qian Cai wrote:
A GPF was reported,
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1]
Hi, Alexandre
Best Regards!
Anson Huang
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@bootlin.com]
> Sent: 2019年1月11日 22:32
> To: Anson Huang
> Cc: a.zu...@towertech.it; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; dl-linux-imx
> Subject: Re:
On Fri, 2019-01-11 at 17:07 +0100, Noralf Trønnes wrote:
>
> Den 11.01.2019 11.25, skrev Daniel Vetter:
> > On Fri, Jan 11, 2019 at 05:49:15PM +0800, CK Hu wrote:
> >> Hi, Daniel:
> >>
> >> On Fri, 2019-01-11 at 10:20 +0100, Daniel Vetter wrote:
> >>> On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK
在 2019年01月11日 20:33, Borislav Petkov 写道:
> On Thu, Jan 10, 2019 at 08:19:43PM +0800, Lianbo Jiang wrote:
>> +init_uts_ns.name.release
>> +
>> +
>> +The version of the Linux kernel. Used to find the corresponding source
>> +code from which the kernel has been built.
>> +
>
1 - 100 of 260 matches
Mail list logo
