From: John Rigby <jrigby@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: petkovbb@googlemail.com, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] Fix collateral damage to top level Makefile
Date: Thu, 17 Jul 2008 10:01:44 -0600 [thread overview]
Message-ID: <487F6CE8.8090203@freescale.com> (raw)
In-Reply-To: <20080717070549.30755.13083.stgit@trillian.secretlab.ca>
Grant,
I owe you on this one. Sorry.
John
Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.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@secretlab.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
>
>
>
prev parent reply other threads:[~2008-07-17 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 7:06 [PATCH] Fix collateral damage to top level Makefile Grant Likely
2008-07-17 7:27 ` Paul Mundt
2008-07-17 8:50 ` Benjamin Herrenschmidt
2008-07-17 9:49 ` Boris Petkov
2008-07-17 15:11 ` Grant Likely
2008-07-17 16:01 ` John Rigby [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487F6CE8.8090203@freescale.com \
--to=jrigby@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.