From: Michal Ostrowski <mostrows@speakeasy.net>
To: James Morris <jmorris@intercode.com.au>
Cc: Stephen Hemminger <shemminger@osdl.org>,
"David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com
Subject: Re: [PATCH 2.5.72] (1/3) PPPoE cleanup [TRIVIAL]
Date: 22 Jun 2003 19:26:06 -0400 [thread overview]
Message-ID: <1056324366.26751.123.camel@brick.watson.ibm.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0306230157140.578-100000@excalibur.intercode.com.au>
Debugging stuff can go. I kept it in for future debugging but haven't
found it of much use.
On Sun, 2003-06-22 at 11:59, James Morris wrote:
> On Fri, 20 Jun 2003, Stephen Hemminger wrote:
>
> > This is a cleanup patch, no change in functionality.
> > - Get rid of debug macro's that aren't used anywhere in the code.
>
> I'm guessing that Michal wants to leave these in for future debugging?
>
>
> - James
--
Michal Ostrowski <mostrows@speakeasy.net>
prev parent reply other threads:[~2003-06-22 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 0:31 [PATCH 2.5.72] (1/3) PPPoE cleanup [TRIVIAL] Stephen Hemminger
2003-06-22 15:59 ` James Morris
2003-06-22 23:26 ` Michal Ostrowski [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=1056324366.26751.123.camel@brick.watson.ibm.com \
--to=mostrows@speakeasy.net \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).