On 7/9/19 5:38 AM, Peter Zijlstra wrote:
On Mon, Jul 08, 2019 at 07:00:08PM -0700, Ankur Arora wrote:
On 2019-06-26 12:23 p.m., Thomas Gleixner wrote:
On Wed, 26 Jun 2019, Raslan, KarimAllah wrote:
On Wed, 2019-06-26 at 10:54 -0400, Konrad Rzeszutek Wilk wrote:
There were some ideas that Anku
On Mon, 2019-07-08 at 23:35 +0200, Christoph Hellwig wrote:
> We actually have a discussion on that in another thread, but if you
> can easily reproduce the issue, can you test the patch below?
>
> diff --git a/fs/xfs/xfs_bio_io.c b/fs/xfs/xfs_bio_io.c
> index 757c1d9293eb..e2148f2d5d6b 100644
> -
From: Numfor Mbiziwo-Tiapo
Running the 'perf test' command after building perf with a memory
sanitizer causes a warning that says:
WARNING: MemorySanitizer: use-of-uninitialized-value... in
mmap-thread-lookup.c
Initializing the go variable to 0 silences this harmless warning.
Committer warn
From: Leo Yan
Based on the following report from Smatch, fix the use-after-freed
pointer.
tools/perf/builtin-stat.c:1353
add_default_attributes() warn: passing freed memory 'str'.
The pointer 'str' has been freed but later it is still passed into the
function parse_events_print_error(). Th
nux/kernel/git/acme/linux into perf/core
(2019-07-09 13:22:03 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-5.3-20190709
for you to fetch changes up to 323fd749821daab0f327ec86d707c4542963cdb0:
perf int
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/builtin-trace.c:1044
thread_trace__new() error: we previously assumed 'ttrace' could be
null (see line 1041).
tools/perf/builtin-trace.c
1037 static struct thread_trac
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/builtin-top.c:109
perf_top__parse_source() warn: variable dereferenced before check 'he'
(see line 103)
tools/perf/builtin-top.c:233
perf_top__show_details() warn: var
mmc cards on mmc1 are not detected because of wrong card detect (cd) level.
Change cd from GPIO_ACTIVE_HIGH to GPIO_ACTIVE_LOW.
This is necessary because of commit e63201f19438 ("mmc: omap_hsmmc:
Delete platform data GPIO CD and WP")
Signed-off-by: Andreas Klinger
---
arch/arm/boot/dts/am335x-
From: Arnaldo Carvalho de Melo
Check first, as machines__deliver_event() may have
perf_evlist__id2evsel() returning NULL.
This was found while checking a report from Leo Yan that used the smatch
tool to find places where a pointer is checked before use and then,
later in the same function gets u
From: Leo Yan
Based on the following report from Smatch, fix the potential
dereferencing freed memory check.
tools/perf/util/annotate.c:1125
disasm_line__parse() error: dereferencing freed memory 'namep'
tools/perf/util/annotate.c
1100 static int disasm_line__parse(char *line, const cha
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/util/map.c:479
map__fprintf_srccode() error: we previously assumed 'state' could be
null (see line 466)
tools/perf/util/map.c
465 /* Avoid redundant printing *
From: Leo Yan
Based on the following report from Smatch, fix the potential
NULL pointer dereference check.
tools/perf/util/session.c:1252
dump_read() error: we previously assumed 'evsel' could be null
(see line 1249)
tools/perf/util/session.c
1240 static void dump_read(struct perf_evs
From: Arnaldo Carvalho de Melo
It'll return "unknown", no need to open code it.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Leo Yan
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-4okvjmm18arjrcyfhuahg...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/builtin-report.c |
From: Arnaldo Carvalho de Melo
Part of the erosion of util/util.h, that will lose its include stdlib.h,
we need to add it to places where it is needed but was getting it
indirectly.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-1imnqezw99ahc07fjeb51...@g
From: Arnaldo Carvalho de Melo
In places where the equivalent was already being done, i.e.:
free(a);
a = NULL;
And in placs where struct members are being freed so that if we have
some erroneous reference to its struct, then accesses to freed members
will result in segfaults, which we can
From: Arnaldo Carvalho de Melo
Eroding a bit more the tools/perf/util/util.h hodpodge header.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-natazosyn9rwjka25tvcn...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/include/linux/zalloc.h
From: Arnaldo Carvalho de Melo
So that at the end each of the entries have its list node struct cleared
and the egroup list head ends emptied.
Cc: Adrian Hunter
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-dxzj1ah350fy9ec0xbhb1...@git.kernel.org
Signed-of
From: Arnaldo Carvalho de Melo
To allow for destructors to check if they're operating on a object still
in a list, and to avoid going from use after free list entries into
still valid, or even also other already removed from list entries.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link:
From: Luke Mujica
Remove the 'int i' because it is declared but not used in parse-events.y
or in the generated parse-events.c.
Signed-off-by: Luke Mujica
Cc: Alexander Shishkin
Cc: Ian Rogers
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link: http://lkml.kernel.o
From: Luke Mujica
Remove the 'error' variable because it is declared but not used in
parse-events.y or in the generated parse-events.c.
Signed-off-by: Luke Mujica
Cc: Alexander Shishkin
Cc: Ian Rogers
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Stephane Eranian
Link: http://lkml
From: Arnaldo Carvalho de Melo
And in a separate header, so that we erode util.h a bit more.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-xpzvuu9d0gei9jl9bkzgo...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/get_current_d
From: Arnaldo Carvalho de Melo
Out of util.h, to reduce its scope, and since we have a namespaces.h
header, much better to have it there, where it is related to.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-zlu81bbtccuzygh7m8nmg...@git.kernel.org
Signed
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/util/cs-etm.c:2545
cs_etm__process_auxtrace_info() error: we previously assumed
'session->itrace_synth_opts' could be null (see line 2541)
tools/perf/util/cs-etm.c
254
From: Leo Yan
Based on the following report from Smatch, fix the potential
NULL pointer dereference check.
tools/perf/ui/browsers/hists.c:641
hist_browser__run() error: we previously assumed 'hbt' could be
null (see line 625)
tools/perf/ui/browsers/hists.c:3088
perf_evsel__hists_brows
From: Adrian Hunter
Drop power_events_view before its dependent tables.
SQLite does not seem to mind but the fix was needed for PostgreSQL
(export-to-postgresql.py script), so do the same fix for the SQLite. It is
more logical and keeps the 2 scripts following the same approach.
Signed-off-by:
From: Adrian Hunter
PostgreSQL can error if power_events_view is not dropped before its
dependent tables e.g.
Exception: Query failed: ERROR: cannot drop table mwait because other
objects depend on it
DETAIL: view power_events_view depends on table mwait
Signed-off-by: Adrian Hunter
Cc
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/util/intel-pt.c:3200
intel_pt_process_auxtrace_info() error: we previously assumed
'session->itrace_synth_opts' could be null (see line 3196)
tools/perf/util/intel-pt.c:
From: Song Liu
In pipe mode, session->header.env.arch is not populated until the events
are processed. Therefore, the following command crashes:
perf record -o - | perf script
(gdb) bt
It fails when we try to compare env.arch against uts.machine:
if (!strcmp(uts.machine, session->h
From: Leo Yan
Based on the following report from Smatch, fix the potential NULL
pointer dereference check.
tools/perf/util/intel-bts.c:898
intel_bts_process_auxtrace_info() error: we previously assumed
'session->itrace_synth_opts' could be null (see line 894)
tools/perf/util/intel-bts.c
The kasan_check_read() is marked 'inline', which usually includes
the 'always_inline' attribute. In some configuration, gcc decides that
it cannot inline this, causing a build failure:
In file included from include/linux/compiler.h:257,
from arch/x86/include/asm/current.h:5,
this fixes below issues reported by coccicheck
sound/soc/codecs/wcd9335.c:3611:5-8: Unneeded variable: "ret". Return
"0" on line 3625
sound/soc/codecs/wcd9335.c:3941:5-8: Unneeded variable: "ret". Return
"0" on line 3971
sound/soc/codecs/wcd9335.c:3745:5-8: Unneeded variable: "ret". Return
"0" on
On Mon, Jul 08, 2019 at 12:35:13PM -0700, Thomas Garnier wrote:
> On Mon, Jul 8, 2019 at 12:09 PM Alexey Dobriyan wrote:
> >
> > Thomas Garnier wrote:
> > > - "pushq $1f\n\t"
> > > + "movabsq $1f, %q0\n\t"
> > > + "pushq %q0\n\t"
> > > "iretq\n\t"
On Sun, Jul 7, 2019 at 7:31 AM Andreas Färber wrote:
>
> Am 07.07.19 um 15:23 schrieb Aleix Roca Nonell:
> > Add bindings for Relatek RTD1296 SoC. And the Bannana Pi BPI-W2 board.
>
> "Realtek", "Banana"
>
> >
> > Signed-off-by: Aleix Roca Nonell
> > ---
> > Documentation/devicetree/bindings/arm
On Mon, Jul 08, 2019 at 05:12:10PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.185 release.
> There are 73 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
On Mon, Jul 08, 2019 at 05:12:52PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.133 release.
> There are 56 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 kno
On Mon, Jul 08, 2019 at 05:12:27PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.58 release.
> There are 90 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
On Tue, Jul 9, 2019 at 8:08 PM 'Nick Desaulniers' via Clang Built
Linux wrote:
> On Tue, Jul 9, 2019 at 1:41 AM Linus Walleij wrote:
>
> > I guess this brings up the old question whether the compiler should
> > be worked around or just considered immature, but as it happens this
>
> Definitely a
On Mon, Jul 08, 2019 at 05:12:32PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.17 release.
> There are 96 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.
This patch fixes below issues reported by coccicheck
sound/soc/bcm/cygnus-pcm.c:642:5-8: Unneeded variable: "ret". Return "0"
on line 650
sound/soc/bcm/cygnus-pcm.c:671:5-8: Unneeded variable: "ret". Return "0"
on line 696
We cannot change return type of these functions as they are callback
funct
llvm gets confused by inline asm with .rep directives, which
can lead to miscalculating the number of instructions inside it,
and in turn lead to an overflow for relative address calculation:
/tmp/cfi_cmdset_0002-539a47.s: Assembler messages:
/tmp/cfi_cmdset_0002-539a47.s:11288: Error: bad immedia
On Tue, 9 Jul 2019 at 20:36, Arnd Bergmann wrote:
>
> The kasan_check_read() is marked 'inline', which usually includes
> the 'always_inline' attribute. In some configuration, gcc decides that
> it cannot inline this, causing a build failure:
>
> In file included from include/linux/compiler.h:257,
On Mon, Jul 08, 2019 at 05:11:53PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.185 release.
> There are 102 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 kno
On Tue, Jul 9, 2019 at 11:39 AM Alexey Dobriyan wrote:
>
> On Mon, Jul 08, 2019 at 12:35:13PM -0700, Thomas Garnier wrote:
> > On Mon, Jul 8, 2019 at 12:09 PM Alexey Dobriyan wrote:
> > >
> > > Thomas Garnier wrote:
> > > > - "pushq $1f\n\t"
> > > > + "movabsq $1f, %q0\n\t
-mindirect-branch and -fcf-protection are not compatible, and
so kernel builds fail with a gcc build where -fcf-protection is
enabled by default. Add -fcf-protection=none to the retpoline
flags to fix this.
Signed-off-by: Seth Forshee
---
Makefile | 4
1 file changed, 4 insertions(+)
diff
Hi Bartosz,
On Tue, May 28, 2019 at 5:46 PM Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Use the managed variant of gpiochip_add_data() and remove the call to
> gpiochip_remove().
>
> Cc: Geert Uytterhoeven
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/gpio/gpio-em.c | 4
On Tue, Jul 9, 2019 at 11:36 AM Arnd Bergmann wrote:
>
> The kasan_check_read() is marked 'inline', which usually includes
> the 'always_inline' attribute. In some configuration, gcc decides that
> it cannot inline this, causing a build failure:
>
> In file included from include/linux/compiler.h:2
On Wed, Jul 3, 2019 at 2:01 PM Hongwei Zhang wrote:
>
> Add bindings to support SGPIO on AST2400 or AST2500.
>
> Signed-off-by: Hongwei Zhang
> ---
> .../devicetree/bindings/gpio/sgpio-aspeed.txt | 36
> ++
Is this SGPIO as in the blinky lights for HDDs in servers? If s
Original reproducer is almost identical to the one that is fixed by
https://patchwork.ozlabs.org/patch/1129479/.
bpf_prog_free_deferred bug that's undeterministically exposed after
this fix seems to be the cause of a bunch of other bug reports and is
not related to verifier precision tracking.
#s
Calling an __init function from a __meminit function is not allowed:
WARNING: vmlinux.o(.meminit.text+0x30ff): Section mismatch in reference from
the function sparse_buffer_alloc() to the function
.init.text:sparse_buffer_free()
The function __meminit sparse_buffer_alloc() references
a function
The restructuring of the driver got the dependencies wrong: without
CONFIG_NET_DSA we get this build failure:
WARNING: unmet direct dependencies detected for NET_DSA_VITESSE_VSC73XX
Depends on [n]: NETDEVICES [=y] && HAVE_NET_DSA [=y] && OF [=y] && NET_DSA
[=n]
Selected by [m]:
- NET_DSA_VI
Hi! I'm adding Vojtěch Vladyka to conversation.
Steve, can you describe what you mean by Advanced Format 4K sector size?
It is hard disk with 512 bytes logical sector size and 4096 bytes
physical sector size? Or do you mean hard disk which has both logical
and physical sector size equal to 4096 b
Without the CONFIG_PM_CLK dependency, we can now build this file
in kernels that don't have CONFIG_PM at all, resulting in a harmless
warning from code that was always there since it got merged:
drivers/dma/tegra210-adma.c:747:12: error: 'tegra_adma_runtime_resume' defined
but not used [-Werror=u
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 47 of them as possibly being bugs in the usb subsystem.
On Tue, Jul 9, 2019 at 12:25 AM Vincent Guittot
wrote:
>
> On Sun, 7 Jul 2019 at 23:48, Saravana Kannan wrote:
> >
> > On Thu, Jul 4, 2019 at 12:12 AM Vincent Guittot
> > wrote:
> > >
> > > On Wed, 3 Jul 2019 at 23:33, Saravana Kannan wrote:
> > > >
> > > > On Tue, Jul 2, 2019 at 11:45 PM Vince
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the "android/ashmem
On 6/18/19 10:15 AM, Arnd Bergmann wrote:
On Tue, Jun 18, 2019 at 2:03 PM Will Deacon wrote:
From 6e004b8824d4eb6a4e61cd794fbc3a761b50135b Mon Sep 17 00:00:00 2001
From: Will Deacon
Date: Tue, 18 Jun 2019 12:56:49 +0100
Subject: [PATCH] genksyms: Teach parse about __uint128_t built-in type
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 29 of them as possibly being bugs in the bluetooth subsy
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the "kernel/cgroup"
This is mostly update of the usual drivers: qla2xxx, hpsa, lpfc, ufs,
mpt3sas, ibmvscsi, megaraid_sas, bnx2fc and hisi_sas as well as the
removal of the osst driver (I heard from Willem privately that he would
like the driver removed because all his test hardware has
failed). Plus number of minor
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as possibly being bugs in the "security/integr
On Tue, Jul 09, 2019 at 11:02:40AM -0700, Alexei Starovoitov wrote:
> On Tue, Jul 9, 2019 at 10:48 AM Josh Poimboeuf wrote:
> >
> > On Mon, Jul 08, 2019 at 04:16:25PM -0700, Alexei Starovoitov wrote:
> > > total time is hard to compare.
> > > Could you compare few tests?
> > > like two that are ca
From: Jose Abreu
Date: Tue, 9 Jul 2019 10:02:57 +0200
> Some performace improvements (01/03 and 03/03) and a fix (02/03),
> all for -next.
Series applied, thanks Jose.
Mixing array constraints like 'maxItems' and string or integer value
constraints like 'minimum' don't make sense. Also, with only value
constraints, it is implied we have a single value. So lets remove
'maxItems: 1'.
Cc: Mark Brown
Cc: linux-...@vger.kernel.org
Signed-off-by: Rob Herring
---
Do
On 07/09/2019 09:17 PM, Josh Poimboeuf wrote:
> On Tue, Jul 09, 2019 at 11:02:40AM -0700, Alexei Starovoitov wrote:
>> On Tue, Jul 9, 2019 at 10:48 AM Josh Poimboeuf wrote:
>>>
>>> On Mon, Jul 08, 2019 at 04:16:25PM -0700, Alexei Starovoitov wrote:
total time is hard to compare.
Could yo
wt., 9 lip 2019 o 20:49 Geert Uytterhoeven napisał(a):
>
> Hi Bartosz,
>
> On Tue, May 28, 2019 at 5:46 PM Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > Use the managed variant of gpiochip_add_data() and remove the call to
> > gpiochip_remove().
> >
> > Cc: Geert Uytterhoeven
On Wed, Jul 3, 2019 at 7:58 PM Nathan Chancellor
wrote:
> On Wed, Jul 03, 2019 at 10:10:55AM +0200, Arnd Bergmann wrote:
> > When CONFIG_LOCKDEP is set, every use of DECLARE_WAIT_QUEUE_HEAD_ONSTACK()
> > produces an annoying warning from clang, which is particularly annoying
> > for allmodconfig b
On Tue, Jul 09, 2019 at 01:50:26PM +0200, Dag Moxnes wrote:
> Use the neighbour lock when copying the MAC address from the neighbour
> data struct in dst_fetch_ha.
>
> When not using the lock, it is possible for the function to race with
> neigh_update(), causing it to copy an torn MAC address:
>
Fixes: 962fb618909e ("net: ethernet: ti: davinci_cpdma: allow desc split while
down")
Signed-off-by: kbuild test robot
---
davinci_cpdma.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/ti/davinci_cpdma.c
b/drivers/net/ethernet/ti/davinci_cpdma.c
i
tree:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
master
head: 4608a726c66807c27bc7d91bdf8a288254e29985
commit: 962fb618909ef64e0c89af5b79ba0fed910b78e3 [13028/13492] net: ethernet:
ti: davinci_cpdma: allow desc split while down
reproduce:
# apt-get i
On Tue, Jul 9, 2019 at 8:46 PM Marco Elver wrote:
>
> On Tue, 9 Jul 2019 at 20:36, Arnd Bergmann wrote:
> >
> > The kasan_check_read() is marked 'inline', which usually includes
> > the 'always_inline' attribute. In some configuration, gcc decides that
> > it cannot inline this, causing a build f
On Tue, Jul 02, 2019 at 11:22:59AM -0700, Eric Biggers wrote:
>
> Sure, but the new mount syscalls still need tests. Where are the tests?
>
Still waiting for an answer to this question.
Did we just release 6 new syscalls with no tests?
I don't understand how that is even remotely acceptable.
James,
> This is mostly update of the usual drivers: qla2xxx, hpsa, lpfc, ufs,
> mpt3sas, ibmvscsi, megaraid_sas, bnx2fc and hisi_sas as well as the
> removal of the osst driver (I heard from Willem privately that he would
> like the driver removed because all his test hardware has
> failed). P
This reverts commit b6c61a6c37317efd7327199bfe24770af3d7e799.
The requested pixelformat is being propagated from the capture to the
tpg in the sensor.
This was a bad design choice, as we start having the following issues:
* We set a pixelformat in the capture;
* We set matching media bus formats
This reverts commit 3c1b9ac753e99005d7ee0a883d6e5b577ba32aa9.
Required to Revert "media: vimc: propagate pixel format in the stream"
which introduced the stream object in the vimc_ent_device struct.
Signed-off-by: Helen Koike
---
drivers/media/platform/vimc/vimc-debayer.c | 5 -
drivers/med
On Tue, 2019-07-09 at 15:39 -0400, Martin K. Petersen wrote:
> James,
>
> > This is mostly update of the usual drivers: qla2xxx, hpsa, lpfc,
> > ufs, mpt3sas, ibmvscsi, megaraid_sas, bnx2fc and hisi_sas as well
> > as the removal of the osst driver (I heard from Willem privately
> > that he would
James,
> Actually, I was planning a second pull request for that one. I
> presume you think it's ready to go?
It's spent 3 weeks in -next without any complaints.
--
Martin K. Petersen Oracle Linux Engineering
On Tue, 2 Jul 2019, Nadav Amit wrote:
> SGI UV support is outdated and not maintained, and it is not clear how
> it performs relatively to non-UV. Remove the code to simplify the code.
You should at least Cc the SGI/HP folks on that. They are still
around. Done so.
> Cc: Peter Zijlstra
> Cc: Da
Hi Cong,
I finally got around to looking at these patches. Sorry for such a long
time, I've been terribly busy :-(
BTW, it's best to look at how other commits in a subsystem do their
subject lines. The subsystem is "tracing" not "trace", and Linus
prefers to have the first letter after that cap
On Tue, Jul 09, 2019 at 11:41:54AM -0700, Guenter Roeck wrote:
> On Mon, Jul 08, 2019 at 05:12:32PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.1.17 release.
> > There are 96 patches in this series, all will be posted as a response
> > to this one. I
The pull request you sent on Tue, 9 Jul 2019 07:46:32 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
> parisc-5.3-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/593c75463ab6d6985cdc9916f3d1c28b5f6340cd
Thank you!
--
Deet-doot-dot,
The pull request you sent on Tue, 09 Jul 2019 12:33:14 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-kdump-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/565eb5f8c5d379b6a6a3134c76b2fcfecdd007d3
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Tue, 9 Jul 2019 15:22:59 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk
> tags/printk-for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7011b7e1b702cc76f9e969b41d9a95969f2aecaa
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Tue, 9 Jul 2019 13:38:19 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/608745f12462e2d8d94d5cc5dc94bf0960a881e3
Thank you!
--
Deet-doot-dot, I am a b
The pull request you sent on Tue, 9 Jul 2019 09:06:11 -0600:
> git://git.lwn.net/linux.git tags/docs-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e9a83bd2322035ed9d7dcf35753d3f984d76c6a5
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/use
The pull request you sent on Tue, 09 Jul 2019 12:33:14 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b7d5c9239855f99762e8a547bea03a436e8a12e8
Thank you!
--
Deet-doot-dot, I am a b
Hi!
On Tue 09-07-19 13:27:58, Steve Magnani wrote:
> Recently I have been exploring Advanced Format (4K sector size)
> and high capacity aspects of UDF 2.01 support in Linux and
> Windows 10. I thought it might be helpful to summarize my findings.
>
> The good news is that I did not see any bugs
The pull request you sent on Tue, 9 Jul 2019 04:32:39 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
> next-lsm
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9d22167f34305280c5dd57a74c21651da3c23015
Thank you!
--
Deet-doot-
On Wed, 19 Jun 2019 09:39:52 +0200, Oliver Graute wrote:
> From: Oliver Graute
>
> added header defines for imx8qm clock
>
> Signed-off-by: Oliver Graute
> ---
> include/dt-bindings/clock/imx8qm-clock.h | 851 +++
> 1 file changed, 851 insertions(+)
> create mode 100644 in
On Wed, 19 Jun 2019 11:52:01 +0200, Fabrice Gasnier wrote:
> STM32 Timers support generic 3 cells PWM bindings to encode PWM number,
> period and polarity as defined in pwm.txt.
>
> Fixes: cd9a99c2f8e8 ("dt-bindings: pwm: Add STM32 bindings")
>
> Signed-off-by: Fabrice Gasnier
> ---
> Documenta
On Tue, Jul 09, 2019 at 09:50:27PM +0200, Thomas Gleixner wrote:
> On Tue, 2 Jul 2019, Nadav Amit wrote:
>
> > SGI UV support is outdated and not maintained, and it is not clear how
> > it performs relatively to non-UV. Remove the code to simplify the code.
>
> You should at least Cc the SGI/HP f
Ich beabsichtige, Ihnen einen Teil meines Vermögens als freiwillige
finanzielle Spende zukommen zu lassen.
Wang Jianlin
This message was sent using IMP, the Internet Messaging Program.
--
Este mensaje ha sido analizado por STEP O
On Wed, Jun 19, 2019 at 04:15:34PM +0200, Gregory CLEMENT wrote:
> Document the device tree binding for the cluster clock controllers found
> in the Armada 7K/8K SoCs.
>
> Signed-off-by: Gregory CLEMENT
> ---
> .../arm/marvell/ap806-system-controller.txt | 25 +++
> 1 file chan
On Thu, 20 Jun 2019 17:30:46 +0800, Mason Yang wrote:
> Dcument the bindings used by the Renesas R-Car Gen3 RPC-IF controller.
>
> Signed-off-by: Mason Yang
> ---
> .../devicetree/bindings/spi/spi-renesas-rpc.txt| 43
> ++
> 1 file changed, 43 insertions(+)
> create mod
On Thu, 20 Jun 2019 17:09:50 -0400, Al Cooper wrote:
> Remove "brcm,bdc-v0.16" because it was never used on any system.
> Add "brcm,bdc-udc-v3.1" which exists for any STB system with BDC.
>
> Signed-off-by: Al Cooper
> ---
> Documentation/devicetree/bindings/usb/brcm,bdc.txt | 4 ++--
> 1 file c
On 7/9/19 1:56 PM, Pali Rohár wrote:
Steve, can you describe what you mean by Advanced Format 4K sector size?
It is hard disk with 512 bytes logical sector size and 4096 bytes
physical sector size? Or do you mean hard disk which has both logical
and physical sector size equal to 4096 bytes?
> -Original Message-
> From: Eric Dumazet
> Sent: 9-Jul-19 09:46
> To: Jon Maloy ; Eric Dumazet
> ; Chris Packham
> ; ying@windriver.com;
> da...@davemloft.net
> Cc: net...@vger.kernel.org; tipc-discuss...@lists.sourceforge.net; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH]
On Fri, Jul 05, 2019 at 11:44:18PM -0400, Valdis Klētnieks wrote:
> This worked fine in next-20190618, but in next-20190701 I'm seeing dmesg
> entries at boot:
>
> dmesg | grep -i x.509
> [8.345699] Loading compiled-in X.509 certificates
> [8.366137] Problem loading in-kernel X.509 certifi
On Fri, 21 Jun 2019 15:07:18 +0800, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Add i.MX8MM system counter clock macro definition.
>
> Signed-off-by: Anson Huang
> ---
> include/dt-bindings/clock/imx8mm-clock.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Reviewed-by:
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 4 of them as possibly being bugs in the sound subsystem.
From: Arnd Bergmann
Date: Tue, 9 Jul 2019 20:55:55 +0200
> The restructuring of the driver got the dependencies wrong: without
> CONFIG_NET_DSA we get this build failure:
>
> WARNING: unmet direct dependencies detected for NET_DSA_VITESSE_VSC73XX
> Depends on [n]: NETDEVICES [=y] && HAVE_NET_
401 - 500 of 744 matches
Mail list logo
