public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@tilera.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch/tile: Miscellaneous cleanup changes.
Date: Sun, 27 Jun 2010 12:39:49 -0400	[thread overview]
Message-ID: <4C277ED5.6020208@tilera.com> (raw)
In-Reply-To: <201006261156.28495.arnd@arndb.de>

On 6/26/2010 5:56 AM, Arnd Bergmann wrote:
> As far as I can tell, all the changes in this patch look reasonable, but
> as a rule you should never mix functional changes and cleanups in a single
> patch. This is both for review purposes as well as for being able to bisect
> specific regressions that might be introduced by the patch.
>   

Yes, I'll try to be more precise with my commits in the future.  I was
playing catch-up with a bunch of commits in our internal tree, which
uses Perforce.  The change migration process doesn't lend itself to
pulling individual commits out of Perforce and into git, and I also
worried about spamming LKML with dozens of small patches for the tile
architecture, which after all hasn't even been pulled into Linus's tree
yet.  And, of course, since few if any folks are actually running these
bits on their hardware yet (our hardware customers are likely all
running the sources we ship them), the bisection issue is less
critical.  But I will at least make sure to separate out cleanups and
bugfixes going forward.

Thanks!

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com


      reply	other threads:[~2010-06-27 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 21:04 [PATCH] arch/tile: Miscellaneous cleanup changes Chris Metcalf
2010-06-26  9:56 ` Arnd Bergmann
2010-06-27 16:39   ` 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=4C277ED5.6020208@tilera.com \
    --to=cmetcalf@tilera.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox