mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@au1.ibm.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>
Subject: Re: [PATCH] sx tty_driver add .owner field remove MOD_INC_DEC_USE_COUNT
Date: Fri, 30 May 2003 18:05:24 +1000	[thread overview]
Message-ID: <20030530080556.EC79C17DE1@ozlabs.au.ibm.com> (raw)
In-Reply-To: Your message of "Thu, 29 May 2003 14:35:10 MST." <12430000.1054244110@w-hlinder>

In message <12430000.1054244110@w-hlinder> you write:
> --On Thursday, May 29, 2003 12:02:50 PM -0700 Greg KH <greg@kroah.com> wrote:
> 
> > 
> > Ick, this patch should be reverted, it should not be removing
> > sx_hungup() for no reason.  I think Hanna agrees with this.
> 
> Yup. Sorry. Not sure what happened there. Here is the patch
> to replace the sx_hangup function. This is based off 2.5.70-bk3
> and I have compiled it but dont have the hardware to test it.

Yes, but I don't think you need to put back the comment about
decrementing use counts 8)

> +/* I haven't the foggiest why the decrement use count has to happen
> +   here. The whole linux serial drivers stuff needs to be redesigned.
> +   My guess is that this is a hack to minimize the impact of a bug
> +   elsewhere. Thinking about it some more. (try it sometime) Try
> +   running minicom on a serial port that is driven by a modularized
> +   driver. Have the modem hangup. Then remove the driver module. Then
> +   exit minicom.  I expect an "oops".  -- REW */

Cheers,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-05-30  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305270126.h4R1QjA3029554@hera.kernel.org>
2003-05-29 19:02 ` Greg KH
2003-05-29 21:35   ` Hanna Linder
2003-05-30  8:05     ` Rusty Russell [this message]
2003-05-30 17:48       ` Hanna Linder

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=20030530080556.EC79C17DE1@ozlabs.au.ibm.com \
    --to=rusty@au1.ibm.com \
    --cc=hannal@us.ibm.com \
    --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

all inboxes | Powered by JetHome®