public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Fix modutils to check ELF symbol index
Date: Tue, 21 Aug 2001 14:55:01 +1000	[thread overview]
Message-ID: <29071.998369701@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 20 Aug 2001 10:34:18 MST." <20010820103418.A15514@lucon.org>

On Mon, 20 Aug 2001 10:34:18 -0700, 
"H . J . Lu" <hjl@lucon.org> wrote:
>Hi Keith,
>
>All my previous email sent to you are bounced. I am sending this to the
>kernel mailing list, hoping you will read it..

My mail logs for August only show 2 attempts from 24.176.137.160, both
in the past 12 hours.  The first was blocked with a 451 response
because the reverse DNS lookup failed, blame home.com for not doing
anything about spammers.  The second got through because reverse DNS
worked.

Patch will be in modutils 2.4.8, thanks.


      reply	other threads:[~2001-08-21  4:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20 17:34 PATCH: Fix modutils to check ELF symbol index H . J . Lu
2001-08-21  4:55 ` Keith Owens [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=29071.998369701@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=hjl@lucon.org \
    --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