linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217089] xone23c mixer
Date: Wed, 01 Mar 2023 15:39:45 +0000	[thread overview]
Message-ID: <bug-217089-208809-Mdum6v1pXz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217089-208809@https.bugzilla.kernel.org/>

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

--- Comment #21 from Pierre Germain (pierre2008@gmail.com) ---
(In reply to Alan Stern from comment #20)
> In the meantime, you can mark this bug report closed.

Sorry Alan, I don't see that option, I think I would need more permissions.
There should be a Edit link next to Status: NEW but I don't have that option.

-- 
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:[~2023-03-01 15:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  9:36 [Bug 217089] New: xone23c mixer bugzilla-daemon
2023-02-26 19:15 ` [Bug 217089] " bugzilla-daemon
2023-02-26 21:33 ` bugzilla-daemon
2023-02-26 22:33 ` bugzilla-daemon
2023-02-27 10:02 ` bugzilla-daemon
2023-02-27 21:22 ` bugzilla-daemon
2023-02-27 21:23 ` bugzilla-daemon
2023-02-27 21:24 ` bugzilla-daemon
2023-02-27 21:25 ` bugzilla-daemon
2023-02-27 21:33 ` bugzilla-daemon
2023-02-28  2:13 ` bugzilla-daemon
2023-02-28 11:06 ` bugzilla-daemon
2023-02-28 11:07 ` bugzilla-daemon
2023-02-28 11:09 ` bugzilla-daemon
2023-02-28 11:13 ` bugzilla-daemon
2023-02-28 16:25 ` bugzilla-daemon
2023-02-28 16:52 ` bugzilla-daemon
2023-02-28 16:55 ` bugzilla-daemon
2023-02-28 19:35 ` bugzilla-daemon
2023-03-01  9:20 ` bugzilla-daemon
2023-03-01 15:26 ` bugzilla-daemon
2023-03-01 15:39 ` bugzilla-daemon [this message]
2023-03-01 15:55 ` bugzilla-daemon
2023-03-01 16:07 ` bugzilla-daemon
2023-03-01 20:27 ` 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-217089-208809-Mdum6v1pXz@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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).