From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: SATA ACPI SECURITY FREEZE LOCK (regression?)
Date: Thu, 16 May 2024 18:16:36 +0700 [thread overview]
Message-ID: <ZkXrFDwHS1a5pTnx@archie.me> (raw)
In-Reply-To: <d4caa0a0-2487-493c-a498-c6eca7483fde@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Thu, May 16, 2024 at 12:19:24PM +0200, Thorsten Leemhuis wrote:
> On 16.05.24 12:07, Bagas Sanjaya wrote:
> > On 5/16/24 16:56, Linux regression tracking (Thorsten Leemhuis) wrote:
> >> On 14.05.24 07:18, Bagas Sanjaya wrote:
> >>>
> >>> doru iorgulescu <doru.iorgulescu1@gmail.com> dumped repeated SATA error
> >>> messages on Bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=218832):
> >>
> >> Thx. I wonder if this is a problem at all. Acted in bugzilla for now.
> >>
> >> BTW: you did not reply to my question yesterday: why did you start for
> >> forwarding bugzilla tickets yourself again? I thought we agreed to let
> >> me handle that.
> >
> > I'm just wondering there and see what bugs I can forward to mailing lists
> > (of course with relevant maintainers Cc'ed).
>
> Please leave that to me for now, as we agreed on a while ago. We tried
> that already and that made some people upset and annoyed about
> regression tracking, which I really want to avoid.
>
> If you are unhappy with how I handle things, just tell me.
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-05-16 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZkL0EIESAleNhVqr@archie.me>
[not found] ` <ef803d3c-14c3-47ef-91d7-4ca498519bf0@leemhuis.info>
2024-05-16 10:07 ` SATA ACPI SECURITY FREEZE LOCK (regression?) Bagas Sanjaya
2024-05-16 10:19 ` Thorsten Leemhuis
2024-05-16 11:16 ` Bagas Sanjaya [this message]
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=ZkXrFDwHS1a5pTnx@archie.me \
--to=bagasdotme@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).