From: Tony Lindgren <tony@atomide.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1
Date: Fri, 26 May 2017 08:30:46 -0700 [thread overview]
Message-ID: <20170526153045.GA3717@atomide.com> (raw)
In-Reply-To: <20170522090153.5596-1-enric.balletbo@collabora.com>
* Enric Balletbo i Serra <enric.balletbo@collabora.com> [170522 02:05]:
> The second version of the hardware moved the card detect pin from gpio0_6
> to gpio1_9, as we won't support the first hardware version fix the pinmux
> configuration of this pin.
OK so proto vs production version misconfiguration, applying both into
omap-for-v4.12/fixes-v2 thanks. Note that you're not supposed to send
any email to the stable list unless requesting a backport of something.
The idea is to add the stable tag when committing, and nowadays it seems
having a proper "Fixes" tag seems to do the job automatically.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1
Date: Fri, 26 May 2017 08:30:46 -0700 [thread overview]
Message-ID: <20170526153045.GA3717@atomide.com> (raw)
In-Reply-To: <20170522090153.5596-1-enric.balletbo@collabora.com>
* Enric Balletbo i Serra <enric.balletbo@collabora.com> [170522 02:05]:
> The second version of the hardware moved the card detect pin from gpio0_6
> to gpio1_9, as we won't support the first hardware version fix the pinmux
> configuration of this pin.
OK so proto vs production version misconfiguration, applying both into
omap-for-v4.12/fixes-v2 thanks. Note that you're not supposed to send
any email to the stable list unless requesting a backport of something.
The idea is to add the stable tag when committing, and nowadays it seems
having a proper "Fixes" tag seems to do the job automatically.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1
Date: Fri, 26 May 2017 08:30:46 -0700 [thread overview]
Message-ID: <20170526153045.GA3717@atomide.com> (raw)
In-Reply-To: <20170522090153.5596-1-enric.balletbo@collabora.com>
* Enric Balletbo i Serra <enric.balletbo@collabora.com> [170522 02:05]:
> The second version of the hardware moved the card detect pin from gpio0_6
> to gpio1_9, as we won't support the first hardware version fix the pinmux
> configuration of this pin.
OK so proto vs production version misconfiguration, applying both into
omap-for-v4.12/fixes-v2 thanks. Note that you're not supposed to send
any email to the stable list unless requesting a backport of something.
The idea is to add the stable tag when committing, and nowadays it seems
having a proper "Fixes" tag seems to do the job automatically.
Regards,
Tony
next prev parent reply other threads:[~2017-05-26 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:01 [PATCH v2 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1 Enric Balletbo i Serra
2017-05-22 9:01 ` Enric Balletbo i Serra
2017-05-22 9:01 ` [PATCH v2 2/2] ARM: dts: am335x-sl50: Fix cannot claim requested pins for spi0 Enric Balletbo i Serra
2017-05-22 9:01 ` Enric Balletbo i Serra
2017-05-26 15:30 ` Tony Lindgren [this message]
2017-05-26 15:30 ` [PATCH v2 1/2] ARM: dts: am335x-sl50: Fix card detect pin for mmc1 Tony Lindgren
2017-05-26 15:30 ` Tony Lindgren
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=20170526153045.GA3717@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.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 \
/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.