From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Martin Zaharinov <micron10@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Bug Report with kernel 6.3.5
Date: Fri, 30 Jun 2023 20:40:57 +0700 [thread overview]
Message-ID: <d5e0c840-f4ea-d44f-803c-fe97c481759b@gmail.com> (raw)
In-Reply-To: <F8555BEF-15B3-4CFF-8156-D5B1D6C24736@gmail.com>
On 6/30/23 19:42, Martin Zaharinov wrote:
> Hi Bagas,
>
> Close for now , if i collect new info will update here .
>
I repeat from my previous email:
Can you clearly describe your regression? And your nginx setup? And most
importantly, can you please bisect between v6.2 and v6.3 to find the
culprit? Can you also check the mainline?
Sorry if I have to cut down the context because you top-posted.
I didn't know what context you were referring to in that case.
Bye!
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-06-30 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 4:51 Bug Report with kernel 6.3.5 Martin Zaharinov
2023-06-04 5:42 ` Bagas Sanjaya
2023-06-29 11:29 ` Bagas Sanjaya
2023-06-30 12:42 ` Martin Zaharinov
2023-06-30 13:40 ` 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=d5e0c840-f4ea-d44f-803c-fe97c481759b@gmail.com \
--to=bagasdotme@gmail.com \
--cc=edumazet@google.com \
--cc=micron10@gmail.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).