From: Jean Delvare <khali@linux-fr.org>
To: sensors@Stimpy.netroedge.com, linux-kernel@vger.kernel.org
Cc: greg@kroah.com, vsu@altlinux.ru
Subject: Re: [PATCH 2.6] Rework memory allocation in i2c chip drivers (second try)
Date: Sun, 18 Apr 2004 08:01:12 +0200 [thread overview]
Message-ID: <20040418080112.2617338f.khali@linux-fr.org> (raw)
In-Reply-To: <20040417145309.4831f2b6.khali@linux-fr.org>
Hu!? Any idea why this (duplicate) mail went through vger.kernel.org and
nivdia.com before reaching the lm_sensors mailing-list? Broken mail
server at nvidia, or what?
Just curious.
Thanks.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2004-04-18 6:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 17:10 [RFC 2.6] Rework memory allocation in i2c chip drivers Jean Delvare
2004-04-03 19:07 ` Geert Uytterhoeven
2004-04-03 20:20 ` Sergey Vlasov
2004-04-09 17:31 ` Greg KH
2004-04-10 14:58 ` [PATCH 2.6] Rework memory allocation in i2c chip drivers (second try) Jean Delvare
2004-04-17 12:53 ` Jean Delvare
2004-04-18 6:01 ` Jean Delvare [this message]
2004-05-02 20:06 ` [PATCH 2.6] Fix memory leaks in w83781d and asb100 Jean Delvare
2004-05-05 22:18 ` Greg KH
2004-05-07 12:42 ` Jean Delvare
2004-05-07 22:34 ` Greg KH
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=20040418080112.2617338f.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@Stimpy.netroedge.com \
--cc=vsu@altlinux.ru \
/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