On Mon, Nov 16, 2015 at 11:12:24AM -0500, ira.weiny wrote: > On Mon, Nov 16, 2015 at 10:00:04AM -0500, ira. weiny wrote: > > On Sun, Nov 15, 2015 at 08:09:18PM -0800, Greg KH wrote: > > > On Sun, Nov 15, 2015 at 01:17:00PM -0500, ira.weiny wrote: > > > > With the latest staging-testing and staging-next[*] I am getting the following panic. > > > > > > > > [*] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git > > > > > > So 4.4-rc1 also has this issue? > > > > Not sure about 4.4-rc1 I thought I tried master last week but I think I may > > have been pulling the wrong tree from kernel.org. Let me try again. > > It does not happen 4.4-rc1... > > And I just tested with your updated staging-testing and it worked... > > <sigh> I'm seeing different commit IDs for the HEAD of these trees. > > Current head of staging-testing > > 4811789503d1 staging: unisys: visorbus: visorbus_main.c: made checkpatch wa rning-free > be1d6cb3e657 Staging: fwserial: Declare fwtty_port_put as static > 3bf40d65dcbf staging/rdma/hfi1: use one-shot LCB write > > > My previous head. > > 26b4a300d775 staging: unisys: visorbus: visorbus_main.c: made checkpatch warning -free > ec1bacdc52b1 Staging: fwserial: Declare fwtty_port_put as static > 2a3e9651000b staging/rdma/hfi1: use one-shot LCB write > > How would that happen? > > I did not rebase the tree... At least that I recall? I was fetching your tree > all weekend to see if there was something different and nothing changed until > this morning? :-/ staging-testing is rebased at times, like during the merge window, it's for me to test with, I wouldn't count on it ever being "stable", please use staging-next for that, as that is what is merged in linux-next. Only use staging-testing if you need to sync up with me if I've taken a bunch of patches right then and they have not passed "testing" good enough to be merged to staging-next. And I just rebased it on 4.4-rc1, so that's why you saw the change happen. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
