From: Mark Brown <broonie@kernel.org>
To: "Franklin S Cooper Jr." <fcooper@ti.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-spi@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>,
ssantosh@kernel.org, "Ivan T. Ivanov" <iivanov@mm-sol.com>,
m-karicheri2@ti.com, "Ivan T. Ivanov" <iivanov.xz@gmail.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
hkallweit1@gmail.com
Subject: Re: [PATCH v2] spi: Setup the master controller driver before setting the chipselect
Date: Wed, 28 Oct 2015 09:33:23 +0900 [thread overview]
Message-ID: <20151028003323.GV28319@sirena.org.uk> (raw)
In-Reply-To: <562F6C9B.6010607@ti.com>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
On Tue, Oct 27, 2015 at 07:22:51AM -0500, Franklin S Cooper Jr. wrote:
> I don't see that you pulled this patch into your topic/core branch just yet. Would you prefer
> for me to shoot a v3 with Andy's tested by or will you just add it when your ready to
> pull it in?
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
Please don't send content free pings. If your patch has been lost then
you will need to resend it, if your patch is waiting to be handled then
at best your message is likely to be threaded in with the original
thread and therefore not seen. Either way a content free ping just adds
to mail volume rather than helping.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-10-28 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 15:29 Franklin S Cooper Jr
2015-10-16 15:45 ` Andy Shevchenko
2015-10-16 15:47 ` Franklin S Cooper Jr.
2015-10-16 15:55 ` Andy Shevchenko
2015-10-27 12:22 ` Franklin S Cooper Jr.
2015-10-27 13:11 ` Grygorii Strashko
2015-10-27 13:34 ` Grygorii Strashko
2015-10-28 0:33 ` Mark Brown [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=20151028003323.GV28319@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=fcooper@ti.com \
--cc=hkallweit1@gmail.com \
--cc=iivanov.xz@gmail.com \
--cc=iivanov@mm-sol.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nsekhar@ti.com \
--cc=ssantosh@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
all inboxes | Powered by JetHome®