lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTinyQ6kdCMG=gj1vXQifUNRA1Ewokg@mail.gmail.com>
Date:	Thu, 14 Apr 2011 17:54:40 +0530
From:	Pavan Savoy <pavan_savoy@...y.com>
To:	greg@...ah.com, linux-kernel@...r.kernel.org
Cc:	pavan_savoy@...y.com, Pavan Savoy <pavan_savoy@...com>
Subject: Re: [PATCH 0/3] shared transport robustness fixes

On Fri, Apr 8, 2011 at 3:27 PM,  <pavan_savoy@...com> wrote:
> From: Pavan Savoy <pavan_savoy@...com>
>
> Texas Instruments' WiLink connectivity chipset's Bluetooth, FM and GPS
> wireless technologies are interfaced over single UART, which is enabled
> by the TI-ST line discipline driver.
>
> The following patches are updates and few fixes found during robustness testing
> of the driver.
> 1. The patch handles the delayed tty receive_buf function called by the TTY layer.
> 2. Removes the dependency on rfkill for build from Kconfig
> 3. Fix for the skipping the change remote baud rate command.

Greg,

Please review and queue up for merge, if its alright..

Thanks,
Pavan


> Pavan Savoy (2):
>  drivers:misc:ti-st: handle delayed tty receive
>  drivers:misc:ti-st: remove rfkill dependency
>
> Victor Goldenshtein (1):
>  drivers:misc:ti-st: fix skip remote baud logic
>
>  drivers/misc/ti-st/Kconfig   |    1 -
>  drivers/misc/ti-st/st_core.c |   23 +++++++++++++----------
>  drivers/misc/ti-st/st_kim.c  |    6 ++++--
>  include/linux/ti_wilink_st.h |    3 ++-
>  4 files changed, 19 insertions(+), 14 deletions(-)
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ