All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@kernel.org
Subject: [Bug 198161] incremental patch-4.9.51-52 on sg.c break Nero 4 nero burning rom application
Date: Sat, 16 Dec 2017 14:02:21 +0000	[thread overview]
Message-ID: <bug-198161-11613-VKiUSHDhzt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198161-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198161

--- Comment #3 from Jean-Luc (luc.bertho@gmail.com) ---
(In reply to Johannes Thumshirn from comment #2)
> (In reply to Jean-Luc from comment #0)
> > Hi
> > 
> > Nero 4 Linux can no longer detect devices since the changes in code in
> sg.c.
> > It displays the following message: "Warning: no device detected"...
> > 
> > Regards
> 
> Can you please re-test with a more recent kernel (e.g. v4.14) ? I have had
> submitted a fix for exactly this issue with Nero and believe it is gone.

Hello Johannes,
the only versions of the kernel that seem impacted are kernel 4.9.52-> 4.9.69
I saw your fix for the kernel version 4.12 and I checked it successfully with a
4.12.1 kernel
the latest version of the kernel is not affected by this bug.

Versions tested and OK: 
4.12.1 (with your patch)
4.13.1
4.14.5

I also try kernel 4.10.0-42-generic
(VirtualBox, Ubuntu), ok too

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2017-12-16 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  2:35 [Bug 198161] New: incremental patch-4.9.51-52 on sg.c break Nero 4 nero burning rom application bugzilla-daemon
2017-12-14  5:14 ` [Bug 198161] " bugzilla-daemon
2017-12-14  9:24 ` bugzilla-daemon
2017-12-16 14:02 ` bugzilla-daemon [this message]
2017-12-16 14:10 ` bugzilla-daemon

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=bug-198161-11613-VKiUSHDhzt@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.