From: Randy Dunlap <randy.dunlap@oracle.com>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org, stefano.babic@babic.homelinux.org,
randy.dunlap@oracle.com, kim.xx.lilliestierna@stericsson.com,
christian.bejram@stericsson.com,
daniel.martensson@stericsson.com
Subject: Re: [PATCH] [CAIF-RFC 5/8-v2] CAIF Protocol Stack
Date: Fri, 9 Oct 2009 09:43:06 -0700 [thread overview]
Message-ID: <20091009094306.4671ef33.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1255095571-6501-6-git-send-email-sjur.brandeland@stericsson.com>
On Fri, 09 Oct 2009 15:39:28 +0200 sjur.brandeland@stericsson.com wrote:
> From: Sjur Braendeland <sjur.brandeland@stericsson.com>
>
> Change-Id: I205c5b3baf1542e1593637ce896d8684870415be
> Signed-off-by: Sjur Braendeland <sjur.brandeland@stericsson.com>
> ---
> net/caif/Kconfig | 61 ++
> net/caif/Makefile | 56 ++
> net/caif/caif_chnlif.c | 219 +++++++
> net/caif/caif_chr.c | 374 ++++++++++++
> net/caif/caif_config_util.c | 167 ++++++
> net/caif/chnl_chr.c | 1393 +++++++++++++++++++++++++++++++++++++++++++
> net/caif/chnl_net.c | 492 +++++++++++++++
> 7 files changed, 2762 insertions(+), 0 deletions(-)
> create mode 100644 net/caif/Kconfig
> create mode 100644 net/caif/Makefile
> create mode 100644 net/caif/caif_chnlif.c
> create mode 100644 net/caif/caif_chr.c
> create mode 100644 net/caif/caif_config_util.c
> create mode 100644 net/caif/chnl_chr.c
> create mode 100644 net/caif/chnl_net.c
>
> diff --git a/net/caif/Kconfig b/net/caif/Kconfig
> new file mode 100644
> index 0000000..7fb9e9c
> --- /dev/null
> +++ b/net/caif/Kconfig
> @@ -0,0 +1,61 @@
> +#
> +# CAIF net configurations
> +#
> +
> +#menu "Caif Support"
> +comment "CAIF Support"
> +
> +menuconfig CAIF
> + tristate "Enable Caif support"
> + default n
> + ---help---
> + Say Y here if you need to use a phone modem that uses CAIF as transport
end above with period ('.').
> + You will also need to say yes to any caif physical devices that your platform
> + supports.
> + This can be either built-in or as a loadable module, if you select to build it as module
s/,/;/
> + the other CAIF also needs to built as modules
the other CAIF {options or drivers or some other word here} also need ... modules.
(end with period)
> + See Documentation/CAIF for a further explanation on how to use and configure.
> +
> +if CAIF
> +
> +config CAIF_CHARDEV
> + tristate "CAIF character device"
> + default CAIF
> + ---help---
> + Say Y if you will be using the CAIF AT type character devices.
> + This can be either built-in or as a loadable module,
> + If you select to build it as a built in then the main caif device must also be a builtin.
> + If unsure say Y.
> +
> +config CAIF_NETDEV
> + tristate "CAIF Network device"
> + default CAIF
> + ---help---
> + Say Y if you will be using the CAIF based network device.
> + This can be either built-in or as a loadable module,
> + If you select to build it as a built in then the main caif device must also be a builtin.
> + If unsure say Y.
> +
> +
> +config CAIF_USE_PLAIN
> + bool "Use plain buffers instead of SKB in caif"
> + default n
> + ---help---
> + Use plain buffer to transport data,
s/,/./
> + Select what type of internal buffering CAIF should use,
> + skb or plain.
> + If unsure say N hre.
> +
> +config CAIF_DEBUG
> + bool "Enable Debug"
> + default n
> + --- help ---
> + Enable the inclusion of debug code in the caif stack,
> + be aware that doing this will impact performance.
> + If unsure say N here.
> +
> +# Include physical drivers
> +# source "drivers/net/caif/Kconfig"
Drop the above line.
> +source "drivers/net/caif/Kconfig"
> +endif
> +#endmenu
---
~Randy
next prev parent reply other threads:[~2009-10-09 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 13:39 [PATCH] [CAIF-RFC 0/8-v2] CAIF Protocol Stack sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 1/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 2/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 3/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 4/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 5/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 6/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 7/8-v2] " sjur.brandeland
2009-10-09 13:39 ` [PATCH] [CAIF-RFC 8/8-v2] " sjur.brandeland
2009-10-12 13:43 ` [PATCH] [CAIF-RFC 7/8-v2] " Stefano Babic
2009-10-12 13:06 ` [PATCH] [CAIF-RFC 6/8-v2] " Stefano Babic
2009-10-09 16:43 ` Randy Dunlap [this message]
2009-10-12 12:51 ` [PATCH] [CAIF-RFC 5/8-v2] " Stefano Babic
2009-10-12 12:20 ` [PATCH] [CAIF-RFC 4/8-v2] " Stefano Babic
2009-10-12 9:28 ` [PATCH] [CAIF-RFC 2/8-v2] " Stefano Babic
2009-10-12 8:08 ` [PATCH] [CAIF-RFC 1/8-v2] " Stefano Babic
2009-10-12 8:20 ` David Miller
2009-10-12 9:41 ` [PATCH] [CAIF-RFC 0/8-v2] " David 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=20091009094306.4671ef33.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=christian.bejram@stericsson.com \
--cc=daniel.martensson@stericsson.com \
--cc=kim.xx.lilliestierna@stericsson.com \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.com \
--cc=stefano.babic@babic.homelinux.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).