All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Call for 2.8.0 soon
Date: Thu, 19 May 2005 06:24:02 +0000	[thread overview]
Message-ID: <20030629001925.0203d558.khali@linux-fr.org> (raw)
In-Reply-To: <3EE7C67A.4040703@paradyne.com>


> OK I think we are getting close.

Looks so, yes.

> - GCC 3.3 warnings Khali is working?

I've fixed some warnings these days, but not the GCC 3.2 ones. Note that
I don't have GCC 3.3 anyway, so I can't say anything about this one. We
had a report from a Japanese user (Ishikawa, Chiaki) about GCC 3.3, it
seems that it has more to do with Makefiles than with code by itself. I
think MDS will handle this better than I would.

Two warnings remain (apart from ones possibly generated by GCC 3.2):

1* via686a_find defined but not used. I would #if 0/#endif the function,
is that the right thing to do?

2* Some warnings in the config file parser. AFAIK, this is generated
code. I don't know how to fix these (if it is only possible). Maybe we
can just define -Wno-unused for these specific files, but I don't know
how to do this either. Anyone?

> - UTF issue fixed for new perls, now we need a fix for old perls

Should be working now.

> let's try to wrap things up and release in a week?

Would be great :)

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  parent reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:23 Call for 2.8.0 soon Mark D. Studebaker 
2005-05-19  6:23 ` Philip Pokorny
2005-05-19  6:23 ` Jean Delvare
2005-05-19  6:23 ` Philip Pokorny
2005-05-19  6:23 ` Mark D. Studebaker 
2005-05-19  6:23 ` Greg KH
2005-05-19  6:23 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare [this message]
2005-05-19  6:24 ` Mark D. Studebaker 
2005-05-19  6:24 ` Jean Delvare

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=20030629001925.0203d558.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.