From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, samuel@sortiz.org
Subject: Re: [patch 09/11] irda: replace __FUNCTION__ with __func__
Date: Wed, 30 Jul 2008 17:04:32 -0700 [thread overview]
Message-ID: <20080730170432.8daf3c38.akpm@linux-foundation.org> (raw)
In-Reply-To: <1217462067.4338.0.camel@brick>
On Wed, 30 Jul 2008 16:54:27 -0700
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> On Wed, 2008-07-30 at 16:52 -0700, Andrew Morton wrote:
> > On Wed, 30 Jul 2008 16:42:36 -0700 (PDT)
> > David Miller <davem@davemloft.net> wrote:
> >
> > > From: akpm@linux-foundation.org
> > > Date: Wed, 30 Jul 2008 12:37:42 -0700
> > >
> > > > From: Harvey Harrison <harvey.harrison@gmail.com>
> > > >
> > > > __FUNCTION__ is gcc-specific, use __func__
> > > >
> > > > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> > > > Cc: Samuel Ortiz <samuel@sortiz.org>
> > > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > >
> > > This gets rejects because it conflicts with the down_try()
> > > changes that went into Linus's tree recently. Specifically
> > > this occurs in sir_dev.c
> >
> > urgh, OK, sorry. I'll hang onto it, see how we get along next time.
>
> I'll try again at -rc2 time perhaps? Or I can just regen later tonight
> and resend if you prefer.
>
Could. But that would muck up Rusty's patch, or linux-next.
Then again, Rusty's full down_try() patch won't be making it into
2.6.27 and David tends to merge little cleanups like this into -rc2 (or
later) so perhaps that's the way to go.
<fixes that reject for the twelfth time>
I'll resend.
prev parent reply other threads:[~2008-07-31 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:37 [patch 09/11] irda: replace __FUNCTION__ with __func__ akpm
2008-07-30 23:42 ` David Miller
2008-07-30 23:52 ` Andrew Morton
2008-07-30 23:54 ` Harvey Harrison
2008-07-31 0:04 ` Andrew Morton [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=20080730170432.8daf3c38.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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;
as well as URLs for NNTP newsgroup(s).