netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: irda-users@lists.sourceforge.net, netdev@oss.sgi.com,
	Martin Diehl <lists@mdiehl.de>
Subject: Re: [PATCH] (1/5) get rid of useless hashbin in irtty
Date: Fri, 15 Aug 2003 16:05:46 -0700	[thread overview]
Message-ID: <20030815230546.GA31831@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030815154608.56cf0551.shemminger@osdl.org>

On Fri, Aug 15, 2003 at 03:46:08PM -0700, Stephen Hemminger wrote:
>
> Working on converting IRDA to new netdevice semantics,

	I hope you realised that this is most likely 2.7.X
material. There is not enough IrDA testing happening in 2.6.X to make
sure that this could work properly in the short time we have before
2.6.0. It usually take 3 months to get feedback on the 2.4.X
changes. Driver still have not caught up with the core changes in
2.6.X, so I don't feel like introducing more core changes that would
destabilise everything.
	I don't want to discourage you, because I know that this needs
to happen. Also, you may want to contact Martin Diehl, which is taking
care of irtty-sir and dongle drivers, so might have a more accurate
perpective on the problem and help on that.
	I'm not saying "No", I just want some way to reduce the risk
level. Having Martin involved is one good way.

> this is the first
> of some of the small things I found.
> 
> The irtty hashbin is created, maintained and never used.

	irtty is broken in 2.6.X, and the only thing that should
happen to it is complete removal.

> Motivation for removing is that the hashbin locking has problems with
> the locking assumptions in on network device removal.

	Please explain that, if there is a bug in hashbin, it need
fixing. I personally took care of making sure that hashbin locking is
sensible, so I have to assume that there is something wrong with
network device removal.
	Also note that the hashbin was created with NO_LOCK, so
hashbin locking can't be a problem ;-)

	Have fun...

	Jean

  reply	other threads:[~2003-08-15 23:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 22:46 [PATCH] (1/5) get rid of useless hashbin in irtty Stephen Hemminger
2003-08-15 23:05 ` Jean Tourrilhes [this message]
2003-08-16 12:20   ` David S. Miller
2003-08-17  0:14     ` Jean Tourrilhes
2003-08-17  0:58       ` David S. Miller
2003-08-17  1:11         ` Jean Tourrilhes
2003-08-17  1:09           ` David S. Miller
2003-08-17  1:36             ` Jean Tourrilhes
2003-08-18 16:03           ` Stephen Hemminger
2003-08-18 16:50             ` Jean Tourrilhes
2003-08-18 16:53               ` Jeff Garzik
2003-08-18 17:08                 ` Jean Tourrilhes
2003-08-19  0:07                   ` Jeff Garzik
2003-08-19 22:58                     ` [PATCH] kill old irtty Stephen Hemminger
2003-08-20  4:02                       ` David S. Miller
     [not found]         ` <Pine.LNX.4.44.0308171335050.1409-100000@notebook.home.mdiehl.de>
2003-08-18  5:18           ` [PATCH] (1/5) get rid of useless hashbin in irtty David S. Miller
     [not found]             ` <Pine.LNX.4.44.0308180959150.3006-100000@notebook.home.mdiehl.de>
2003-08-18  9:21               ` David S. Miller

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=20030815230546.GA31831@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=irda-users@lists.sourceforge.net \
    --cc=jt@hpl.hp.com \
    --cc=lists@mdiehl.de \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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).