public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavan Savoy <pavan_savoy@ti.com>
To: "Savoy, Pavan" <pavan_savoy@ti.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"pavan_savoy@sify.com" <pavan_savoy@sify.com>
Subject: Re: [PATCH 0/4] drivers:misc: ti-st: platform specifics
Date: Fri, 15 Jul 2011 11:50:10 -0500	[thread overview]
Message-ID: <4E206FC2.9090804@ti.com> (raw)
In-Reply-To: <1310486113-29081-1-git-send-email-pavan_savoy@ti.com>

On 7/12/2011 10:55 AM, Savoy, Pavan wrote:
> Greg,
>
> resending,
> since I didn't see these up on lkml.org
>
> These are the some of the patches which have gone on top of Texas Instrument's
> shared transport driver which fixes issues found during field testing.
> These include:
> a. removing an annoying and misleading debug message
> b. various platform hooks for enabling/disabling chip and communicating PM
> states of the WiLink chip.
> c. Re-initializing completion for make sure failed firmware download doesn't
> create a problem the next time around.
> d. fail-safe fix which happens upon corner cases when UART drops
> bytes or chip is too busy and hence sends across h/w error events.

Greg,

I hope you find some time to have a look at these.

Thanks & Regards,
Pavan Savoy.

>
>
> Pavan Savoy (3):
>    drivers:misc: ti-st: avoid a misleading dbg msg
>    drivers:misc:ti-st: platform hooks for chip states
>    drivers:misc: ti-st: reinit completion on ver read
>
> Vijay Badawadagi (1):
>    drivers:misc: ti-st: fail-safe on wrong pkt type
>
>   drivers/misc/ti-st/st_core.c |    9 ++++++++-
>   drivers/misc/ti-st/st_kim.c  |   13 +++++++++++++
>   drivers/misc/ti-st/st_ll.c   |   19 +++++++++++++++++++
>   include/linux/ti_wilink_st.h |   27 ++++++++++++++++++++++++++-
>   4 files changed, 66 insertions(+), 2 deletions(-)
>


       reply	other threads:[~2011-07-15 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1310486113-29081-1-git-send-email-pavan_savoy@ti.com>
2011-07-15 16:50 ` Pavan Savoy [this message]
2011-07-20 14:30 [PATCH 0/4] drivers:misc: ti-st: platform specifics pavan_savoy
2011-07-20 14:30 ` [PATCH 1/4] drivers:misc: ti-st: avoid a misleading dbg msg pavan_savoy
2011-07-20 14:30   ` [PATCH 2/4] drivers:misc:ti-st: platform hooks for chip states pavan_savoy
2011-07-20 14:30     ` [PATCH 3/4] drivers:misc: ti-st: reinit completion on ver read pavan_savoy
2011-07-20 14:30       ` [PATCH 4/4] drivers:misc: ti-st: fail-safe on wrong pkt type pavan_savoy
2011-07-20 14:30         ` [PATCH 0/4] drivers:misc: ti-st: platform specifics pavan_savoy

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=4E206FC2.9090804@ti.com \
    --to=pavan_savoy@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavan_savoy@sify.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