From: David Brownell <david-b@pacbell.net>
To: kmpark@infradead.org
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: OMAP2 McSPI code cleanup
Date: Fri, 17 Aug 2007 08:51:40 -0700 [thread overview]
Message-ID: <200708170851.41052.david-b@pacbell.net> (raw)
In-Reply-To: <003901c7e0a3$08dc39d0$e1ac580a@swcenter.sec.samsung.co.kr>
On Friday 17 August 2007, you wrote:
> ARM: OMAP: OMAP2 McSPI code cleanup
SPI patches don't merge via the ARM or OMAP patch streams...
If you just send them for the OMAP tree they won't necessarily
go upstream unless the SPI maintainer happens to notice them.
> Remove unused variable & write space
>
> ...
next prev parent reply other threads:[~2007-08-17 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 7:48 [PATCH] ARM: OMAP: OMAP2 McSPI code cleanup Kyungmin Park
2007-08-17 15:51 ` David Brownell [this message]
2007-08-22 7:10 ` Tony Lindgren
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=200708170851.41052.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=kmpark@infradead.org \
--cc=linux-omap-open-source@linux.omap.com \
/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