netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
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: [RFC PATCH v3 0/8] CAIF Protocol Stack
Date: Mon, 30 Nov 2009 17:08:44 +0100	[thread overview]
Message-ID: <4B13EE0C.7080000@trash.net> (raw)
In-Reply-To: <1259593252-2493-1-git-send-email-sjur.brandeland@stericsson.com>

sjur.brandeland@stericsson.com wrote:
> Change Log:
> 
> General:
> * Sockets has replaced the character device implementation,
>   when accessing the modem. AT channels has to open sockets.
> * CAIF Link layer is now implemented as net-devices.
> * Cleanup of asserts no using caif_assert everywhere.
> * Style cleanups, spacing, typedefs etc.
> 
> Documentation/CAIF
> * Removed tool chardevconfig for configuration.
>   Instead  CAIF NET device can be configured with RTNL or socket IOCTL.
> * Removed replaced user space tool ldiscd to configure TTY.
>   TTY is now opened from kernel when loading caif_serial.ko
> * Added caif socket MAN page to Documentation (Will be moved later on).
> * Added example on CAIF NET device configuration.
> * Removed reference to  Doc No: 155 19-CRH 109 913.
> 
> include/linux
> * Added caif_socket.h defining CAIF Socket interface.
> * Added if_caif.h define CAIF IP Net Device configuration
> 
> include/net
> * Added caif_dev.h defining interface between driver and caif-core.
> 
> include/net/generic
> * Updated assert statement
> * Removed typedefs
> 
> net/caif
> * Added socket implementation and removed character device.
> * General removed typedefs and fixed CHECKPATCH warnings
> * Minor change on error handling in cfcnfg.c
> * chnl_net.c Added RTNL support and IOCTL
> * Fixed typos in Kconfig

Please add the changelog to the respective patches and give them
meaningful subjects. Its impossible to review patches if you
don't even know what they're supposed to do.

  parent reply	other threads:[~2009-11-30 16:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 15:00 [RFC PATCH v3 0/8] CAIF Protocol Stack sjur.brandeland
2009-11-30 15:00 ` [RFC PATCH v3 1/8] " sjur.brandeland
2009-11-30 15:00   ` [RFC PATCH v3 2/8] " sjur.brandeland
2009-11-30 15:00     ` [RFC PATCH v3 3/8] " sjur.brandeland
2009-11-30 15:00       ` [RFC PATCH v3 4/8] " sjur.brandeland
2009-11-30 15:00         ` [RFC PATCH v3 5/8] " sjur.brandeland
2009-11-30 15:00           ` [RFC PATCH v3 6/8] " sjur.brandeland
2009-11-30 15:00             ` [RFC PATCH v3 7/8] " sjur.brandeland
2009-11-30 15:00               ` [RFC PATCH v3 8/8] " sjur.brandeland
2009-12-15 17:12               ` [RFC PATCH v3 7/8] " stefano babic
2009-11-30 16:41           ` [RFC PATCH v3 5/8] " Randy Dunlap
2009-12-10 13:05             ` Sjur Brændeland
2009-12-10 16:44               ` Randy Dunlap
2009-12-15 16:47         ` [RFC PATCH v3 4/8] " stefano babic
2009-12-16 16:16           ` Sjur Brændeland
2009-12-15 16:00       ` [RFC PATCH v3 3/8] " stefano babic
2009-12-16 16:15         ` Sjur Brændeland
2009-12-09  0:18     ` [RFC PATCH v3 2/8] " stefano babic
2009-12-10 11:20       ` Sjur Brændeland
2009-12-08 23:42   ` [RFC PATCH v3 1/8] " stefano babic
2009-12-10 11:11     ` Sjur Brændeland
2009-11-30 16:08 ` Patrick McHardy [this message]
2009-11-30 18:26   ` [RFC PATCH v3 0/8] " Sjur Brændeland
2009-12-02 17:02 ` Stefano Babic
2009-12-03 17:49   ` Sjur Brændeland

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=4B13EE0C.7080000@trash.net \
    --to=kaber@trash.net \
    --cc=christian.bejram@stericsson.com \
    --cc=daniel.martensson@stericsson.com \
    --cc=kim.xx.lilliestierna@stericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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).