From: Greg KH <greg@kroah.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Tony Lindgren <tony@atomide.com>,
stable@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: am335x-sl50: Fix cannot claim requested pins for spi0
Date: Sat, 20 May 2017 10:45:31 +0200 [thread overview]
Message-ID: <20170520084531.GB4284@kroah.com> (raw)
In-Reply-To: <20170519165144.11508-2-enric.balletbo@collabora.com>
On Fri, May 19, 2017 at 06:51:44PM +0200, Enric Balletbo i Serra wrote:
> We don't need to bitbang these pins anymore, instead we muxed these
> pins as SPI, after this change, done in commit 6c69f726, we introduced
> the following error:
>
> pinctrl-single 44e10800.pinmux: pin PIN85 already requested \
> by 44e10800.pinmux; cannot claim for 48030000.spi
> pinctrl-single 44e10800.pinmux: pin-85 (48030000.spi) status -22
>
> Fixes: 6c69f726 ("ARM: dts: am335x-sl50: Enable SPI0 interface and Flash Memory")
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> arch/arm/boot/dts/am335x-sl50.dts | 4 ----
> 1 file changed, 4 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: am335x-sl50: Fix cannot claim requested pins for spi0
Date: Sat, 20 May 2017 10:45:31 +0200 [thread overview]
Message-ID: <20170520084531.GB4284@kroah.com> (raw)
In-Reply-To: <20170519165144.11508-2-enric.balletbo@collabora.com>
On Fri, May 19, 2017 at 06:51:44PM +0200, Enric Balletbo i Serra wrote:
> We don't need to bitbang these pins anymore, instead we muxed these
> pins as SPI, after this change, done in commit 6c69f726, we introduced
> the following error:
>
> pinctrl-single 44e10800.pinmux: pin PIN85 already requested \
> by 44e10800.pinmux; cannot claim for 48030000.spi
> pinctrl-single 44e10800.pinmux: pin-85 (48030000.spi) status -22
>
> Fixes: 6c69f726 ("ARM: dts: am335x-sl50: Enable SPI0 interface and Flash Memory")
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> arch/arm/boot/dts/am335x-sl50.dts | 4 ----
> 1 file changed, 4 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2017-05-20 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 16:51 [PATCH 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1 Enric Balletbo i Serra
2017-05-19 16:51 ` Enric Balletbo i Serra
2017-05-19 16:51 ` [PATCH 2/2] ARM: dts: am335x-sl50: Fix cannot claim requested pins for spi0 Enric Balletbo i Serra
2017-05-19 16:51 ` Enric Balletbo i Serra
2017-05-20 8:45 ` Greg KH [this message]
2017-05-20 8:45 ` Greg KH
2017-05-20 8:45 ` [PATCH 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1 Greg KH
2017-05-20 8:45 ` Greg KH
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=20170520084531.GB4284@kroah.com \
--to=greg@kroah.com \
--cc=enric.balletbo@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.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 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.