From: maximilian attems <janitor@sternwelten.at>
To: Margit Schubert-While <margitsw@t-online.de>
Cc: netdev@oss.sgi.com
Subject: Re: [patch 01/16] __FUNCTION__ string concatenation
Date: Thu, 2 Sep 2004 17:28:08 +0200 [thread overview]
Message-ID: <20040902152807.GA1894@stro.at> (raw)
In-Reply-To: <200409021302.22823.margitsw@t-online.de>
On Thu, 02 Sep 2004, Margit Schubert-While wrote:
> On Thu, 02 Sep 2004, Maximilian scribeth:
> > I don't have the hardware to do a run-time check.
> > It should not pose any problems though.
>
> Oh, I think we can safely say that, especially as TRACE
> is nowhere referenced ;-)
> (And therefore the patch is unnecessary)
yup nice hint it was used:
drivers/net/wireless/prism54/islpci_hotplug.c: /* TRACE(DRV_NAME); */
will resent patch that removes both.
--
maks
next prev parent reply other threads:[~2004-09-02 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 11:02 [patch 01/16] __FUNCTION__ string concatenation Margit Schubert-While
2004-09-02 15:28 ` maximilian attems [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-01 21:02 janitor
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=20040902152807.GA1894@stro.at \
--to=janitor@sternwelten.at \
--cc=margitsw@t-online.de \
--cc=netdev@oss.sgi.com \
/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).