linux-kernel - Re: [PATCH] uio: Allow to take irq bottom-half into irq

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: <CAHtQpK6=5ThOvSygRLNU--5_yGLCyL1=a3mn4cn6eQv5DFjNGg@mail.gmail.com>
Date:   Thu, 7 Dec 2017 12:17:39 +0100
From:   Andrey Zhizhikin <andrey.z@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] uio: Allow to take irq bottom-half into irq_handler with
 additional dt-binding

On Thu, Dec 7, 2017 at 10:16 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top

Understood, rules are golden! :)

>
> The uio-phys driver does use DT bindings, so perhaps look at how those
> are defined.

UIO in general uses standard bindings (like "compatible", "reg",
"interrupt"), but the documentation part is completely missing. What I
was able to find in Kernel tree is a HOW-TO from Hans-Juergen Koch
dated 2006 and kobject reference on Embedding kobjects with UIO as an
example. I've created a new binding document under
Documentation/devicetree/bindings/uio/ and would submit it together
with updated patch in series.

If anyone happen to know which place I missed in the Kernel to look at
for uio dt-binding Documentation part - please point me out.

>
> Ok, that all seems like a good thing to have the ability to do here, you
> should mention it in the changelog text when you redo this patch.

Would be done!

I am planning to have all above corrected and re-submit the patch as
series with Documentation part included.

Cheers,
Andrey.