From: Oliver Neukum <oneukum@suse.com>
To: guido@kiener-muenchen.de
Cc: dpenkler@gmail.com, steve_bayless@keysight.com,
gregkh@linuxfoundation.org, pankaj.adhikari@ni.com,
guido.kiener@rohde-schwarz.com, linux-usb@vger.kernel.org
Subject: [07/12] usb: usbtmc: Add ioctl USBTMC488_IOCTL_WAIT_SRQ
Date: Mon, 28 May 2018 14:36:06 +0200 [thread overview]
Message-ID: <1527510966.6190.6.camel@suse.com> (raw)
Am Montag, den 28.05.2018, 10:59 +0000 schrieb guido@kiener-
muenchen.de:
> > No, the problem is that you will underflow io->mutex
> >
>
> Don't worry. The function usbtmc488_ioctl_wait_srq is called by
> usbtmc_ioctl which already locks the mutex. See
> https://elixir.bootlin.com/linux/v4.17-rc7/source/drivers/usb/class/usbtmc.c#L1189
> So the mutex is just unlocked here to allow other threads to still communicate
> with the device.
Hi,
thanks I had overlooked that.
Regards
Oliver
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-28 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 12:36 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 10:59 [07/12] usb: usbtmc: Add ioctl USBTMC488_IOCTL_WAIT_SRQ Guido Kiener
2018-05-25 11:17 Oliver Neukum
2018-05-24 12:59 Guido Kiener
2018-05-23 16:33 Greg Kroah-Hartman
2018-05-23 12:08 Oliver Neukum
2018-05-18 15:17 Guido Kiener
2018-05-18 15:07 Greg Kroah-Hartman
2018-05-18 15:02 Guido Kiener
2018-05-18 13:38 Greg Kroah-Hartman
2018-05-17 17:03 Guido Kiener
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=1527510966.6190.6.camel@suse.com \
--to=oneukum@suse.com \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guido.kiener@rohde-schwarz.com \
--cc=guido@kiener-muenchen.de \
--cc=linux-usb@vger.kernel.org \
--cc=pankaj.adhikari@ni.com \
--cc=steve_bayless@keysight.com \
/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).