From: Tony Lindgren <tony@atomide.com>
To: Greg Knight <g.knight@symetrica.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Patch to parameterize DMA_MIN_BYTES for omap2-mcspi
Date: Wed, 18 Mar 2015 15:01:59 -0700 [thread overview]
Message-ID: <20150318220158.GZ31346@atomide.com> (raw)
In-Reply-To: <CAAQQ3umQu=Zh6MC=uXTxzbXGgm48KY6KQTPo4=f=0cVy+FFv-Q@mail.gmail.com>
* Greg Knight <g.knight@symetrica.com> [150318 15:02]:
> Will do, Tony. Thanks for helping out. First time submitting kernel patches
> so I'm still figuring things out.
No problem :)
> I'm not actually certain of the full reach of the acronym "omap" (or,
> frankly, anything about it except that it shows up everywhere with TI's
> footprints). But the patches I'm submitting apply to McASP and McSPI
> subcomponents of the AM335X CPU, which is TI, so... I assume it's omap?
Yes from the kernel point of view if it uses code in arch/arm/*omap*/
it's an omap. And am335x is booting with code in arch/arm/mach-omap2.
Regards,
Tony
next prev parent reply other threads:[~2015-03-18 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:37 Patch to parameterize DMA_MIN_BYTES for omap2-mcspi Greg Knight
2015-03-18 20:31 ` Tony Lindgren
[not found] ` <CAAQQ3umQu=Zh6MC=uXTxzbXGgm48KY6KQTPo4=f=0cVy+FFv-Q@mail.gmail.com>
2015-03-18 22:01 ` Tony Lindgren [this message]
2015-03-18 22:04 ` Greg Knight
-- strict thread matches above, loose matches on Subject: below --
2015-03-19 5:05 Greg Knight
2015-03-19 9:47 ` Mark Brown
2015-03-19 12:34 ` Peter Ujfalusi
2015-03-19 13:16 ` Greg Knight
[not found] ` <CAAQQ3un3k-0nY8xaOXKbmCznOk69ZEhbWLd5ZZV1_=rQLOyspg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-19 14:03 ` Mark Brown
2015-03-19 16:23 ` Peter Ujfalusi
[not found] ` <550AF7F6.7080200-l0cyMroinI0@public.gmane.org>
2015-03-19 17:28 ` Greg Knight
2015-03-19 18:51 ` Mark Brown
2015-03-20 13:10 ` Peter Ujfalusi
[not found] ` <550C1C2C.5080204-l0cyMroinI0@public.gmane.org>
2015-03-22 16:31 ` Mark Brown
2015-03-20 12:58 ` Peter Ujfalusi
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=20150318220158.GZ31346@atomide.com \
--to=tony@atomide.com \
--cc=g.knight@symetrica.com \
--cc=linux-omap@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 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).