All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Boris Kurktchiev <techstuff@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Posible memory leak!?
Date: Mon, 12 May 2003 11:06:03 -0700	[thread overview]
Message-ID: <20030512180603.GA28726@kroah.com> (raw)
In-Reply-To: <200305112342.27469.techstuff@gmx.net>

On Sun, May 11, 2003 at 11:42:27PM -0400, Boris Kurktchiev wrote:
> Now when I did the upgrade to 2.4.20 I did not change my config file at all
> the only new thing that I added was adding usb-to-usb networking ( i have a
> zaurus)

What driver are you using for this?  usbdnet?  I'd recommend using the
in-kernel support for this device instead.  I think the latest versions
of usbnet support it.

thanks,

greg k-h

  parent reply	other threads:[~2003-05-12 18:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10  6:29 [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-10  7:38 ` Muli Ben-Yehuda
2003-05-12  3:26   ` Chris Friesen
2003-05-12  3:32     ` Doug McNaught
2003-05-12  3:42       ` Posible memory leak!? Boris Kurktchiev
2003-05-12 11:17         ` Boris Kurktchiev
     [not found]           ` <200305131158.h4DBw2u30860@Port.imtp.ilyichevsk.odessa.ua>
2003-05-13 18:17             ` Boris Kurktchiev
2003-05-12 18:06         ` Greg KH [this message]
2003-05-12  4:33       ` [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-12 13:23         ` Doug McNaught
2003-05-12 14:07           ` Chris Friesen
2003-05-12  3:53     ` Frank Cusack
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 18:15 Posible memory leak!? Boris Kurktchiev
2003-05-14  6:56 ` Denis Vlasenko
2003-05-14 14:12   ` Boris Kurktchiev
2003-05-15  5:51     ` Denis Vlasenko
2003-05-15 14:24       ` Boris Kurktchiev
2003-05-16  8:48         ` Denis Vlasenko

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=20030512180603.GA28726@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=techstuff@gmx.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 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.