All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kevin Hilman <khilman@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
	Tyler Baker <tyler.baker@linaro.org>,
	Sebastian Reichel <sre@kernel.org>, Felipe Balbi <balbi@ti.com>,
	Olof Johansson <olof@lixom.net>,
	Marek Belisko <marek@goldelico.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode"
Date: Sat, 7 Nov 2015 09:19:25 +1100	[thread overview]
Message-ID: <20151107091925.7dcd14a7@canb.auug.org.au> (raw)
In-Reply-To: <CAMAWPa-7_q8Sf+4VQ0EE6zU-NvacKERFgjqueNif=52Frn0enA@mail.gmail.com>

Hi Kevin,

On Fri, 6 Nov 2015 10:36:34 -0800 Kevin Hilman <khilman@kernel.org> wrote:
>
> On Fri, Nov 6, 2015 at 8:13 AM, Sebastian Reichel <sre@kernel.org> wrote:
> > This reverts commit af19161aaed7ff8d1a52b2e517460f2fa0774e32,
> > which breaks the omap3 device tree build due to a wrong reference.
> >
> > I accidently queued this change via the power supply subsystem while
> > telling Marek at the same time, that it should go through Tony's tree.
> > Following that I did miss Stephen's messages about the build failure in
> > linux-next and since he switched to merging an older snapshot nobody
> > else noticed the problem in my tree. I didn't notice myself, since I
> > did not build any device tree files assuming none have changed by me.
> >
> > Signed-off-by: Sebastian Reichel <sre@kernel.org>  
> 
> We also found this in kernelci.org build testing, and verified that
> this fixes the build.
> 
> Tested-by: Kevin Hilman <khilman@linaro.org>
> 
> Thanks Felipe for reporting, and thanks Sebastian for the quick fix.

I think "quick fix" is a bit rich.  I reported this to Sebastian on
Sept 29, Oct 2 , Oct 8, Oct 16, and Oct 21.  The only response I got
was from Marek Belisko on Oct 8 and 21.  I have been using the battery
tree (git://git.infradead.org/battery-2.6.git#master) from Sept 25, so
none of the commits after that have been in any linux-next release.

Yes, I am a little annoyed.  Do people have trouble receiving my emails?
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

WARNING: multiple messages have this Message-ID (diff)
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode"
Date: Sat, 7 Nov 2015 09:19:25 +1100	[thread overview]
Message-ID: <20151107091925.7dcd14a7@canb.auug.org.au> (raw)
In-Reply-To: <CAMAWPa-7_q8Sf+4VQ0EE6zU-NvacKERFgjqueNif=52Frn0enA@mail.gmail.com>

Hi Kevin,

On Fri, 6 Nov 2015 10:36:34 -0800 Kevin Hilman <khilman@kernel.org> wrote:
>
> On Fri, Nov 6, 2015 at 8:13 AM, Sebastian Reichel <sre@kernel.org> wrote:
> > This reverts commit af19161aaed7ff8d1a52b2e517460f2fa0774e32,
> > which breaks the omap3 device tree build due to a wrong reference.
> >
> > I accidently queued this change via the power supply subsystem while
> > telling Marek at the same time, that it should go through Tony's tree.
> > Following that I did miss Stephen's messages about the build failure in
> > linux-next and since he switched to merging an older snapshot nobody
> > else noticed the problem in my tree. I didn't notice myself, since I
> > did not build any device tree files assuming none have changed by me.
> >
> > Signed-off-by: Sebastian Reichel <sre@kernel.org>  
> 
> We also found this in kernelci.org build testing, and verified that
> this fixes the build.
> 
> Tested-by: Kevin Hilman <khilman@linaro.org>
> 
> Thanks Felipe for reporting, and thanks Sebastian for the quick fix.

I think "quick fix" is a bit rich.  I reported this to Sebastian on
Sept 29, Oct 2 , Oct 8, Oct 16, and Oct 21.  The only response I got
was from Marek Belisko on Oct 8 and 21.  I have been using the battery
tree (git://git.infradead.org/battery-2.6.git#master) from Sept 25, so
none of the commits after that have been in any linux-next release.

Yes, I am a little annoyed.  Do people have trouble receiving my emails?
-- 
Cheers,
Stephen Rothwell                    sfr at canb.auug.org.au

  parent reply	other threads:[~2015-11-06 22:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 16:13 [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode" Sebastian Reichel
2015-11-06 16:13 ` Sebastian Reichel
2015-11-06 16:23 ` Felipe Balbi
2015-11-06 16:23   ` Felipe Balbi
2015-11-06 18:36 ` Kevin Hilman
2015-11-06 18:36   ` Kevin Hilman
2015-11-06 19:03   ` Tony Lindgren
2015-11-06 19:03     ` Tony Lindgren
2015-11-06 22:19   ` Stephen Rothwell [this message]
2015-11-06 22:19     ` Stephen Rothwell
2015-11-06 22:36     ` Kevin Hilman
2015-11-06 22:36       ` Kevin Hilman
2015-11-07  2:44     ` Sebastian Reichel
2015-11-07  2:44       ` Sebastian Reichel
2015-11-07  3:40       ` Stephen Rothwell
2015-11-07  3:40         ` Stephen Rothwell
2015-11-06 20:21 ` Belisko Marek
2015-11-06 20:21   ` Belisko Marek
2015-11-09 14:17 ` Tony Lindgren
2015-11-09 14:17   ` Tony Lindgren

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=20151107091925.7dcd14a7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=balbi@ti.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek@goldelico.com \
    --cc=olof@lixom.net \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    --cc=tyler.baker@linaro.org \
    /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.