All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Doug Anderson <dianders@chromium.org>,
	Rui Miguel Silva <rmfrfs@gmail.com>, Chris Ball <cjb@laptop.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mmc: mxs-mmc: Disable the 'reg_vmmc' regulator when needed
Date: Wed, 26 May 2021 09:46:32 +0200	[thread overview]
Message-ID: <fa7e957e-4b3d-6ff6-1f72-e630eda2960d@wanadoo.fr> (raw)
In-Reply-To: <CAPDyKFptO4PRc=kxd9k8CkofGfyfJB6pdxP-wzrNpSHv0+ya0Q@mail.gmail.com>

Le 26/05/2021 à 00:47, Ulf Hansson a écrit :
> If I put together some patch and submit it, would you be able help to
> run some tests of it, as I don't have access to HW?

No, I won't be able to help.
This only got triggered by a static analysis checker (a own made 
coccinelle script) and I don't have the hardware to test anything.

This is why I can't propose an updated proposal. Trial & error 
development when you can't test by yourself is only counterproductive.

CJ

> 
> Kind regards
> Uffe
> 


WARNING: multiple messages have this Message-ID (diff)
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Doug Anderson <dianders@chromium.org>,
	Rui Miguel Silva <rmfrfs@gmail.com>, Chris Ball <cjb@laptop.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mmc: mxs-mmc: Disable the 'reg_vmmc' regulator when needed
Date: Wed, 26 May 2021 09:46:32 +0200	[thread overview]
Message-ID: <fa7e957e-4b3d-6ff6-1f72-e630eda2960d@wanadoo.fr> (raw)
In-Reply-To: <CAPDyKFptO4PRc=kxd9k8CkofGfyfJB6pdxP-wzrNpSHv0+ya0Q@mail.gmail.com>

Le 26/05/2021 à 00:47, Ulf Hansson a écrit :
> If I put together some patch and submit it, would you be able help to
> run some tests of it, as I don't have access to HW?

No, I won't be able to help.
This only got triggered by a static analysis checker (a own made 
coccinelle script) and I don't have the hardware to test anything.

This is why I can't propose an updated proposal. Trial & error 
development when you can't test by yourself is only counterproductive.

CJ

> 
> Kind regards
> Uffe
> 


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

  reply	other threads:[~2021-05-26  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 12:36 [PATCH] mmc: mxs-mmc: Disable the 'reg_vmmc' regulator when needed Christophe JAILLET
2021-05-21 12:36 ` Christophe JAILLET
2021-05-24 13:59 ` Ulf Hansson
2021-05-24 13:59   ` Ulf Hansson
2021-05-25 19:31   ` Christophe JAILLET
2021-05-25 19:31     ` Christophe JAILLET
2021-05-25 22:47     ` Ulf Hansson
2021-05-25 22:47       ` Ulf Hansson
2021-05-26  7:46       ` Christophe JAILLET [this message]
2021-05-26  7:46         ` Christophe JAILLET

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=fa7e957e-4b3d-6ff6-1f72-e630eda2960d@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=cjb@laptop.org \
    --cc=dianders@chromium.org \
    --cc=festevam@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rmfrfs@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@linaro.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 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.