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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEB7QLBpf2HupqOR9xe2S6cZLk1vnxv7Oqvq4NdRQNaCKjfrNQ@mail.gmail.com>
Date:	Thu, 6 Sep 2012 23:46:30 +0200
From:	Tomas Hlavacek <tmshlvck@...il.com>
To:	gregkh@...uxfoundation.org, alan@...ux.intel.com,
	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	marek.vasut@...il.com, Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH] tty_register_device_attr updated for tty-next

Hello!

On Thu, Sep 6, 2012 at 11:17 PM, Tomas Hlavacek <tmshlvck@...il.com> wrote:
> Added tty_device_create_release() and bound to dev->release in
> tty_register_device_attr().
> Added tty_port_register_device_attr() and used in uart_add_one_port()
> instead of tty_register_device_attr().
>
> Signed-off-by: Tomas Hlavacek <tmshlvck@...il.com>
> ---
>  drivers/tty/serial/serial_core.c |    8 ++++----
>  drivers/tty/tty_io.c             |    7 +++++++
>  drivers/tty/tty_port.c           |   24 ++++++++++++++++++++++++
>  include/linux/tty.h              |    4 ++++
>  4 files changed, 39 insertions(+), 4 deletions(-)
>

A little bit more explanation regarding this patch: It fixes two
problems with my previous patch (tty: uartclk value from serial_core
exposed to sysfs) which Jiri has pointed out earlier today. Both are
related to the changed interface in the tty-next branch and both
should have been dealt with in the first patch. It also fixes minor
problems (one const keyword added and newlines rearranged in the
uart_get_attr_uartclk() function).

Tomas
--
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