public inbox for platform-driver-x86@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted
Date: Tue, 04 Jan 2022 11:07:52 +0000	[thread overview]
Message-ID: <bug-192831-215701-CrheCiliwk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-192831-215701@https.bugzilla.kernel.org/>

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

Andy Shevchenko (andy.shevchenko@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INSUFFICIENT_DATA

--- Comment #2 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
The bug is against v4.10, now we are almost at v5.16. Please, retest with the
latest kernel and fell free to reopen if the bug is still reproducible.

Note v4.10 is LTS, so if the bug is still there in the latest stable version of
it, but there is no such bug in the latest vanilla, try to bisect the fix
commit and then you may require to backport it.

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2022-01-04 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-192831-215701@https.bugzilla.kernel.org/>
2021-02-15 11:13 ` [Bug 192831] acer_wmi spamming logs with iio-sensor-prox Could not open input accel Operation not permitted bugzilla-daemon
2022-01-04 11:07 ` bugzilla-daemon [this message]
2022-01-04 11: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-192831-215701-CrheCiliwk@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=platform-driver-x86@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