All of lore.kernel.org
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: amd: seattle: Use "spi" as name for SPI controllers
Date: Mon, 24 Sep 2018 15:26:05 +0200	[thread overview]
Message-ID: <20180924132605.GB23547@ulmo> (raw)
In-Reply-To: <b0721afb-ff52-f348-a481-bc4e8ee0f4a7@amd.com>

On Mon, Sep 24, 2018 at 01:09:16PM +0000, Lendacky, Thomas wrote:
> On 09/24/2018 04:46 AM, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Recent versions of DTC contain additional checks for SPI busses and warn
> > about certain common mistakes, such as when an SPI controller has a name
> > other than "spi".
> > 
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> 
> Looks like the same patch was already submitted:
> 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-September/601706.html

Indeed. I had done a quick search and not seen these submitted in recent
days and since the DTC change that causes these had only landed in -next
on Friday I had assumed that they must not have been fixed yet.

I wouldn't have thought that Rob had preemptively sent out the fixes.
But it being Rob, maybe I should have. =)

Sorry for the noise,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180924/1ef69125/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Singh, Brijesh" <brijesh.singh@amd.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
Subject: Re: [PATCH] arm64: amd: seattle: Use "spi" as name for SPI controllers
Date: Mon, 24 Sep 2018 15:26:05 +0200	[thread overview]
Message-ID: <20180924132605.GB23547@ulmo> (raw)
In-Reply-To: <b0721afb-ff52-f348-a481-bc4e8ee0f4a7@amd.com>


[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

On Mon, Sep 24, 2018 at 01:09:16PM +0000, Lendacky, Thomas wrote:
> On 09/24/2018 04:46 AM, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Recent versions of DTC contain additional checks for SPI busses and warn
> > about certain common mistakes, such as when an SPI controller has a name
> > other than "spi".
> > 
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> 
> Looks like the same patch was already submitted:
> 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-September/601706.html

Indeed. I had done a quick search and not seen these submitted in recent
days and since the DTC change that causes these had only landed in -next
on Friday I had assumed that they must not have been fixed yet.

I wouldn't have thought that Rob had preemptively sent out the fixes.
But it being Rob, maybe I should have. =)

Sorry for the noise,
Thierry

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-09-24 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  9:46 [PATCH] arm64: amd: seattle: Use "spi" as name for SPI controllers Thierry Reding
2018-09-24  9:46 ` Thierry Reding
2018-09-24 13:09 ` Lendacky, Thomas
2018-09-24 13:09   ` Lendacky, Thomas
2018-09-24 13:26   ` Thierry Reding [this message]
2018-09-24 13:26     ` Thierry Reding

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=20180924132605.GB23547@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.