search

davidker / unisys

Master repository for new changes to drivers/staging/unisys and drivers/visorbus
Other
2 stars 1 forks source link

visorbus_device.responded_to_device_create #19

Closed AlexanderCurtin closed 8 years ago

AlexanderCurtin commented 8 years ago

This is defined in visorbus.h, but never used. Probably should either remove it figure out why it was there in the first place and do that.

davidker commented 8 years ago

Thanks Alex, I will look into it.

David

AlexanderCurtin commented 8 years ago

A fix for this was committed to the issue/19-upstream-next-curtinap-responded_to_device_create branch.

5eb5c23b6583f1c9cd1083a1a586d7759649610c

AlexanderCurtin commented 8 years ago

@davidker

selltc commented 8 years ago

I see this being submitted upstream on 4/6 11:20am. But I don't see Greg ever accepting it. If that's true, why is this closed? (I only noticed this because I was working with a patch that wouldn't fit because of this difference between staging-next and upstream-next.)

selltc commented 8 years ago

This seems to be in Greg's staging-testing, but not staging-next.

davidker commented 8 years ago

We have gotten emails that it was approved to go to staging-next. I haven't seen him actually update the kernel.org version of staging-next. I should have just moved it to Done but not closed it. Sorry still dealing with KanBoard issues.