public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ralf Dauberschmidt" <rfk@digitalstyle.de>
To: <linux-kernel@vger.kernel.org>
Subject: AW: sock_alloc() symbol removed in 2.6.10
Date: Fri, 16 Jun 2006 21:44:37 +0200	[thread overview]
Message-ID: <002a01c6917d$4ddbfc80$0200000a@redstorm> (raw)
In-Reply-To: <1150473371.3070.0.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> what driver are you looking at that wants to use it?

At university we are currently porting a project from a 2.4 series kernel to
a recent 2.6 series kernel. This project uses the sock_alloc() function.


Stephen Smalley wrote:
> Also, it would be better to use sock_create_lite() to ensure proper
> handling by the security subsystem.  See:
> http://marc.theaimsgroup.com/?l=git-commits-head&m=108407590404054&w=2

Thanks for the hint, I will use sock_create_lite() instead.


Regards,
 Ralf Dauberschmidt


      parent reply	other threads:[~2006-06-16 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 10:54 sock_alloc() symbol removed in 2.6.10 Ralf Dauberschmidt
2006-06-16 15:56 ` Arjan van de Ven
2006-06-16 19:20   ` Stephen Smalley
2006-06-16 19:44   ` Ralf Dauberschmidt [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='002a01c6917d$4ddbfc80$0200000a@redstorm' \
    --to=rfk@digitalstyle.de \
    --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