From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mmc: core: Improve marking broken HPI through devicetree
Date: Tue, 19 Apr 2016 16:23:40 +0300 [thread overview]
Message-ID: <5716315C.7070001@cogentembedded.com> (raw)
In-Reply-To: <571622B7.2010202@schinagl.nl>
On 4/19/2016 3:21 PM, Olliver Schinagl wrote:
>>> In patch 81f8a7be66 Hans de Goede added a patch to allow marking an mmc
>>
>> scripts/checkpatch.pl now enforces certain commit citing style, the
>> commit summary should be specified too.
> I used checkpatch from 4.6.0-rc2(or3) and did not notice it. But I'll add it
> to v2.
Maybe it just didn't recognize your commit citing? Anyway, the format is
the same as for the "Fixes:" tag.
>>> device as to having an broken HPI implementation. After talking some
>>> with Hans, we now think it is actually the mmc controller that can be
>>> broken and not support broken HPI's.
>>>
>>> This patch adds a new capability, mmc-broken-hpi, which allows us to
>>> mark a broken hpi implementation on the host level.
>>>
>>> Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
>> [...]
MBR, Sergei
next prev parent reply other threads:[~2016-04-19 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:12 [PATCHv1 0/2] mmc: Move broken-hpi also to the chipset level Olliver Schinagl
2016-04-19 7:12 ` [PATCH 1/2] mmc: core: Improve marking broken HPI through devicetree Olliver Schinagl
2016-04-19 9:29 ` Ulf Hansson
2016-04-19 9:42 ` Olliver Schinagl
2016-04-19 9:49 ` Jaehoon Chung
2016-04-19 12:20 ` Olliver Schinagl
2016-04-19 12:44 ` Jaehoon Chung
2016-04-19 9:51 ` Ulf Hansson
2016-04-19 11:22 ` Hans de Goede
2016-04-19 12:45 ` Olliver Schinagl
2016-04-19 19:20 ` Ulf Hansson
2016-04-19 10:52 ` Sergei Shtylyov
2016-04-19 12:21 ` Olliver Schinagl
2016-04-19 13:23 ` Sergei Shtylyov [this message]
2016-04-19 7:12 ` [PATCH 2/2] mmc: sunxi: Mark the HPI of the mmc controller broken by default Olliver Schinagl
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=5716315C.7070001@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox