mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: chas williams <chas@locutus.cmf.nrl.navy.mil>
Cc: linux-atm-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ATM] second pass at fixing atm spinlock
Date: Wed, 2 Apr 2003 08:18:47 +0100	[thread overview]
Message-ID: <20030402081847.A22335@infradead.org> (raw)
In-Reply-To: <200304011628.h31GSXGi000846@locutus.cmf.nrl.navy.mil>; from chas@locutus.cmf.nrl.navy.mil on Tue, Apr 01, 2003 at 11:28:33AM -0500

On Tue, Apr 01, 2003 at 11:28:33AM -0500, chas williams wrote:
> >ftp://ftp.cmf.nrl.navy.mil/pub/chas/linux-atm/2_5_64_atm_dev_lock.patch
> 
> i have made an equivalent version of these patches for 2.4.20 in hopes
> of getting more feedback.
> 
> ftp://ftp.cmf.nrl.navy.mil/pub/chas/linux-atm/2_4_20_atm_dev_lock.patch
> 
> (only the nicstar, fore200e, eni and he (included) driver support the
> new smp 'safe' locking)

You always include the he driver in your patches, what about cleaning it up
and submitting it first?


  parent reply	other threads:[~2003-04-02  7:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 22:28 chas williams
2003-03-28 10:07 ` Duncan Sands
2003-03-28 13:08   ` chas williams
2003-04-01 16:28 ` chas williams
2003-04-02  0:45   ` [Linux-ATM-General] " Till Immanuel Patzschke
2003-04-02  4:00     ` chas williams
2003-04-02  7:18   ` Christoph Hellwig [this message]
2003-04-02 12:11     ` chas williams
2003-04-03 18:46 ` [ATM] a few more changes for people to test chas williams
2003-04-15 18:58   ` [ATM] more changes available for testing chas williams

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=20030402081847.A22335@infradead.org \
    --to=hch@infradead.org \
    --cc=chas@locutus.cmf.nrl.navy.mil \
    --cc=linux-atm-general@lists.sourceforge.net \
    --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®