From: Vinod Koul <vkoul@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>, Peng Ma <peng.ma@nxp.com>
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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wen He <wen.he_1@nxp.com>, Palmer Dabbelt <palmer@sifive.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>, Ard Biesheuvel <ard.b>
Subject: Re: linux-next: Tree for Dec 21
Date: Mon, 31 Dec 2018 19:31:02 +0530 [thread overview]
Message-ID: <20181231140102.GC7581@vkoul-mobl> (raw)
In-Reply-To: <20181221162149.GA32500@roeck-us.net>
On 21-12-18, 08:21, Guenter Roeck wrote:
> On Fri, Dec 21, 2018 at 07:32:44PM +1100, Stephen Rothwell wrote:
> [6]:
>
> Build failure.
>
> # bad: [340ae71f9dd421227a58c14a909b63033745dca4] Add linux-next specific files for 20181221
> # good: [7566ec393f4161572ba6f11ad5171fd5d59b0fbd] Linux 4.20-rc7
> git bisect start 'HEAD' 'v4.20-rc7'
> # good: [9f3de88514b2b5666214f0be3bc98d4e7136a7f1] Merge remote-tracking branch 'mtd/mtd/next'
> git bisect good 9f3de88514b2b5666214f0be3bc98d4e7136a7f1
> # good: [f4dd556a2cc77f672b9ba585aaad094a6fe09cf7] Merge remote-tracking branch 'spi/for-next'
> git bisect good f4dd556a2cc77f672b9ba585aaad094a6fe09cf7
> # good: [75f0840128c421df5e1741f5df22a34409bb5d72] Merge remote-tracking branch 'char-misc/char-misc-next'
> git bisect good 75f0840128c421df5e1741f5df22a34409bb5d72
> # bad: [4faff5eba474594068ea7f4542af209ab3e66911] Merge remote-tracking branch 'scsi/for-next'
> git bisect bad 4faff5eba474594068ea7f4542af209ab3e66911
> # good: [e894075934a44ef66413fd1046808542011d8552] staging: mt7621-mmc: Fix incompletely removed #if 0 block in sd.c
> git bisect good e894075934a44ef66413fd1046808542011d8552
> # good: [c1b104755b0b11579e292aa153c0605264c81648] scsi: smartpqi: add support for huawei controllers
> git bisect good c1b104755b0b11579e292aa153c0605264c81648
> # good: [695e62f9d1350169ed2bb6c5f164a6a1b1aaae50] Merge remote-tracking branch 'icc/icc-next'
> git bisect good 695e62f9d1350169ed2bb6c5f164a6a1b1aaae50
> # bad: [2b4b64840d7f6929213c0abce72eec7b7b784949] Merge branch 'topic/fsl' into next
> git bisect bad 2b4b64840d7f6929213c0abce72eec7b7b784949
> # good: [c03ec9cbc1c18058d5175998dffec24e40cb709f] Merge branch 'topic/dw' into next
> git bisect good c03ec9cbc1c18058d5175998dffec24e40cb709f
> # good: [1fa4ce0b2caccfd5fb0a37a03cade2ee1dbb0452] Merge branch 'topic/dmatest' into next
> git bisect good 1fa4ce0b2caccfd5fb0a37a03cade2ee1dbb0452
> # good: [531971231dac0edf17af32b06f09681f6506c0a1] dmaengine: sprd: Add me as one of the module authors
> git bisect good 531971231dac0edf17af32b06f09681f6506c0a1
> # bad: [b1bd47b638d4d304b98f68abfee9ee897c1a1939] dt-bindings: fsl-qdma: Add NXP Layerscpae qDMA controller bindings
> git bisect bad b1bd47b638d4d304b98f68abfee9ee897c1a1939
> # bad: [68997fff94afa51b5f74dd90aceec74ce13b3253] dmaengine: fsldma: Adding macro FSL_DMA_IN/OUT implement for ARM platform
> git bisect bad 68997fff94afa51b5f74dd90aceec74ce13b3253
> # good: [ca4f826040111c6746e2378dc45d9c0af3991a09] dmaengine: fsldma: Replace DMA_IN/OUT by FSL_DMA_IN/OUT
> git bisect good ca4f826040111c6746e2378dc45d9c0af3991a09
> # first bad commit: [68997fff94afa51b5f74dd90aceec74ce13b3253] dmaengine: fsldma: Adding macro FSL_DMA_IN/OUT implement for ARM platform
Dropping these
--
~Vinod
next prev parent reply other threads:[~2018-12-31 14:01 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
2018-12-31 14:01 ` Vinod Koul [this message]
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=20181231140102.GC7581@vkoul-mobl \
--to=vkoul@kernel.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=gregkh@linuxfoundation.org \
--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=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).