linux-kernel - Re: [GIT PULL] tracing: Updates for 4.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFyZXjNG9R4LKGhvkNguokUrKVsvegQn9B_Tf67FXm307Q@mail.gmail.com>
Date:	Fri, 6 Nov 2015 14:15:48 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [GIT PULL] tracing: Updates for 4.4

On Fri, Nov 6, 2015 at 2:09 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> This was reported against linux-next on Nov 2 by Sergey Senozhatsky who
> supplied a fix patch that I then used as the merge conflict resolution
> from Nov 3 onward (which everyone involved knew about) ...

Ok, so the problem is that even though a maintainer is aware of the
semantic conflict, the pull request doesn't talk about it.

A lot of maintainers *do* let me know, which I really appreciate, not
only because it avoids the surprise, but because it happens that I
miss these semantic conflicts.

Sometimes the semantic conflict is something that simply doesn't show
up on x86-64 build I do.  Or I was on the road and didn't do a full
allmodconfig build. Or it needs very specific config options etc. Or I
just screw up. When the pull message warns me about it, that will
help.

But maybe it's one of those things that isn't written down, and people
don't think about as part of doing their pull request, so they forget.

                  Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/