From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Johan Hovold <johan@kernel.org>, Lee Jones <lee.jones@linaro.org>,
Support Opensource <support.opensource@diasemi.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Milo Kim <milo.kim@ti.com>,
patches@opensource.wolfsonmicro.com,
Fabio Estevam <fabio.estevam@freescale.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: da9052: fix broken regulator probe
Date: Tue, 19 May 2015 12:01:03 +0200 [thread overview]
Message-ID: <20150519100103.GM28127@localhost> (raw)
In-Reply-To: <20150518184654.GC2761@sirena.org.uk>
On Mon, May 18, 2015 at 07:46:54PM +0100, Mark Brown wrote:
> On Mon, May 18, 2015 at 06:46:30PM +0200, Johan Hovold wrote:
>
> > Yes, resending is sometimes needed, but what set me off here was your
> > comment that resending might not be enough even after you've now become
> > aware of a several-month old regression in your subsystem.
>
> If you're referring to my original reply I'm afraid to disappoint you
> but I hadn't read far enough in the backtrace to see anything except
> that people wanted me to look at a patch I didn't have a copy of (I
> didn't even know if I'd been CCed on the original posting). I was
> simply trying to say that it might be worth looking at other aspects of
> how the patch was sent - what you got there was basically a form letter
> type response to contentless pings.
I might have read too much into that response, but the pings were hardly
contentless (they all included the commit message and some the full patch).
Anyway, glad to see the issue resolved now. Thanks for the review.
Johan
next prev parent reply other threads:[~2015-05-19 10:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150325110231.GC10412@localhost>
2015-03-25 11:07 ` [PATCH 1/2] mfd: da9052: fix broken regulator probe Johan Hovold
2015-03-25 11:07 ` [PATCH 2/2] mfd: core: fix platform-device name collisions Johan Hovold
2015-03-25 12:02 ` Bartlomiej Zolnierkiewicz
2015-03-26 8:34 ` Lee Jones
2015-03-25 12:01 ` [PATCH 1/2] mfd: da9052: fix broken regulator probe Bartlomiej Zolnierkiewicz
2015-03-26 8:32 ` Lee Jones
2015-04-14 13:04 ` Johan Hovold
2015-04-29 7:44 ` Johan Hovold
2015-04-29 8:41 ` Lee Jones
2015-05-13 15:43 ` Lee Jones
2015-05-13 16:08 ` Mark Brown
2015-05-13 16:54 ` Lee Jones
2015-05-13 17:29 ` Mark Brown
2015-05-14 7:19 ` Lee Jones
2015-05-15 14:47 ` Johan Hovold
2015-05-18 9:10 ` Lee Jones
2015-05-18 9:51 ` Johan Hovold
2015-05-18 10:13 ` Lee Jones
2015-05-18 16:28 ` Mark Brown
2015-05-18 16:24 ` Mark Brown
2015-05-18 16:46 ` Johan Hovold
2015-05-18 18:46 ` Mark Brown
2015-05-19 10:01 ` Johan Hovold [this message]
2015-05-19 10:38 ` Mark Brown
2015-05-19 11:01 ` Johan Hovold
2015-05-19 12:01 ` Mark Brown
2015-05-15 14:27 ` [PATCH RESEND] " Johan Hovold
2015-05-18 18:47 ` Mark Brown
2015-05-18 18:57 ` Lee Jones
2015-03-30 7:18 ` [PATCH 1/2] " Lee Jones
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=20150519100103.GM28127@localhost \
--to=johan@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=milo.kim@ti.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=support.opensource@diasemi.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).