linux-kernel - Re: [PATCH v3 1/3] tty: serial: msm: Add mask value for UART

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]

Date:	Tue, 28 Apr 2015 13:26:28 +0200
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Pramod Gurav <gpramod@...eaurora.org>
Cc:	linux-arm-msm@...r.kernel.org, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org, bryanh@...eaurora.org,
	sboyd@...eaurora.org, jslaby@...e.cz
Subject: Re: [PATCH v3 1/3] tty: serial: msm: Add mask value for UART_DM
 registers

On Fri, Apr 10, 2015 at 05:49:54PM +0530, Pramod Gurav wrote:
> The bit masks for RFR_LEVEL1 and STALE_TIMEOUT_MSB values in MR1 and
> IPR registers respectively are different for UART and UART_DM hardware
> cores. We have been using UART core mask values for these. Add the same
> for UART_DM core.
> 
> There is no bit setting as UART_IPR_RXSTALE_LAST for UART_DM core so do
> it only for UART core.
> 
> Signed-off-by: Pramod Gurav <gpramod@...eaurora.org>
> ---
> Changes since v2:
> 
>  - Changed the sequnce of code to avoid duplication of code.
> 
>  drivers/tty/serial/msm_serial.c | 26 ++++++++++++++++++++------
>  drivers/tty/serial/msm_serial.h |  2 ++
>  2 files changed, 22 insertions(+), 6 deletions(-)

I only have patch 1/3 in my inbox, please resend all of them, not just
individual ones you have redone, as that makes it impossible to keep
track of patches in series.

thanks,

greg k-h
--
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/