linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0: broken ums_eneub6250
Date: Sun, 7 Aug 2011 21:22:31 -0700	[thread overview]
Message-ID: <20110808042231.GA6248@kroah.com> (raw)
In-Reply-To: <j1mm4l$55a$1@ID-44327.news.uni-berlin.de>

On Sun, Aug 07, 2011 at 08:39:20PM +0200, Andreas Hartmann wrote:
> Hi,
> 
> obviously, nobody seems to be interested to work on this bug. Until it's
> fixed: There is a workaround to get the device working again with 2.6.39
> and 3.0 - just remove the unusable ums-eneub6250.ko and replace it with
> the complete old and fine keucr-module - staging but working :-)
> 
> https://bugzilla.novell.com/show_bug.cgi?id=709243#c1

How about working on a patch for the in-kernel version of the code to
get it to work properly so we can resolve this?  Given that very few
people actually have this hardware, it's hard for us to work on the
driver.

If you could run 'git bisect' to try to find the problem, that would be
appreciated.

thanks,

greg k-h

  reply	other threads:[~2011-08-08  4:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hjXX6-Ee-55@gated-at.bofh.it>
     [not found] ` <hk6nE-6kT-5@gated-at.bofh.it>
     [not found]   ` <hk7Wq-mZ-1@gated-at.bofh.it>
2011-08-07 18:39     ` Linux 3.0: broken ums_eneub6250 Andreas Hartmann
2011-08-08  4:22       ` Greg KH [this message]
2011-08-08  8:16         ` Andreas Hartmann
2011-08-08 15:33           ` Greg KH
2011-08-08 19:25             ` Andreas Hartmann
2011-08-09  3:39               ` Greg KH
2011-08-10 12:05                 ` Andreas Hartmann
2011-07-29 16:14 Andreas Hartmann
2011-07-30  1:14 ` Randy Dunlap
2011-07-30  2:50   ` Huajun Li
2011-07-30  6:15     ` Andreas Hartmann

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=20110808042231.GA6248@kroah.com \
    --to=greg@kroah.com \
    --cc=andihartmann@01019freenet.de \
    --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;
as well as URLs for NNTP newsgroup(s).