From: Andreas Kemnade <andreas@kemnade.info>
To: David Rivshin <drivshin@awxrd.com>
Cc: linux-pwm@vger.kernel.org, Ladislav Michl <ladis@linux-mips.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Tony Lindgren <tony@atomide.com>, Keerthy <j-keerthy@ti.com>,
Thierry Reding <thierry.reding@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] pwm: pwm-omap-dmtimer: return -EPROBE_DEFER if no dmtimer platform data
Date: Tue, 31 Jul 2018 07:28:21 +0200 [thread overview]
Message-ID: <20180731072803.61d364db@kemnade.info> (raw)
In-Reply-To: <20180730223030.10628-1-drivshin@awxrd.com>
[-- Attachment #1.1: Type: text/plain, Size: 661 bytes --]
Hi,
On Mon, 30 Jul 2018 18:30:30 -0400
David Rivshin <drivshin@awxrd.com> wrote:
> From: David Rivshin <DRivshin@allworx.com>
>
> If a pwm-omap-dmtimer is probed before the dmtimer it uses, the platform
> data won't be set yet.
>
you can of course have my Tested-by:
The version without message runs without trouble in daily use
here on top of 4.17.10. Did also some testing on 4.18-rc7 and I also tested this version.
I personally have no strange feeling about what dev_XXX() you have.
I hope not too many other developers spend time to fix this just to find out
that something like this is already in review queue.
Regards,
Andreas
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-07-31 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 22:30 [PATCH v3] pwm: pwm-omap-dmtimer: return -EPROBE_DEFER if no dmtimer platform data David Rivshin
2018-07-31 5:28 ` Andreas Kemnade [this message]
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=20180731072803.61d364db@kemnade.info \
--to=andreas@kemnade.info \
--cc=drivshin@awxrd.com \
--cc=hns@goldelico.com \
--cc=j-keerthy@ti.com \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.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