All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Zhizhikin <andrey.z@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: Allow to take irq bottom-half into irq_handler with additional dt-binding
Date: Thu, 7 Dec 2017 12:17:39 +0100	[thread overview]
Message-ID: <CAHtQpK6=5ThOvSygRLNU--5_yGLCyL1=a3mn4cn6eQv5DFjNGg@mail.gmail.com> (raw)
In-Reply-To: <20171207091611.GB12353@kroah.com>

On Thu, Dec 7, 2017 at 10:16 AM, Greg KH <gregkh@linuxfoundation.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.

  reply	other threads:[~2017-12-07 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 14:55 [PATCH] uio: Allow to take irq bottom-half into irq_handler with additional dt-binding Andrey Zhizhikin
2017-12-06 15:31 ` Greg KH
2017-12-06 16:59   ` Andrey Zhizhikin
2017-12-07  9:16     ` Greg KH
2017-12-07 11:17       ` Andrey Zhizhikin [this message]
2017-12-07 14:46 ` [PATCH v2 0/2] " Andrey Zhizhikin
2017-12-07 14:46   ` [PATCH v2 1/2] " Andrey Zhizhikin
2017-12-07 14:46     ` Andrey Zhizhikin
2017-12-07 14:46   ` [PATCH v2 2/2] uio: Introduce UIO driver dt-binding documentation Andrey Zhizhikin
2017-12-07 23:42     ` Rob Herring
2017-12-07 23:42       ` Rob Herring
2017-12-08 12:52       ` Andrey Zhizhikin
2017-12-08 12:52         ` Andrey Zhizhikin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHtQpK6=5ThOvSygRLNU--5_yGLCyL1=a3mn4cn6eQv5DFjNGg@mail.gmail.com' \
    --to=andrey.z@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.