All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
	Wolfram Sang <wsa@the-dreams.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Regression in next caused by 95026658c46e i2c: do not use internal..
Date: Mon, 14 Mar 2016 09:09:45 -0700	[thread overview]
Message-ID: <20160314160944.GG9329@atomide.com> (raw)

Hi Sudip & Wolfram,

Looks like commit 95026658c46e ("i2c: do not use internal data from
driver core") in Linux next introduced a regression breaking booting
on most ARM boards according to kernelci.org [0].

Having something like this happen just as the merge window opens is
not nice. You guys should already know.. The patches in next should
be sitting there for a few weeks before the merge window so issues
like this are found out early.

Regards,

Tony

[0] https://kernelci.org/boot/all/job/next/

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression in next caused by 95026658c46e i2c: do not use internal..
Date: Mon, 14 Mar 2016 09:09:45 -0700	[thread overview]
Message-ID: <20160314160944.GG9329@atomide.com> (raw)

Hi Sudip & Wolfram,

Looks like commit 95026658c46e ("i2c: do not use internal data from
driver core") in Linux next introduced a regression breaking booting
on most ARM boards according to kernelci.org [0].

Having something like this happen just as the merge window opens is
not nice. You guys should already know.. The patches in next should
be sitting there for a few weeks before the merge window so issues
like this are found out early.

Regards,

Tony

[0] https://kernelci.org/boot/all/job/next/

             reply	other threads:[~2016-03-14 16:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 16:09 Tony Lindgren [this message]
2016-03-14 16:09 ` Regression in next caused by 95026658c46e i2c: do not use internal Tony Lindgren
2016-03-14 16:52 ` Wolfram Sang
2016-03-14 16:52   ` Wolfram Sang
2016-03-14 17:26   ` Tony Lindgren
2016-03-14 17:26     ` Tony Lindgren
2016-03-14 17:35 ` Sudip Mukherjee
2016-03-14 17:35   ` Sudip Mukherjee

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=20160314160944.GG9329@atomide.com \
    --to=tony@atomide.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    --cc=wsa@the-dreams.de \
    /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.