[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#611216: marked as done (linux-2.6 - New monitor chip: w83795)



Your message dated Fri, 19 Jul 2013 18:00:49 +0200
with message-id <20130719160049.GD15243@inutil.org>
and subject line Re: Bug#611216: driver found outside Debian
has caused the Debian Bug report #611216,
regarding linux-2.6 - New monitor chip: w83795
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
611216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611216
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-30
Severity: important

Please add support for new monitor chip w83795.

Bastian

-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Version: 2.6.37-1

On Mon, Jun 06, 2011 at 05:36:33PM +0100, Ben Hutchings wrote:
> On Mon, Jun 06, 2011 at 11:25:32AM +0200, Steffen Möller wrote:
> > Hello,
> > 
> > I need this for lm-sensors, indeed. Is there anything available through
> > official Debian channels by now?
> > 
> > Google found this for me
> > 
> > http://khali.linux-fr.org/devel/misc/w83795/
> >   features a driver for this chip
> [...]
> 
> It's included in Linux 2.6.37 and later versions.  Bastian wanted
> to add it to the kernel in 'squeeze' based on 2.6.32.

Marking as closed in 2.6.37.

Cheers,
        Moritz

--- End Message ---

Reply to: