From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Thomas Graf <tgraf@suug.ch>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com
Subject: Re: path: module replay
Date: Wed, 19 Jan 2005 15:02:44 +0100 [thread overview]
Message-ID: <41EE6884.9010904@trash.net> (raw)
In-Reply-To: <1106141706.1048.953.camel@jzny.localdomain>
jamal wrote:
>
>And we exchanged emails on this topic already in private and you said
>you will fix and send out the patch;-> So please do just that or you can
>wait until i have more time and my hardware at the same spot.
>
I said I'm going to remove the bogus module loading changes and
apply the patch if there aren't more problems. But there are, and
my time is limited too, so I'm going to wait for a new patch.
Regards
Patrick
next prev parent reply other threads:[~2005-01-19 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 18:35 patch: namsiz Jamal Hadi Salim
2005-01-16 18:49 ` Patrick McHardy
2005-01-16 18:56 ` Thomas Graf
2005-01-16 19:17 ` Jamal Hadi Salim
2005-01-16 19:32 ` path: module replay jamal
2005-01-16 19:43 ` Patrick McHardy
2005-01-16 19:50 ` Patrick McHardy
2005-01-19 4:26 ` Patrick McHardy
2005-01-19 13:35 ` jamal
2005-01-19 14:02 ` Patrick McHardy [this message]
2005-01-24 13:28 ` jamal
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=41EE6884.9010904@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).