linux-kernel - Re: [PATCH] Fix collateral damage to top level Makefile

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 for Android: free password hash cracker in your pocket

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

Message-ID: <487F6CE8.8090203@freescale.com>
Date:	Thu, 17 Jul 2008 10:01:44 -0600
From:	John Rigby <jrigby@...escale.com>
To:	Grant Likely <grant.likely@...retlab.ca>
CC:	petkovbb@...glemail.com, linux-kernel@...r.kernel.org,
	benh@...nel.crashing.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] Fix collateral damage to top level Makefile

Grant,

I owe you on this one.  Sorry.

John

Grant Likely wrote:
> From: Grant Likely <grant.likely@...retlab.ca>
>
> The patch named "powerpc/mpc5121: Add clock driver", also contained
> an unrelated and bogus change to the top-level makefile.  This patch
> backs out the bad bit.
>
> SHA1 of offending patch: 137e95906e294913fab02162e8a1948ade49acb5)
>
> Signed-off-by: Grant Likely <grant.likely@...retlab.ca>
> ---
>
> If the maintainer who picked up this patch (Grant Likely) had done
> his job, this cack-up never would have happened.  Why do we still
> have to deal with such sloppy individuals?
>
> Ben/Linus;  I assume one of you will want to pick this up soonish?
> Otherwise, I'll add it to my tree and it will be part of my next
> pull request.
>
> g.
>
>  Makefile |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 1564577..6192922 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,4 +1,3 @@
> -FRED=42
>  VERSION = 2
>  PATCHLEVEL = 6
>  SUBLEVEL = 26
>
>
>   

--
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/