linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"abdhalee@linux.vnet.ibm.com" <abdhalee@linux.vnet.ibm.com>,
	"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hch@lst.de" <hch@lst.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"hare@suse.com" <hare@suse.com>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>
Subject: Re: [BUG][bisected 270065e] linux-next fails to boot on powerpc
Date: Fri, 18 Aug 2017 22:13:36 +0000	[thread overview]
Message-ID: <1503094414.2622.21.camel@wdc.com> (raw)
In-Reply-To: <0f7e2114-eba1-f149-ea80-d32d8b6d212a@linux.vnet.ibm.com>

T24gRnJpLCAyMDE3LTA4LTE4IGF0IDE2OjU3IC0wNTAwLCBCcmlhbiBLaW5nIHdyb3RlOg0KPiBU
byBhZGQgdG8gbXkgYW5hbHlzaXMgYWJvdmUsICM5IHNob3VsZCBub3QgYmUgdGhlcmUuLi4gSXQg
bG9va3MgbGlrZQ0KPiBqaWZmaWVzX2F0X2FsbG9jIHdvdWxkIGFsc28gYmUgZ2V0dGluZyByZWlu
aXRpYWxpemVkIGluIHRoaXMgY2FzZSwgcmVzdWx0aW5nIGluDQo+IGEgcGVycGV0dWFsIHJldHJ5
LCB3aGljaCBpcyB3aGF0IEkgd2FzIHNlZWluZy4NCg0KSGVsbG8gQnJpYW4sDQoNClNvbWUgdGlt
ZSBhZ28gSSBub3RpY2VkIHRoYXQgamlmZmllc19hdF9hbGxvYyBpcyBpbmRlZWQgc2V0IHdoaWxl
IGEgY29tbWFuZA0KaXMgYmVpbmcgcHJlcGFyZWQgaW5zdGVhZCBvZiBhdCBjb21tYW5kIGFsbG9j
YXRpb24gdGltZS4gSSB0aGluayB0aGF0DQpiZWhhdmlvciB3YXMgaW50cm9kdWNlZCBpbiAyMDA1
IHRocm91Z2ggY29tbWl0IGIyMWE0MTM4NTExOCAoIltTQ1NJXSBhZGQNCmdsb2JhbCB0aW1lb3V0
IHRvIHRoZSBzY3NpIG1pZC1sYXllciIpLiBBdCB0aGF0IHRpbWUgU0NTSSBjb21tYW5kcyB3ZXJl
DQphbGxvY2F0ZWQgYXQgcHJlcCB0aW1lIGFuZCBmcmVlZCBhdCB1bnByZXAgdGltZS4gUmVjZW50
bHkgdGhhdCBoYXMgYmVlbg0KY2hhbmdlZCBzdWNoIHRoYXQgYSBTQ1NJIGNvbW1hbmQgKHN0cnVj
dCBzY3NpX2NtbmQpIGhhcyB0aGUgc2FtZSBsaWZldGltZSBhcw0Kc3RydWN0IHJlcXVlc3QuIElu
IG90aGVyIHdvcmRzLCBpdCB3YXMgbm90IHBvc3NpYmxlIGluIDIwMDUgYnV0IGl0IGlzDQpwb3Nz
aWJsZSB0b2RheSB0byBzZXQgamlmZmllc19hdF9hbGxvYyBhdCBjb21tYW5kIGFsbG9jYXRpb24g
dGltZSBpbnN0ZWFkIG9mDQp3aGVuIGEgY29tbWFuZCBpcyBiZWluZyBwcmVwYXJlZC4gRG8geW91
IHdhbnQgbWUgdG8gc3VibWl0IGEgcGF0Y2ggdGhhdA0KaW1wbGVtZW50cyB0aGlzIGNoYW5nZT8N
Cg0KQmFydC4NCg0K

  reply	other threads:[~2017-08-18 22:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 17:00 [BUG][bisected 270065e] linux-next fails to boot on powerpc Abdul Haleem
2017-08-16 17:21 ` Bart Van Assche
2017-08-16 23:18   ` Brian King
2017-08-17 15:52     ` Bart Van Assche
2017-08-18 21:04       ` Brian King
2017-08-18 21:17         ` [PATCH] ipr: Set no_report_opcodes for RAID arrays Brian King
2017-08-21 20:22           ` Martin K. Petersen
2017-08-18 21:41         ` [BUG][bisected 270065e] linux-next fails to boot on powerpc Bart Van Assche
2017-08-18 21:57           ` Brian King
2017-08-18 22:13             ` Bart Van Assche [this message]
2017-08-21 22:11               ` [PATCH 0/2] Allow scsi_prep_fn to occur for retried commands Brian King
2017-08-21 22:13                 ` [PATCH 1/2] scsi: Move scsi_cmd->jiffies_at_alloc initialization to allocation time Brian King
2017-08-21 22:16                   ` Brian King
2017-08-21 22:40                   ` [PATCHv2 " Brian King
2017-08-22  6:51                   ` [PATCH " hch
2017-08-21 22:14                 ` [PATCH 2/2] scsi: Preserve retry counter through scsi_prep_fn Brian King
2017-08-22  6:51                   ` hch
2017-08-22  6:42                 ` [PATCH 0/2] Allow scsi_prep_fn to occur for retried commands Abdul Haleem
2017-08-21 20:27             ` [BUG][bisected 270065e] linux-next fails to boot on powerpc Martin K. Petersen
2017-08-17  1:33   ` Michael Ellerman
2017-08-16 20:25 ` Bart Van Assche
2017-08-17  7:06   ` Michael Ellerman

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=1503094414.2622.21.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=abdhalee@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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).