mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Insop Song <insop.song@gainspeed.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jane Wan <Jane.Wan@gainspeed.com>, <grant.likely@secretlab.ca>,
	<rob.herring@calxeda.com>, <Emilian.Medve@Freescale.com>,
	<kenth.eriksson@transmode.com>,
	<thomas.de.schampheleire@gmail.com>, <b48286@Freescale.com>,
	<jg1.han@samsung.com>, <sr@denx.de>,
	<spi-devel-general@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] Configure FSL eSPI CSBEF, CSAFT, and whether to send all received data to user
Date: Mon, 14 Apr 2014 14:38:53 -0700	[thread overview]
Message-ID: <20140414213853.GF14129@neon.local.cohere.net> (raw)
In-Reply-To: <20140414205151.GH25182@sirena.org.uk>

On Mon, Apr 14, 2014 at 09:51:51PM +0100, Mark Brown wrote:
> On Sat, Apr 12, 2014 at 11:48:35AM -0700, Jane Wan wrote:
> > Make FSL eSPI properties configurable through device tree.  The
> > configurable parameters include CSnBEF and CSnAFT in ESPI_SPMODEn
> > registers (n=0,1,2,3), and whether to send all received data to user.
> 
> Don't send cover letters for individual patches, include anything that's
> needed in the patch changelog or after the ---.
> 
> > Test done:
> > - Kernel version 3.8.13
> 
> We're developing v3.15 now, you need to submit against current code.
> 

We will generate a new patch.

> Please also be sure to CC the mailing list on patches, the sourceforge
> list has been unused for quite some time now.

We use scripts/get_maintainer.pl to get the mailing addresses.
We will double check the mailing list from MAINTAINER file.

Regards,

Insop


  reply	other threads:[~2014-04-14 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12 18:48 Jane Wan
2014-04-12 18:48 ` Jane Wan
2014-04-14 20:55   ` Mark Brown
2014-04-16 16:39     ` Jane Wan
2014-04-16 17:28       ` Mark Brown
2014-04-14 20:51 ` Mark Brown
2014-04-14 21:38   ` Insop Song [this message]
2014-04-14 23:49     ` Mark Brown
2014-04-14 23:59       ` Insop Song
2014-04-15  0:00       ` Insop Song
2014-04-15 12:11         ` Mark Brown

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=20140414213853.GF14129@neon.local.cohere.net \
    --to=insop.song@gainspeed.com \
    --cc=Emilian.Medve@Freescale.com \
    --cc=Jane.Wan@gainspeed.com \
    --cc=b48286@Freescale.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jg1.han@samsung.com \
    --cc=kenth.eriksson@transmode.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=sr@denx.de \
    --cc=thomas.de.schampheleire@gmail.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
all inboxes | Powered by JetHome®