public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-scsi@vger.kernel.org
Subject: Re: [patch 08/17] scsi: replace remaining __FUNCTION__ occurrences
Date: Sun, 30 Mar 2008 11:45:42 -0700	[thread overview]
Message-ID: <1206902742.6543.35.camel@brick> (raw)
In-Reply-To: <1206891402.4224.35.camel@localhost.localdomain>

On Sun, 2008-03-30 at 10:36 -0500, James Bottomley wrote:
> On Sun, 2008-03-30 at 08:07 -0700, Andrew Morton wrote:
> > On Sun, 30 Mar 2008 09:08:27 -0500 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> > 
> No, my complaint isn't that we can't do this ... given an infinite
> amount of time, everything can be done.  The problem is that time spent
> on SCSI is a finite and quite precious resource ... I allocate it like
> this:
> 
>      1. Bug fixes
>      2. Driver Maintenance
>      3. Feature Enhancments
>      4. Trivial Cleanups
> 
> However, for 4. I do still require there to be some actual benefit to
> the cleanup (remove a warning, eliminate dead code) etc which is what
> I'm still struggling to find with the __FUNCTION__->__func__
> transformation.

Well, instead of spending energy arguing over this, could you let me
know what files are conflicting with acpi causing a revert...then
I can send you the non-conflicting stuff in a new patch, and get the
rest in through the acpi tree?


Harvey


  reply	other threads:[~2008-03-30 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:48 [patch 08/17] scsi: replace remaining __FUNCTION__ occurrences akpm
2008-03-28 22:35 ` James Bottomley
2008-03-28 22:45   ` Andrew Morton
2008-03-28 22:48     ` Harvey Harrison
2008-03-30 14:08     ` James Bottomley
2008-03-30 15:07       ` Andrew Morton
2008-03-30 15:36         ` James Bottomley
2008-03-30 18:45           ` Harvey Harrison [this message]
2008-03-31 19:34 ` Mike Christie
2008-03-31 19:39   ` Andrew Morton

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=1206902742.6543.35.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-scsi@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