From: "David S. Miller" <davem@redhat.com>
To: chas@locutus.cmf.nrl.navy.mil
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][ATM] obselete some atm_vcc members
Date: Sat, 08 Mar 2003 12:50:24 -0800 (PST) [thread overview]
Message-ID: <20030308.125024.44441125.davem@redhat.com> (raw)
In-Reply-To: <200303051547.h25FleGi006585@locutus.cmf.nrl.navy.mil>
From: chas williams <chas@locutus.cmf.nrl.navy.mil>
Date: Wed, 05 Mar 2003 10:47:40 -0500
it has been suggested that atm_vcc has redundant members with
struct sock.
this patch removes family, tx_inuse, rx_inuse, and recvq from
atm_vcc in favor of sk->family, sk->wmem_alloc, sk->rmem_alloc,
and sk->receive_queue (respectively).
Applied, but Chas please build fresh patches in the future.
This stuff was all against a tree which still had the atm_dev
semaphore instead of the new spinlock. Therefore half of the patches
rejected and I had to put these parts in by hand.
I did it this time, but really this needs to be done by you.
:-)
next prev parent reply other threads:[~2003-03-08 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 15:47 chas williams
2003-03-08 20:50 ` David S. Miller [this message]
2003-03-09 12:35 ` chas williams
2003-03-09 21:34 ` David S. Miller
2003-03-10 0:50 ` chas williams
2003-03-10 5:11 ` 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=20030308.125024.44441125.davem@redhat.com \
--to=davem@redhat.com \
--cc=chas@locutus.cmf.nrl.navy.mil \
--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®