From: Tejun Heo <htejun@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev queue error
Date: Wed, 15 Jun 2011 07:13:55 +0000 [thread overview]
Message-ID: <20110615071355.GJ8141@htj.dyndns.org> (raw)
In-Reply-To: <BANLkTim9kJEroUeqpqNoE-tCRvxa5=nghw@mail.gmail.com>
Hello, Kay.
Looks good to me. Just some nitpicks.
On Tue, Jun 14, 2011 at 10:24:16PM +0200, Kay Sievers wrote:
> - if (last_present != cd->media_present)
> + if (last_present != cd->media_present) {
> events |= DISK_EVENT_MEDIA_CHANGE;
> + } else if (events & DISK_EVENT_MEDIA_CHANGE) {
> + cd->tur_mismatch++;
> + printk("sr: GET_EVENT_STATUS_NOTIFICATION but TUR unchanged, "
> + "last_present %i <-> cd->media_present %i, count %i\n", last_present, cd->media_present, cd->tur_mismatch);
I suppose the above printk is for debugging and will be removed when
posting for inclusion?
> + if (cd->tur_mismatch > 8) {
> + printk("sr: GET_EVENT_STATUS_NOTIFICATION but TUR unchanged, "
> + "ignoring all future GET_EVENT_STATUS_NOTIFICATION\n");
> + cd->ignore_get_event = true;
sdev_printk(KERN_WARNING, ...) would probably be a better fit.
> + }
> + } else if (cd->tur_mismatch) {
> + printk("sr: GET_EVENT_STATUS_NOTIFICATION = TUR, "
> + "clear mismatch count %i\n", cd->tur_mismatch);
> + cd->tur_mismatch = 0;
Ditto, we probably don't want the above in the final version.
Thank you.
--
tejun
next prev parent reply other threads:[~2011-06-15 7:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:46 udev queue error Markus Rathgeb
2011-05-30 20:06 ` Kay Sievers
2011-05-31 15:31 ` Tejun Heo
2011-05-31 15:34 ` Markus Rathgeb
2011-05-31 15:40 ` Kay Sievers
2011-05-31 15:46 ` Kay Sievers
2011-06-01 1:39 ` Tejun Heo
2011-06-01 2:10 ` Kay Sievers
2011-06-01 4:42 ` Tejun Heo
2011-06-08 11:55 ` Kay Sievers
2011-06-09 11:54 ` Tejun Heo
2011-06-09 12:36 ` Kay Sievers
2011-06-12 12:28 ` Tejun Heo
2011-06-13 19:02 ` Kay Sievers
2011-06-14 20:24 ` Kay Sievers
2011-06-15 7:13 ` Tejun Heo [this message]
2011-06-15 9:34 ` Kay Sievers
2011-06-15 9:40 ` Tejun Heo
2011-06-18 21:41 ` Kay Sievers
2011-06-28 13:45 ` Tejun Heo
2011-06-28 15:53 ` Tejun Heo
2011-06-28 15:57 ` Tejun Heo
2011-06-28 22:20 ` Kay Sievers
2011-06-28 22:21 ` Kay Sievers
2011-06-29 20:54 ` Markus Rathgeb
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=20110615071355.GJ8141@htj.dyndns.org \
--to=htejun@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/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).