From: Marcel Holtmann <marcel@holtmann.org>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
"David S. Miller" <davem@davemloft.net>,
Network Development Mailing List <netdev@oss.sgi.com>
Subject: Re: [PATCH][BLUETOOTH] kill bt_sock_alloc
Date: Thu, 10 Mar 2005 20:51:03 +0100 [thread overview]
Message-ID: <1110484263.8395.6.camel@pegasus> (raw)
In-Reply-To: <20050309184314.GA29053@conectiva.com.br>
Hi Arnaldo,
> > > Looks good to me. Marcel I'd suggest for you to apply this patch.
> > > It helps in reducing overall size of the socket structures.
> >
> > I didn't got the time to review and test it. Will do that next week.
>
> OK, take your time, but the changes are rather small, I left renaming
> all the _pinfo (l2cap_pinfo, for instance) to _sock (for consistency
> with all the other net families) to keep the patch small.
the patch is fine so far, but you forgot to change cmtp/sock.c. Please
do this and resend it.
Send a second patch on top this one which is doing the renaming from
*_pinfo to *_sock. I am fine with the renaming, but I like to have this
in two separate patches.
> For now I'll work on doing this same change to the HAM radio protocols,
> coordinating with Ralf Baechle and then wait for your comments to finally
> kill sk_protinfo and move on to introduce struct connection_sock.
When doing this, please split these changes into patches for
net/bluetooth/, net/bluetooth/rfcomm/ and net/bluetooth/*/.
Regards
Marcel
prev parent reply other threads:[~2005-03-10 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 9:49 [PATCH][BLUETOOTH] kill bt_sock_alloc Arnaldo Carvalho de Melo
2005-03-08 9:52 ` Arnaldo Carvalho de Melo
2005-03-09 17:35 ` Max Krasnyansky
2005-03-09 17:43 ` Arnaldo Carvalho de Melo
2005-03-09 18:24 ` Marcel Holtmann
2005-03-09 18:43 ` Arnaldo Carvalho de Melo
2005-03-10 19:51 ` Marcel Holtmann [this message]
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=1110484263.8395.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=acme@conectiva.com.br \
--cc=davem@davemloft.net \
--cc=maxk@qualcomm.com \
--cc=netdev@oss.sgi.com \
/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).