linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Olliver Schinagl <oliver@schinagl.nl>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Chen-Yu Tsai <wens@csie.org>,
	Venu Byravarasu <vbyravarasu@nvidia.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Michal Hocko <mhocko@suse.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Sudeep Holla <Sudeep.Holla@arm.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Wenkai Du <wenkai.du@intel.com>,
	Chaotian Jing <chaotian.jing@mediatek.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Michal Suchanek <hramrach@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] mmc: core: Improve marking broken HPI through devicetree
Date: Tue, 19 Apr 2016 13:52:54 +0300	[thread overview]
Message-ID: <57160E06.1000806@cogentembedded.com> (raw)
In-Reply-To: <1461049934-12848-2-git-send-email-oliver@schinagl.nl>

Hello.

On 4/19/2016 10:12 AM, 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.

> 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

  parent reply	other threads:[~2016-04-19 10:53 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 [this message]
2016-04-19 12:21     ` Olliver Schinagl
2016-04-19 13:23       ` Sergei Shtylyov
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=57160E06.1000806@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=Sudeep.Holla@arm.com \
    --cc=adrian.hunter@intel.com \
    --cc=chaotian.jing@mediatek.com \
    --cc=hdegoede@redhat.com \
    --cc=hramrach@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mhocko@suse.com \
    --cc=oliver@schinagl.nl \
    --cc=ulf.hansson@linaro.org \
    --cc=vbyravarasu@nvidia.com \
    --cc=wenkai.du@intel.com \
    --cc=wens@csie.org \
    --cc=wsa+renesas@sang-engineering.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 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).