From: "Gorby, Russ" <russ.gorby@intel.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
"open list:SPI SUBSYSTEM"
<spi-devel-general@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011
Date: Mon, 14 Feb 2011 09:22:49 -0800 [thread overview]
Message-ID: <4C5E6457CD7911469A07260381288C28D37127C9@orsmsx502.amr.corp.intel.com> (raw)
In-Reply-To: <20110212091913.GD17755@angua.secretlab.ca>
OK got it. Thanks.
>-----Original Message-----
>From: Grant Likely [mailto:glikely@secretlab.ca] On Behalf Of Grant
>Likely
>Sent: Saturday, February 12, 2011 1:19 AM
>To: Gorby, Russ
>Cc: David Brownell; open list:SPI SUBSYSTEM; open list
>Subject: Re: [PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011
>
>On Wed, Feb 02, 2011 at 01:01:51PM -0800, Russ Gorby wrote:
>> Hello SPI maintainers,
>> I am sending a patch for the (new) intel_mid_ssp_spi driver for
>> consideration for inclusion in the Linux Kernel. This is a SPI master
>> controller driver that is being used for the intel MID platform
>(Medfield).
>> It uses the on-board Bulverde SSP controller configured for SPI
>(spibus #3)
>> running at 25Mhz.
>
>Hi Russ,
>
>Just for future reference, when you're only sending one patch, please
>put your notes into the patch description itself, or immediately after
>the --- line. No need for a cover letter like this one.
>
>Thanks,
>g.
next prev parent reply other threads:[~2011-02-14 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1296680512-2758-1-git-send-email-russ.gorby@intel.com>
2011-02-12 9:19 ` [PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011 Grant Likely
2011-02-14 17:22 ` Gorby, Russ [this message]
[not found] <[PATCH 0/1] Adding intel_mid_ssp_spi driver : 01/27/2011>
2011-02-02 21:01 ` Russ Gorby
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=4C5E6457CD7911469A07260381288C28D37127C9@orsmsx502.amr.corp.intel.com \
--to=russ.gorby@intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).