linux-kernel - Re: [GIT PULL] xtensa: patchset for v3.11-rc1

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>] [day] [month] [year] [list]

Message-ID: <CA+55aFxqXHvDqWO7rqqL6PExsEXn6kfUKRnPFsg89SRq_a74Hw@mail.gmail.com>
Date:	Thu, 11 Jul 2013 12:33:38 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Zankel <chris@...kel.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] xtensa: patchset for v3.11-rc1

On Thu, Jul 11, 2013 at 11:06 AM,  <chris@...kel.net> wrote:
> Hi Linus,
>
> Would be great if you could pull the Xtensa tree. Some of the changes were
> dependent on the timers-core patchset, hence the 'merge' message
> (I think that's the right way to do it?)

Grr. I hate it when people do this. Your merge message sucks. It just
says "Merge branch .." without explaining what the merge does and
*why* it does it.

We have a policy of good commit messages in the kernel.  That is
*doubly* true for cross-subsystem merges that can be so much harder to
understand, and really need very explicit reasons for existing in the
first place.

I've pulled this, but please avoid doing things like this in the future..

              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/