On Tue, Jun 25, 2019 at 03:50:29PM +0800, Greg KH wrote:
> On Mon, Jun 24, 2019 at 11:42:34AM +0100, Ignat Korchagin wrote:
> > Hi Greg,
> >
> > > > For us it seems applying the following 4 mainline patches makes 4.19.x
> > > > branch perf compile with GCC-9:
> > > >
> > > > 4d0f16d059ddb91424480d
On Mon, Jun 24, 2019 at 11:42:34AM +0100, Ignat Korchagin wrote:
> Hi Greg,
>
> > > For us it seems applying the following 4 mainline patches makes 4.19.x
> > > branch perf compile with GCC-9:
> > >
> > > 4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use
> > > strlcpy() as a shorter
Hi Greg,
> > For us it seems applying the following 4 mainline patches makes 4.19.x
> > branch perf compile with GCC-9:
> >
> > 4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use
> > strlcpy() as a shorter form of strncpy() + explicit set nul
> > b6313899f4ed2e76b8375cf8069556f5b94fbf
Em Mon, Jun 10, 2019 at 05:25:42PM +0200, Greg KH escreveu:
> On Mon, Jun 10, 2019 at 12:14:07PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jun 10, 2019 at 12:21:51AM -0700, Ivan Babrou escreveu:
> > > Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
> > > perf still d
On Mon, Jun 10, 2019 at 12:14:07PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jun 10, 2019 at 12:21:51AM -0700, Ivan Babrou escreveu:
> > Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
> > perf still doesn't want to compile:
> >
> > [07:15:32]In file included from /us
Em Mon, Jun 10, 2019 at 12:21:51AM -0700, Ivan Babrou escreveu:
> Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
> perf still doesn't want to compile:
>
> [07:15:32]In file included from /usr/include/string.h:635,
> [07:15:32] from util/debug.h:7,
> [07:15:32] from builtin-
On Mon, Jun 10, 2019 at 4:49 PM Greg KH wrote:
>
> On Mon, Jun 10, 2019 at 04:42:27PM +0200, Miguel Ojeda wrote:
> > I think Josh Poimboeuf added support for a few related things in GCC 8
> > (e.g. 13810435b9a7 ("objtool: Support GCC 8's cold subfunctions")).
>
> That commit is already in all stab
On Mon, Jun 10, 2019 at 3:49 PM Greg KH wrote:
>
> >
> > I typically compile a bare-bones GCC for those things, it is quite quick.
>
> Pointers to how to do that is appreciated. It's been years since I had
> to build gcc "from scratch".
This is how we do it, but we use it for some other projects
On Mon, Jun 10, 2019 at 04:42:27PM +0200, Miguel Ojeda wrote:
> On Mon, Jun 10, 2019 at 4:21 PM Greg KH wrote:
> >
> > > I also checked that 4.19.49 compiles fine with GCC 9, although with a
> > > lot of warnings, mostly from objtool, like "warning: objtool:
> > > sock_register()+0xd: sibling call
On Mon, Jun 10, 2019 at 4:21 PM Greg KH wrote:
>
> > I also checked that 4.19.49 compiles fine with GCC 9, although with a
> > lot of warnings, mostly from objtool, like "warning: objtool:
> > sock_register()+0xd: sibling call from callable instruction with
> > modified stack frame". But it's a st
On Mon, Jun 10, 2019 at 10:32:25AM +0100, Ignat Korchagin wrote:
> Hi Greg,
>
> For us it seems applying the following 4 mainline patches makes 4.19.x
> branch perf compile with GCC-9:
>
> 4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use
> strlcpy() as a shorter form of strncpy() +
Hi Greg,
For us it seems applying the following 4 mainline patches makes 4.19.x
branch perf compile with GCC-9:
4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use
strlcpy() as a shorter form of strncpy() + explicit set nul
b6313899f4ed2e76b8375cf8069556f5b94fbff0: perf help: Remove n
On Mon, Jun 10, 2019 at 12:21:51AM -0700, Ivan Babrou wrote:
> Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
> perf still doesn't want to compile:
>
> [07:15:32]In file included from /usr/include/string.h:635,
> [07:15:32] from util/debug.h:7,
> [07:15:32] from builtin-hel
Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
perf still doesn't want to compile:
[07:15:32]In file included from /usr/include/string.h:635,
[07:15:32] from util/debug.h:7,
[07:15:32] from builtin-help.c:15:
[07:15:32]In function 'strncpy',
[07:15:32] inlined from 'add_man
On May 17, 2019 2:23:10 PM GMT-03:00, Ivan Babrou wrote:
>On Fri, May 17, 2019 at 8:22 AM Arnaldo Carvalho de Melo
> wrote:
>>
>> Em Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda escreveu:
>> > On Fri, May 17, 2019 at 10:51 AM Greg KH
> wrote:
>> > >
>> > > On Fri, May 17, 2019 at 10:35:29AM
On Fri, May 17, 2019 at 8:22 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda escreveu:
> > On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> > >
> > > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > > On Fri, May 17, 2019 at 9:38 A
Em Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda escreveu:
> On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra
> > > wrote:
> > > >
> > > > Right; if there is anything y
On Fri, May 17, 2019 at 11:42:17AM +0200, Greg KH wrote:
> On Fri, May 17, 2019 at 11:27:41AM +0200, Miguel Ojeda wrote:
> > On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
> > >
> > > On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> > >
> > > > a6e60d84989f ("include/linux/module.h
On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra
> > > wrote:
> > > >
> > > > Right; if there is anything you
On Fri, May 17, 2019 at 11:27:41AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> >
> > > a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> > > init/cleanup_module")
> >
> > Tha
On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
>
> On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
>
> > a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> > init/cleanup_module")
>
> That patch I applied now.
Note that this one requires the second one (c0d9782f5b
On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra
> > > wrote:
> > > >
> > > > Right; if there is anything you
On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
>
> On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
> > >
> > > Right; if there is anything you can reproduce on linus.git I'll happily
> > > have a look. If it doesn't reproduc
On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
> >
> > On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> > > On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > > > We are building the upstream kernel. The
On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
>
> On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> > On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > > We are building the upstream kernel. There are a few patches, but
> > > nothing related to objtool.
> > >
> > >
On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > We are building the upstream kernel. There are a few patches, but
> > nothing related to objtool.
> >
> > Unless you mean mainline/stable by upstream, I haven't tried that. W
On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> We are building the upstream kernel. There are a few patches, but
> nothing related to objtool.
>
> Unless you mean mainline/stable by upstream, I haven't tried that. We
> stick to LTS.
Please work and all of these issues fixed up in
We are building the upstream kernel. There are a few patches, but
nothing related to objtool.
Unless you mean mainline/stable by upstream, I haven't tried that. We
stick to LTS.
On Thu, May 16, 2019 at 7:04 PM Josh Poimboeuf wrote:
>
> On Thu, May 16, 2019 at 11:20:54PM +0200, Miguel Ojeda wrote
On Thu, May 16, 2019 at 11:20:54PM +0200, Miguel Ojeda wrote:
> > mm/slub.o: warning: objtool: init_cache_random_seq()+0x36: sibling
> > call from callable instruction with modified stack frame
> > mm/slub.o: warning: objtool: slab_out_of_memory()+0x3b: sibling call
> > from callable instruction wi
On Thu, May 16, 2019 at 2:21 PM Miguel Ojeda
wrote:
>
> Hi,
>
> On Thu, May 16, 2019 at 10:11 PM Ivan Babrou wrote:
> >
> > Hey Miguel,
> >
> > The first error is during perf build process (make -C tools/perf install):
> >
> > [17:38:21] In file included from /usr/include/string.h:635,
> > [17:38
Hi,
On Thu, May 16, 2019 at 10:11 PM Ivan Babrou wrote:
>
> Hey Miguel,
>
> The first error is during perf build process (make -C tools/perf install):
>
> [17:38:21] In file included from /usr/include/string.h:635,
> [17:38:21] from ui/tui/helpline.c:4:
> [17:38:21] In function '
On Fri, Oct 26, 2018 at 5:49 PM Martin Steigerwald wrote:
>
> This regression is gone with 4.19-rc8.
Thanks for the update!
> Martin Steigerwald - 11.09.18, 09:53:
> […]
> > Linus Torvalds - 02.09.18, 23:45:
> > > As usual, the rc2 release is pretty small. People are taking a
> >
> > With 4.19-
This regression is gone with 4.19-rc8.
Thanks,
Martin
Martin Steigerwald - 11.09.18, 09:53:
[…]
> Linus Torvalds - 02.09.18, 23:45:
> > As usual, the rc2 release is pretty small. People are taking a
>
> With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs
> with black screen when
On Mon 2018-10-22 00:38:43, Joe Perches wrote:
> On Mon, 2018-10-22 at 08:32 +0100, Greg KH wrote:
>
> > Greg Kroah-Hartman (7):
> > Code of Conduct Interpretation: Add document explaining how the Code
> > of Conduct is to be interpreted
> > Code of Conduct Interpretation: Properly re
On Mon, 2018-10-22 at 08:32 +0100, Greg KH wrote:
> Greg Kroah-Hartman (7):
> Code of Conduct Interpretation: Add document explaining how the Code of
> Conduct is to be interpreted
> Code of Conduct Interpretation: Properly reference the TAB correctly
> Code of Conduct: Provide
On Mon, Oct 15, 2018 at 08:49:15AM +0200, Greg KH wrote:
> Hi all,
>
> As mentioned last week, here's a -rc8 release as it seems needed.
>
> There were a lot of "little" pull requests this week, semi-normal for
> this late in the cycle, but a lot of them were "fix up the previous fix
> I just sen
On Mon, Oct 08, 2018 at 12:43:05PM -0600, Shuah Khan wrote:
> On Sun, Oct 7, 2018 at 9:48 AM Greg KH wrote:
> >
> > Hi all,
> >
> > Yet again, it's time for a kernel -rc release. This one is bigger than
> > -rc6 was, for a variety of unrelated reasons it seems. Lots of
> > different trees being
On Sun, Oct 7, 2018 at 9:48 AM Greg KH wrote:
>
> Hi all,
>
> Yet again, it's time for a kernel -rc release. This one is bigger than
> -rc6 was, for a variety of unrelated reasons it seems. Lots of
> different trees being merged this week, much more so than the previous
> one. Highlights includ
On 16.09.2018 21:22, Linus Torvalds wrote:
Hi,
> One was simply my own reaction to having screwed up my scheduling of
> the maintainership summit: yes, I was somewhat embarrassed about
> having screwed up my calendar, but honestly, I was mostly hopeful that
> I wouldn't have to go to the kernel
On 04.10.2018 16:57, Eric W. Biederman wrote:
> Very often people will propose patches that do solve their specific case
> but only do 10% or maybe 20% of what is needed for a general kernel
> level solution. For something that just works and does not cause
> maintenance problems in the long run.
On Sun, Oct 07, 2018 at 03:36:22PM -0700, Guenter Roeck wrote:
> On Sun, Oct 07, 2018 at 05:45:29PM +0200, Greg KH wrote:
> > Hi all,
> >
> > Yet again, it's time for a kernel -rc release. This one is bigger than
> > -rc6 was, for a variety of unrelated reasons it seems. Lots of
> > different tr
On 18.09.2018 03:30, Pavel Snajdr wrote:
Hi folks,
I usually try to stay out of political issues in software projects
(there're already too much real political problems, where people need
to stand up and push away actual oppressors), but now I have the bad
feeling that political (or more precisel
On Sun, Oct 07, 2018 at 05:45:29PM +0200, Greg KH wrote:
> Hi all,
>
> Yet again, it's time for a kernel -rc release. This one is bigger than
> -rc6 was, for a variety of unrelated reasons it seems. Lots of
> different trees being merged this week, much more so than the previous
> one. Highligh
Pavel Snajdr writes:
>
> We started our organization (vpsFree.org) on top of OpenVZ patch set and are
> now
> working to get vanilla up to the task of replacing the venerable 2.6.32-based
> OpenVZ 6 Linux-like thing. The new Code of Conduct is a guarantee for us, that
> we won't be laughed out of
On Sun, Sep 30, 2018 at 3:07 PM, Martin Steigerwald wrote:
> l...@lkcl.net - 30.09.18, 14:09:
>> the third is how UNICEF trains teachers to treat children as human
>> beings.
>
> During releasing a lot of limiting "stuff" I found that probably nothing
> written or said can hurt my feelings unles
l...@lkcl.net - 30.09.18, 14:09:
> > That written: Quite some of the rude mails that contained swearwords
> > I read from you have been about code, not persons. I think this is
> > an important distinction. I do not have much of an issue with
> > swearing at code :), especially when it is in some h
> That written: Quite some of the rude mails that contained swearwords I
> read from you have been about code, not persons. I think this is an
> important distinction. I do not have much of an issue with swearing at
> code :), especially when it is in some humorous way.
absolutely, and this is
https://linux.slashdot.org/story/18/09/27/1529236/linus-torvalds-on-linuxs-code-of-conduct#comments
linus: ah... um... okay so this is beginning to remind me of dr who
films, the comedy film "the world's end", and various other b-movie
horror shows where people were taken over through mind-control
On Sun, Sep 23, 2018 at 08:05:23PM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Sun, Sep 23, 2018 at 7:57 PM Greg KH wrote:
> > As almost everyone knows, it's been an "interesting" week from a social
> > point-of-view. But from the technical side, -rc5 looks totally normal.
>
> Thanks for
Hi Greg,
On Sun, Sep 23, 2018 at 7:57 PM Greg KH wrote:
> As almost everyone knows, it's been an "interesting" week from a social
> point-of-view. But from the technical side, -rc5 looks totally normal.
Thanks for, and congratulations with, your first non-stable release!
> As usual, please go
linus, hi,
i haven't been able to get hold of a copy of "invisible dynamics" yet
however my partner did track down a... "translation" of the six
systemic laws from family to organisational principles (from where
they were originally derived). the book puts the systemic laws in a
clearer way and e
Hi Pavel,
and how about if we viewed the new Code of Conduct as about the same
thing as BitKeeper was for the development process?
You should view the Code of Conduct for what it is, as I referenced
previously with real world examples, the evidence shows that it is just
a ploy to take control
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8a104f8b5867c682d994ffa7a74093c54469c11f
ahh, guys? ah... i'm going to try *really* hard to follow the advice
that's listed here ok?
http://www.pndc.com/documents/_PDF%20Text-PNDC%20WORKS.pdf it's a
little challenging
On 2018-09-17 23:09, Michael Woods wrote:
The Code of Conflict was perfectly fine. Whomever convinced you to add
the Code of Conduct was convincing you to give control over to a
social justice initiative that has no interest in the kernel's core
function or reason for existence.
Hi Michael,
Hi Linus,
> The one change that stands out and merits mention is the code of
> conduct addition...
The Code of Conflict was perfectly fine. Whomever convinced you to add
the Code of Conduct was convincing you to give control over to a social
justice initiative that has no interest in the kerne
On Sun, 2018-09-16 at 12:22 -0700, Linus Torvalds wrote:
> Greg Kroah-Hartman (1):
> Code of Conduct: Let's revamp it.
I believe it would be better if this sort of change
had on-list and public discussion before being applied.
On Sun, Sep 16, 2018 at 12:22:43PM -0700, Linus Torvalds wrote:
> [ So this email got a lot longer than I initially thought it would
> get, but let's start out with the "regular Sunday release" part ]
>
> Another week, another rc.
>
Build results:
total: 135 pass: 134 fail: 1
Failed buil
The new kernel rc release is good news as always. The rest of this? not
so much.
"I can’t wait for the mass exodus from Linux now that it’s been
infiltrated by SJWs. Hahahah" -- @CoralineAda on Twitter [1][2]
You really want people like this attempting to sabotage FOSS projects?
I for one am not
hi linus,
just saw the note on slashdot. i just wanted to say how amazed,
relieved and delighted i was to see what you wrote. that you
recognised that you needed to reflect, *sought feedback*, and, most
importantly, were willing and able to discuss that and ask publicly.
as the longest-serving c
Hi Linus.
I was "around linux-kernel" some 10 years ago and still to this date
sometimes check e.g. lkml.org where I happened upon this; felt it hard
to resist commenting on one specific bit...
Whereas you concentrate on net-positive effect on code quality of an at
times "crass" communication sty
Ville Syrjälä - 12.09.18, 19:10:
> On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote:
> > Cc´d Intel Gfx mailing list, in case somebody there knows something:
> >
> > Cc´d Thorsten for regression tracking… forgot initially. Can also
> > open bug report at a later time but so far I
On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote:
> Cc´d Intel Gfx mailing list, in case somebody there knows something:
>
> Cc´d Thorsten for regression tracking… forgot initially. Can also open
> bug report at a later time but so far I cannot provide many details
> about the
Cc´d Intel Gfx mailing list, in case somebody there knows something:
Cc´d Thorsten for regression tracking… forgot initially. Can also open
bug report at a later time but so far I cannot provide many details
about the issue.
Rafael J. Wysocki - 11.09.18, 10:17:
> On Tue, Sep 11, 2018 at 10:01 A
Hi,
On Tue, Sep 11, 2018 at 10:01 AM Martin Steigerwald wrote:
>
> Hi.
>
> Linus Torvalds - 02.09.18, 23:45:
> > As usual, the rc2 release is pretty small. People are taking a
>
> With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs
> with black screen when resuming from suspend o
Hi.
Linus Torvalds - 02.09.18, 23:45:
> As usual, the rc2 release is pretty small. People are taking a
With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs
with black screen when resuming from suspend or hibernation. With
4.18.1 it did not. Of course there have been userspace r
On 09/03/2018 12:09 PM, David Miller wrote:
From: Guenter Roeck
Date: Mon, 3 Sep 2018 11:22:02 -0700
The sparc32:allmodconfig build problem is the same as last week.
David - any interest/plan to get this fixed, or should I just drop
the build ?
I didn't see it, please give me a reference to
From: Guenter Roeck
Date: Mon, 3 Sep 2018 11:22:02 -0700
> The sparc32:allmodconfig build problem is the same as last week.
> David - any interest/plan to get this fixed, or should I just drop
> the build ?
I didn't see it, please give me a reference to the details.
Thanks.
On Sun, Sep 02, 2018 at 02:45:22PM -0700, Linus Torvalds wrote:
> As usual, the rc2 release is pretty small. People are taking a
> breather after the merge window, and it takes a bit of time for bug
> reports to start coming in and get identified. Plus people were
> probably still on vacation (par
From: Linus Torvalds
> Sent: 26 August 2018 22:49
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> This was a fairly frustrating merge window, partly because 4.19 looks
> to be a pretty big release (no single reason), and partly just due to
> random noise.
...
Time for 5.
On Mon, Aug 27, 2018 at 02:56:32PM -0700, Linus Torvalds wrote:
> On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
> >
> > Build results:
> > total: 132 pass: 129 fail: 3
>
> Thanks for running these. Looks like everything but the sparc thing is
> under control, and the sparc thing mi
On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
>
> Build results:
> total: 132 pass: 129 fail: 3
Thanks for running these. Looks like everything but the sparc thing is
under control, and the sparc thing might be one of those "big builds
don't work on sparc" ;(
Linus
On Mon, 27 Aug 2018 06:44:59 PDT (-0700), li...@roeck-us.net wrote:
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
So two weeks have passed, and the merge window for 4.19 is over.
[ ... ]
Anyway, go forth and test,
Build results:
total: 132 pass: 129 fail: 3
Faile
>
> On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds foundation.org> wrote:
> >
> > So two weeks have passed, and the merge window for 4.19 is over.
> >
>
>
> > Anyway, go forth and test,
> >
>
> I am seeing the errors use-after-free errors in mei_cl_write. dmesg as
> follows.
> Adding Tomas Wi
On Mon, Aug 27, 2018 at 11:13:11AM -0700, Christoph Hellwig wrote:
> On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> > When building sparc32 images, this results in the following
> > error.
> >
> > drivers/base/platform.c: In function 'setup_pdev_archdata':
> > drivers/base/platfo
On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds
wrote:
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> Anyway, go forth and test,
>
I am seeing the errors use-after-free errors in mei_cl_write. dmesg as follows.
Adding Tomas Winkler to the thread.
[ 12.602912] PM: Add
On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> When building sparc32 images, this results in the following
> error.
>
> drivers/base/platform.c: In function 'setup_pdev_archdata':
> drivers/base/platform.c:235:22: error: assignment from incompatible pointer
> type [-Werror=incom
On Mon, Aug 27, 2018 at 08:46:41AM -0700, Christoph Hellwig wrote:
> > sparc:
> >
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > esp_sbus_probe+0x408/0x6e8
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > sparc_lance_probe_one+0x428/0x4f
> >
> > Missing i
> sparc:
>
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> esp_sbus_probe+0x408/0x6e8
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> sparc_lance_probe_one+0x428/0x4f
>
> Missing initialization of coherent_dma_mask in the respective drivers.
>
> ---
> Each platf
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and the merge window for 4.19 is over.
>
[ ... ]
>
> Anyway, go forth and test,
>
Build results:
total: 132 pass: 129 fail: 3
Failed builds:
riscv:defconfig
riscv:allnoconfig
80 matches
Mail list logo
