linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "King, Lawrence" <lking@qti.qualcomm.com>
Cc: Andy Gross <andy.gross@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	"galak@codeaurora.org" <galak@codeaurora.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"ill.deacon@arm.com" <ill.deacon@arm.com>,
	"todor.tomov@linaro.org" <todor.tomov@linaro.org>,
	"srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
	"stanimir.varbanov@linaro.org" <stanimir.varbanov@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.
Subject: Re: SPI fix needed in kernel (DragonBoard 410c)
Date: Thu, 23 Feb 2017 09:41:25 -0800	[thread overview]
Message-ID: <20170223174125.be5ewn5o5tk2hwhk@sirena.org.uk> (raw)
In-Reply-To: <6857de0f674548d09ecad023211b3d1f@NASANEXM01D.na.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Wed, Feb 22, 2017 at 07:56:21PM +0000, King, Lawrence wrote:
> Argghh.. I am such a Newbie ;-) I originally sent this as “HTML” which of course was rejected by many of the recipients....
> 
> Resending as plain-text, with the formerly in-line oscilloscope screen shots attached as JPEG files.
> 
> Scope_4.jpg shows the problem with Chip Select, Scope_5.jpg shows the chip select with the fix.

I'm sorry but I can't really tell what this mail is about, it looks like
the end of a large, top posted thread with formatting issues so it's
pretty hard to read.  Can you please concisely describe the issue you'd
like to discuss?

Please don't top post, reply in line with needed context.  This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.

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 also check the list of people you're CCing, you've sent this to
a *very* large set of people.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2017-02-23 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 19:56 SPI fix needed in kernel (DragonBoard 410c) King, Lawrence
2017-02-22 21:08 ` Dan Sneddon
2017-02-23 17:41 ` 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=20170223174125.be5ewn5o5tk2hwhk@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=andy.gross@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ill.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lking@qti.qualcomm.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=stanimir.varbanov@linaro.org \
    --cc=todor.tomov@linaro.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).