From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Kees Cook <keescook@chromium.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
M Chetan Kumar <m.chetan.kumar@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Klink <flokli@flokli.de>
Subject: Re: Fwd: iosm: detected field-spanning write for XMM7360
Date: Tue, 20 Jun 2023 19:25:50 +0700 [thread overview]
Message-ID: <4ce78431-d397-a7a5-cb3d-905c61d47cc4@gmail.com> (raw)
In-Reply-To: <0826b484-8bbc-d58f-2caf-7015bd30f827@leemhuis.info>
On 6/20/23 16:12, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 20.06.23 10:44, Bagas Sanjaya wrote:
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>
> Bagas, you can't know this, as we didn't have such a sitaution until
> now, so FYI:
>
> Please don't add "field-spanning write" warnings to the regression
> tracking, that's not worth the trouble (at least for the time beeing).
> Just forward them to Kees, who might look into them if the developer in
> question doesn't care. That was the approach we agreed on here:
>
> https://lore.kernel.org/all/f1ca3cea-01ae-998a-2aa8-c3e40cf46975@leemhuis.info/
>
OK, thanks for another tip! I always forgot to double-check everywhere...
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-06-20 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 8:44 Fwd: iosm: detected field-spanning write for XMM7360 Bagas Sanjaya
2023-06-20 9:12 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 12:25 ` Bagas Sanjaya [this message]
2023-06-20 19:32 ` Kees Cook
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=4ce78431-d397-a7a5-cb3d-905c61d47cc4@gmail.com \
--to=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=flokli@flokli.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.chetan.kumar@linux.intel.com \
--cc=netdev@vger.kernel.org \
--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 NNTP newsgroup(s).