linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Stefan Agner <stefan@agner.ch>,
	Marcel Ziswiler <marcel@ziswiler.com>,
	linux-tegra@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] pinctrl: tegra: Move drivers registration to arch_init level
Date: Mon, 06 Aug 2018 12:15:41 +0300	[thread overview]
Message-ID: <2086462.IQpRViTvQm@dimapc> (raw)
In-Reply-To: <4576764.PLucfz68jK@dimapc>

On Thursday, 2 August 2018 16:01:24 MSK Dmitry Osipenko wrote:
> On Thursday, 2 August 2018 14:11:43 MSK Dmitry Osipenko wrote:
> > There is a bug in regards to deferred probing within the drivers core
> > that causes GPIO-driver to suspend after its users. The bug appears if
> 
> I meant "before its users", of course. If the rest of the patches is fine,
> please let me know if re-sending is needed or you'll correct the comment in
> place while applying.

Linus, please pick up the v2.

  reply	other threads:[~2018-08-06  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 11:11 [PATCH v1 1/2] pinctrl: tegra: Move drivers registration to arch_init level Dmitry Osipenko
2018-08-02 11:11 ` [PATCH v1 2/2] gpio: tegra: Move driver registration to subsys_init level Dmitry Osipenko
2018-08-02 11:31 ` [PATCH v1 1/2] pinctrl: tegra: Move drivers registration to arch_init level Stefan Agner
2018-08-03 17:24   ` Linus Walleij
2018-08-04 14:01     ` Dmitry Osipenko
2018-08-06 13:03       ` Stefan Agner
2018-08-06 13:38         ` Dmitry Osipenko
2018-08-06 21:01           ` Stefan Agner
2018-08-02 13:01 ` Dmitry Osipenko
2018-08-06  9:15   ` Dmitry Osipenko [this message]
2018-08-06 10:37     ` Linus Walleij
2018-08-03 17:18 ` Linus Walleij

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=2086462.IQpRViTvQm@dimapc \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marcel@ziswiler.com \
    --cc=stefan@agner.ch \
    --cc=thierry.reding@gmail.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).