RE: [char-misc-next 0/9 RESEND] mei: support for async event notifications
> > > > and consume the event notifications. > > > > The asynchronous nature is provided via poll and fasync. > > > > > > What changed to require a RESEND? > > > > You've asked for it. > > You might want to give me some context, as I have no idea why I asked > for a resend. Obviously you must have done something to the series from > the previous one, right? Quoting from (https://lkml.org/lkml/2015/7/23/5) and referring to the second sentence. 'Due to the changes in Linus's tree, this doesn't apply to 4.2-rc3. Can you refresh this series and resend? Same for the other outstanding mei patches you have sent that I haven't applied.' Thanks Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [char-misc-next 0/9 RESEND] mei: support for async event notifications
and consume the event notifications. The asynchronous nature is provided via poll and fasync. What changed to require a RESEND? You've asked for it. You might want to give me some context, as I have no idea why I asked for a resend. Obviously you must have done something to the series from the previous one, right? Quoting from (https://lkml.org/lkml/2015/7/23/5) and referring to the second sentence. 'Due to the changes in Linus's tree, this doesn't apply to 4.2-rc3. Can you refresh this series and resend? Same for the other outstanding mei patches you have sent that I haven't applied.' Thanks Tomas -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications
On Mon, Jul 27, 2015 at 06:36:18AM +, Winkler, Tomas wrote: > > > > > On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: > > > FW has gained new capability where a FW client can asynchronously > > > notify the host that an event has occurred in its process. > > > The notification doesn't provide any data and host may need to query > > > further the FW client in order to get details of the event. > > > New IOCTLs are introduced for the user space to enable/disable > > > and consume the event notifications. > > > The asynchronous nature is provided via poll and fasync. > > > > What changed to require a RESEND? > > You've asked for it. You might want to give me some context, as I have no idea why I asked for a resend. Obviously you must have done something to the series from the previous one, right? thanks, greg "short term memory of a squirrel" k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications
On Mon, Jul 27, 2015 at 06:36:18AM +, Winkler, Tomas wrote: On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: FW has gained new capability where a FW client can asynchronously notify the host that an event has occurred in its process. The notification doesn't provide any data and host may need to query further the FW client in order to get details of the event. New IOCTLs are introduced for the user space to enable/disable and consume the event notifications. The asynchronous nature is provided via poll and fasync. What changed to require a RESEND? You've asked for it. You might want to give me some context, as I have no idea why I asked for a resend. Obviously you must have done something to the series from the previous one, right? thanks, greg short term memory of a squirrel k-h -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [char-misc-next 0/9 RESEND] mei: support for async event notifications
> > On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: > > FW has gained new capability where a FW client can asynchronously > > notify the host that an event has occurred in its process. > > The notification doesn't provide any data and host may need to query > > further the FW client in order to get details of the event. > > New IOCTLs are introduced for the user space to enable/disable > > and consume the event notifications. > > The asynchronous nature is provided via poll and fasync. > > What changed to require a RESEND? You've asked for it. Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [char-misc-next 0/9 RESEND] mei: support for async event notifications
On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: FW has gained new capability where a FW client can asynchronously notify the host that an event has occurred in its process. The notification doesn't provide any data and host may need to query further the FW client in order to get details of the event. New IOCTLs are introduced for the user space to enable/disable and consume the event notifications. The asynchronous nature is provided via poll and fasync. What changed to require a RESEND? You've asked for it. Tomas -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications
On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: > FW has gained new capability where a FW client can asynchronously > notify the host that an event has occurred in its process. > The notification doesn't provide any data and host may need to query > further the FW client in order to get details of the event. > New IOCTLs are introduced for the user space to enable/disable > and consume the event notifications. > The asynchronous nature is provided via poll and fasync. What changed to require a RESEND? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[char-misc-next 0/9 RESEND] mei: support for async event notifications
FW has gained new capability where a FW client can asynchronously notify the host that an event has occurred in its process. The notification doesn't provide any data and host may need to query further the FW client in order to get details of the event. New IOCTLs are introduced for the user space to enable/disable and consume the event notifications. The asynchronous nature is provided via poll and fasync. Alexander Usyskin (1): mei: bus: add and call callback on notify event Tomas Winkler (8): mei: define async notification hbm commands mei: implement async notification hbm messages mei: enable async event notifications only from hbm version 2.0 mei: add mei_cl_notify_request command mei: add a handler that waits for notification on event mei: add async event notification ioctls mei: support polling for event notification mei: implement fasync for event notification Documentation/ioctl/ioctl-number.txt | 2 + Documentation/misc-devices/mei/mei.txt | 45 ++- drivers/misc/mei/bus.c | 50 +++- drivers/misc/mei/client.c | 224 + drivers/misc/mei/client.h | 8 ++ drivers/misc/mei/debugfs.c | 2 + drivers/misc/mei/hbm.c | 136 drivers/misc/mei/hbm.h | 2 + drivers/misc/mei/hw.h | 68 ++ drivers/misc/mei/interrupt.c | 7 ++ drivers/misc/mei/main.c| 96 ++ drivers/misc/mei/mei_dev.h | 15 +++ drivers/nfc/mei_phy.c | 3 +- include/linux/mei_cl_bus.h | 4 + include/uapi/linux/mei.h | 19 +++ 15 files changed, 675 insertions(+), 6 deletions(-) -- 2.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[char-misc-next 0/9 RESEND] mei: support for async event notifications
FW has gained new capability where a FW client can asynchronously notify the host that an event has occurred in its process. The notification doesn't provide any data and host may need to query further the FW client in order to get details of the event. New IOCTLs are introduced for the user space to enable/disable and consume the event notifications. The asynchronous nature is provided via poll and fasync. Alexander Usyskin (1): mei: bus: add and call callback on notify event Tomas Winkler (8): mei: define async notification hbm commands mei: implement async notification hbm messages mei: enable async event notifications only from hbm version 2.0 mei: add mei_cl_notify_request command mei: add a handler that waits for notification on event mei: add async event notification ioctls mei: support polling for event notification mei: implement fasync for event notification Documentation/ioctl/ioctl-number.txt | 2 + Documentation/misc-devices/mei/mei.txt | 45 ++- drivers/misc/mei/bus.c | 50 +++- drivers/misc/mei/client.c | 224 + drivers/misc/mei/client.h | 8 ++ drivers/misc/mei/debugfs.c | 2 + drivers/misc/mei/hbm.c | 136 drivers/misc/mei/hbm.h | 2 + drivers/misc/mei/hw.h | 68 ++ drivers/misc/mei/interrupt.c | 7 ++ drivers/misc/mei/main.c| 96 ++ drivers/misc/mei/mei_dev.h | 15 +++ drivers/nfc/mei_phy.c | 3 +- include/linux/mei_cl_bus.h | 4 + include/uapi/linux/mei.h | 19 +++ 15 files changed, 675 insertions(+), 6 deletions(-) -- 2.4.3 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications
On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote: FW has gained new capability where a FW client can asynchronously notify the host that an event has occurred in its process. The notification doesn't provide any data and host may need to query further the FW client in order to get details of the event. New IOCTLs are introduced for the user space to enable/disable and consume the event notifications. The asynchronous nature is provided via poll and fasync. What changed to require a RESEND? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
