From: David Miller <davem@davemloft.net>
To: sjur.brandeland@stericsson.com
Cc: sjurbr@gmail.com, netdev@vger.kernel.org, linus.walleij@stericsson.com
Subject: Re: [PATCH net-next-2.6 4/4] caif: Add debug connection type for CAIF.
Date: Sun, 20 Jun 2010 20:39:08 -0700 (PDT) [thread overview]
Message-ID: <20100620.203908.35022785.davem@davemloft.net> (raw)
In-Reply-To: <1276793741-20278-4-git-send-email-sjur.brandeland@stericsson.com>
From: sjur.brandeland@stericsson.com
Date: Thu, 17 Jun 2010 18:55:41 +0200
> From: Sjur Braendeland <sjur.brandeland@stericsson.com>
>
> Added new CAIF protocol type CAIFPROTO_DEBUG for accessing
> CAIF debug on the ST Ericsson modems.
>
> There are two debug servers on the modem, one for radio related
> debug (CAIF_RADIO_DEBUG_SERVICE) and the other for
> communication/application related debug (CAIF_COM_DEBUG_SERVICE).
>
> The debug connection can contain trace debug printouts or
> interactive debug used for debugging and test.
>
> Debug connections can be of type STREAM or SEQPACKET.
>
> Signed-off-by: Sjur Braendeland <sjur.brandeland@stericsson.com>
Applied.
next prev parent reply other threads:[~2010-06-21 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 16:55 [PATCH net-next-2.6 1/4] caif: Bugfix not all services uses flow-ctrl sjur.brandeland
2010-06-17 16:55 ` [PATCH net-next-2.6 2/4] caif: Bugfix - RFM must support segmentation sjur.brandeland
2010-06-17 16:55 ` [PATCH net-next-2.6 3/4] caif: Use link layer MTU instead of fixed MTU sjur.brandeland
2010-06-17 16:55 ` [PATCH net-next-2.6 4/4] caif: Add debug connection type for CAIF sjur.brandeland
2010-06-21 3:39 ` David Miller [this message]
2010-06-21 3:39 ` [PATCH net-next-2.6 3/4] caif: Use link layer MTU instead of fixed MTU David Miller
2010-06-21 3:38 ` [PATCH net-next-2.6 2/4] caif: Bugfix - RFM must support segmentation David Miller
2010-06-21 3:38 ` [PATCH net-next-2.6 1/4] caif: Bugfix not all services uses flow-ctrl 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=20100620.203908.35022785.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linus.walleij@stericsson.com \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.com \
--cc=sjurbr@gmail.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).