From: Chris Metcalf <cmetcalf@tilera.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: bad commit in the tile tree
Date: Wed, 16 May 2012 20:19:06 -0400 [thread overview]
Message-ID: <4FB443FA.1070003@tilera.com> (raw)
In-Reply-To: <20120517091417.62c65eea7002be18d8af2f34@canb.auug.org.au>
On 5/16/2012 7:14 PM, Stephen Rothwell wrote:
> Hi Chris,
>
> The top commit on the tile tree has a bad description ("usb hackery" does
> not tell us anything), sprinkles stuff (mainly printk()s) all over the
> generic usb code and is not signed off by anyone ...
>
> I assume it is a debugging patch (or similar) and should *not* be in
> linux-next.
>
> I will use the version of the tile tree from next-20120516 for today
> (unless you update your tree very soon).
Oops :-) It is debugging hackery. I committed it to do work on a
different branch, which I then pushed, forgetting that by default I'd push
the linux-next branch as well. Fixed now. Sorry!
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
prev parent reply other threads:[~2012-05-17 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 23:14 linux-next: bad commit in the tile tree Stephen Rothwell
2012-05-17 0:19 ` Chris Metcalf [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=4FB443FA.1070003@tilera.com \
--to=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox