From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Andrew Morton <akpm@linux-foundation.org>,
Sinan Kaya <okaya@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Theodore Ts'o <tytso@mit.edu>, Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Wen He <wen.he_1@nxp.com>, Peng Ma <peng.ma@nxp.com>,
Vinod Koul <vkoul@kernel.org>, Palmer Dabbelt <palmer@sifive.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ard
Subject: Re: linux-next: Tree for Dec 21
Date: Mon, 24 Dec 2018 09:20:46 +0100 [thread overview]
Message-ID: <20181224082046.GD19684@kroah.com> (raw)
In-Reply-To: <20181221162149.GA32500@roeck-us.net>
On Fri, Dec 21, 2018 at 08:21:49AM -0800, Guenter Roeck wrote:
> ---
> [5]:
>
> The bisect is old, but still applies. Revering the offending patch fixes the problem.
>
> # bad: [8c9733fd9806c71e7f2313a280f98cb3051f93df] Add linux-next specific files for 20181123
> # good: [9ff01193a20d391e8dbce4403dd5ef87c7eaaca6] Linux 4.20-rc3
> git bisect start 'HEAD' 'v4.20-rc3'
> # good: [34c2101b4f765edf1b91c2837da9c60fbf9f6912] Merge remote-tracking branch 'spi-nor/spi-nor/next'
> git bisect good 34c2101b4f765edf1b91c2837da9c60fbf9f6912
> # good: [15367a0657fc8027ff3466bf0202bde9f270259b] Merge remote-tracking branch 'kgdb/kgdb-next'
> git bisect good 15367a0657fc8027ff3466bf0202bde9f270259b
> # bad: [d29686ab179c34c5dbaac067a9effbeeb6a8073e] Merge remote-tracking branch 'soundwire/next'
> git bisect bad d29686ab179c34c5dbaac067a9effbeeb6a8073e
> # good: [7cd63670817c236ccaf21ffe9d7b4921afeab130] Merge remote-tracking branch 'tip/auto-latest'
> git bisect good 7cd63670817c236ccaf21ffe9d7b4921afeab130
> # good: [597140853698c0dc174b93eb534406a40e467375] Merge remote-tracking branch 'rcu/rcu/next'
> git bisect good 597140853698c0dc174b93eb534406a40e467375
> # good: [acb97a35ae6d363144f4e3916bff5284a5a03d01] Merge remote-tracking branch 'phy-next/next'
> git bisect good acb97a35ae6d363144f4e3916bff5284a5a03d01
> # bad: [3f45b9087678824f50a34783db5a519f0d4d5e03] Merge remote-tracking branch 'tty/tty-next'
> git bisect bad 3f45b9087678824f50a34783db5a519f0d4d5e03
> # good: [61e169ee7683630ee0276dd5dcb5599976757770] serial: fsl_lpuart: fix the typo: UARTCR1_PE -> UARTCTRL_PE
> git bisect good 61e169ee7683630ee0276dd5dcb5599976757770
> # good: [646097940ad35aa2c1f2012af932d55976a9f255] serial: set suppress_bind_attrs flag only if builtin
> git bisect good 646097940ad35aa2c1f2012af932d55976a9f255
> # bad: [d6e1935819db0c91ce4a5af82466f3ab50d17346] serial: core: Allow processing sysrq at port unlock time
> git bisect bad d6e1935819db0c91ce4a5af82466f3ab50d17346
> # bad: [6d11023c345e369bcb9d5a68b271764e362c1f6e] serial: 8250: Default SERIAL_OF_PLATFORM to SERIAL_8250
> git bisect bad 6d11023c345e369bcb9d5a68b271764e362c1f6e
> # good: [347a28b586802d09604a149c1a1f6de5dccbe6fa] writeback: don't decrement wb->refcnt if !wb->bdi
> git bisect good 347a28b586802d09604a149c1a1f6de5dccbe6fa
> # first bad commit: [6d11023c345e369bcb9d5a68b271764e362c1f6e] serial: 8250: Default SERIAL_OF_PLATFORM to SERIAL_8250
Ok I have now reverted this patch, hopefully that resolves the issue.
thanks, and sorry it took this long to revert.
greg k-h
next prev parent reply other threads:[~2018-12-24 8:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:32 linux-next: Tree for Dec 21 Stephen Rothwell
2018-12-21 16:21 ` Guenter Roeck
2018-12-21 16:33 ` Ard Biesheuvel
2018-12-21 20:57 ` Florian Westphal
2018-12-22 6:43 ` Chandan Rajendra
2018-12-24 8:20 ` Greg Kroah-Hartman [this message]
2018-12-31 14:01 ` Vinod Koul
2018-12-21 16:37 ` linux-next: Tree for Dec 21 (acpi without CONFIG_PCI) Randy Dunlap
[not found] ` <CAK9iUCO_Pk3eYH+hyMuqU6weDsbzC9Sg1Z719fm8u_3Oh7s-iQ@mail.gmail.com>
2018-12-21 17:26 ` Randy Dunlap
2018-12-21 17:43 ` Randy Dunlap
2018-12-22 0:05 ` Sinan Kaya
2018-12-21 18:28 ` Randy Dunlap
2018-12-22 0:04 ` Sinan Kaya
2018-12-21 17:08 ` linux-next: Tree for Dec 21 (nvdimm/security.o) Randy Dunlap
2018-12-21 18:51 ` Dan Williams
2018-12-21 21:01 ` Dan Williams
2018-12-21 17:35 ` linux-next: Tree for Dec 21 (mmc/host/sdhci-omap.c) Randy Dunlap
2018-12-21 18:02 ` linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION) Randy Dunlap
2018-12-21 20:39 ` [alsa-devel] " Pierre-Louis Bossart
2018-12-21 18:36 ` linux-next: Tree for Dec 21 (FB_BACKLIGHT) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 10:42 linux-next: Tree for Dec 21 Stephen Rothwell
2021-12-21 12:27 Stephen Rothwell
2020-12-21 3:18 Stephen Rothwell
2017-12-21 4:41 Stephen Rothwell
2016-12-21 2:22 Stephen Rothwell
2015-12-21 8:05 Stephen Rothwell
2014-12-21 10:28 Stephen Rothwell
2012-12-21 3:25 Stephen Rothwell
2011-12-21 6:47 Stephen Rothwell
2011-12-21 23:15 ` Andrew Morton
2011-12-22 23:08 ` Andrew Morton
2011-12-22 23:20 ` Tejun Heo
2011-12-22 23:24 ` Andrew Morton
2011-12-22 23:38 ` Tejun Heo
2011-12-22 23:44 ` Andrew Morton
2011-12-22 23:46 ` Tejun Heo
2011-12-23 0:42 ` Tejun Heo
2011-12-24 5:13 ` Hugh Dickins
2011-12-25 16:08 ` Sedat Dilek
2011-12-25 23:55 ` Stephen Rothwell
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=20181224082046.GD19684@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=joel@joelfernandes.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=okaya@kernel.org \
--cc=palmer@sifive.com \
--cc=peng.ma@nxp.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=vkoul@kernel.org \
--cc=wen.he_1@nxp.com \
--cc=xypron.glpk@gmx.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 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).