devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam J Allison <adamj.allison-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
Cc: Frank Rowand
	<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Straight up new person
Date: Tue, 24 May 2016 16:08:54 -0500	[thread overview]
Message-ID: <CANF=RFSo+SAq514xtywGmLg0_+2CXGbNB4dQMw2OPeZ--n8ezg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1605241638360.11009@Device-040570>

Robert,
I'll _safely_ assume you'll do the patching...

Frank,
thank you for pointing me in the right direction.

Have a good day,
-Adam


On Tue, May 24, 2016 at 3:40 PM, Robert P. J. Day <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org> wrote:
> On Tue, 24 May 2016, Frank Rowand wrote:
>
>> On 5/23/2016 3:40 PM, Adam J Allison wrote:
>> > I'm a noob to this, and I've just got a simple typo.
>> > I don't want to bother you, but I can't find out who to email to get it fixed.
>> > I've read the documentation a few times, but still couldn't figure it out.
>> >
>> >
>> > tl dr
>> > am33xx.dtsi: line 190 emda3_mperr should probably be edma3_mperr
>> >
>> >
>> > Thank you for your understanding,
>> > Adam
>>
>> The documentation can be a little hard to navigate.
>>
>> Does this file help?
>>
>>    Documentation/devicetree/bindings/submitting-patches.txt
>>
>> If not, let me know and I'll try to make the documentation
>> better.
>
>   also, when you spot a typo like that, ***immediately*** assume there
> are more of them:
>
> $ grep emda *
> am33xx.dtsi:                    interrupt-names = "edma3_ccint", "emda3_mperr",
> am4372.dtsi:                    interrupt-names = "edma3_ccint", "emda3_mperr",
> dm814x.dtsi:                    interrupt-names = "edma3_ccint", "emda3_mperr",
> dra7.dtsi:                      interrupt-names = "edma3_ccint", "emda3_mperr",
> $
>
> because there always are.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-05-24 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 22:40 Straight up new person Adam J Allison
     [not found] ` <CANF=RFTPy+V2qzFiihEYNxRhn52uoL=RXZBAcGXcRi72DniLbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-24 20:15   ` Frank Rowand
     [not found]     ` <5744B67E.6040209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-24 20:40       ` Robert P. J. Day
2016-05-24 21:08         ` Adam J Allison [this message]

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='CANF=RFSo+SAq514xtywGmLg0_+2CXGbNB4dQMw2OPeZ--n8ezg@mail.gmail.com' \
    --to=adamj.allison-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=rpjday-L09J2beyid0N/H6P543EQg@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).