linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Maxey <dwm@enoyolf.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Jim Paris <jim@jtan.com>,
	linux-ide@vger.kernel.org,
	smartmontools-support@lists.sourceforge.net
Subject: Re: smartctl causing HSM violation on sata_nv, 2.6.18
Date: Mon, 02 Oct 2006 18:24:06 -0500	[thread overview]
Message-ID: <20061002232406.517005@bebe.enoyolf.org> (raw)
In-Reply-To: <45215B86.3020106@gmail.com>


On Tue, 03 Oct 2006 03:33:42 +0900, Tejun Heo wrote:
> 
> I've got delivery failure notice for smartmontools-support mail address. 
>   Does anyone know how to contact smartmontools author?
> 

Bruce Allen <ballen@gravity.phys.uwm.edu> is the maintainer.

++doug


      reply	other threads:[~2006-10-02 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 18:33 smartctl causing HSM violation on sata_nv, 2.6.18 Jim Paris
2006-09-28  6:54 ` Tejun Heo
2006-09-28  8:09   ` Jim Paris
2006-10-02 18:33     ` Tejun Heo
2006-10-02 23:24       ` Doug Maxey [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=20061002232406.517005@bebe.enoyolf.org \
    --to=dwm@enoyolf.org \
    --cc=htejun@gmail.com \
    --cc=jim@jtan.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /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).