From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: irda-users@lists.sourceforge.net,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] : ir250_cache_wait_data-2.diff
Date: Mon, 17 Jun 2002 18:11:28 -0700 [thread overview]
Message-ID: <20020617181128.F6338@bougret.hpl.hp.com> (raw)
In-Reply-To: <3D0A7219.6000303@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Jun 14, 2002 at 06:45:45PM -0400
On Fri, Jun 14, 2002 at 06:45:45PM -0400, Jeff Garzik wrote:
> Patch did not apply... I think you're a victim of __FUNCTION__
> cleanups, possibly. Whoever did those in recent 2.5.x kernels didn't
> bother notifying any maintainers :(
By the way, is there any more cleanups in the pipeline ? I
mean, the whitespace cleanups missed 50% of the code and the
__FUNCTION__ cleanups missed 90% of the occurences, so should I expect
more or can I redo my patches this week ?
Thanks...
Jean
prev parent reply other threads:[~2002-06-18 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 0:53 [PATCH] : ir250_cache_wait_data-2.diff Jean Tourrilhes
2002-06-14 22:45 ` Jeff Garzik
2002-06-18 1:11 ` Jean Tourrilhes [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=20020617181128.F6338@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=irda-users@lists.sourceforge.net \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--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