linux-kernel - Re: [PATCH 0/4] switch arc-uart to devicetree based probing

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: <20130116061636.GA5680@kroah.com>
Date:	Tue, 15 Jan 2013 22:16:36 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] switch arc-uart to devicetree based probing

On Fri, Jan 11, 2013 at 11:50:19AM +0530, Vineet Gupta wrote:
> Hi,
> 
> As part of converting ARC Port to devicetree infrastructure, the following
> series converts the arc-uart driver to DT.
> 
> * The first patch is a bug-fix which showed up in the process as DT based
>   platform devices by default have -ve id
> * Next two prepare the driver for forthcoming DT changes.
> * Last one contains the DT bindings and driver using those.
> 
> Couple of points worth mentioning:
> * The earlyprintk portion of driver still relies on static platform data
>   we would need some earlyprintk handling in of_fdt_* to clean it up properly
> * Two of the three platform data instances are now retrieved from DT.
>   However one still needs to be dynamically passed by platform (using
>   of_dev_auxdata) as we want to run same image in simulator and hardware
> 
> Tested on in-works ARC 3.8 port.
> 
> P.S. Greg, can this be treated as a bug-fix for 3.8

No, because it is not a bugfix, but a new feature, sorry.

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/