From: Greg KH <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: beld zhang <beldzhang@gmail.com>, stable@vger.kernel.org
Subject: Re: Fwd: 6.1.30: thunderbolt: Clear registers properly when auto clear isn't in use cause call trace after resume
Date: Mon, 29 May 2023 08:26:36 +0100 [thread overview]
Message-ID: <2023052908-generous-nutrient-ab24@gregkh> (raw)
In-Reply-To: <ZHQK_ZyW3NW3JXdz@debian.me>
On Mon, May 29, 2023 at 09:16:29AM +0700, Bagas Sanjaya wrote:
> On Sun, May 28, 2023 at 08:02:35PM +0100, Greg KH wrote:
> > > sorry I have no idea how to fill a proper bug report at kernel
> > > bugzilla, hope these shared links work.
> > > btw I have no TB devices to test.
> > >
> > > dmesg:
> > > https://drive.google.com/file/d/1bUWnV7q2ziM4tdTzmuGiVuvEzaLcdfKm/view?usp=sharing
> > >
> > > config:
> > > https://drive.google.com/file/d/1It75_AV5tOzfkXXBAX5zAiZMoeJAe0Au/view?usp=sharing
> >
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
>
> Hi Greg,
>
> You confuse attaching bug artifacts (here dmesg and .config) with stable
> kernel patches. The reporter doesn't have any patches to help fixing
> this regression at the moment.
>
No, I was not confused, sending bug reports to this email address is not
going to help at all, so my bot was correct.
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-29 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 20:15 6.1.30: thunderbolt: Clear registers properly when auto clear isn't in use cause call trace after resume beld zhang
2023-05-27 23:48 ` Bagas Sanjaya
2023-05-28 12:55 ` Mario Limonciello
[not found] ` <CAG7aomVVJyDpKjpZ=k=+9qKY5+13eFjcGPEWZ0T0+NTNfZWDfA@mail.gmail.com>
2023-05-28 18:35 ` Fwd: " beld zhang
2023-05-28 19:02 ` Greg KH
2023-05-29 2:16 ` Bagas Sanjaya
2023-05-29 7:26 ` Greg KH [this message]
2023-05-29 2:21 ` Bagas Sanjaya
2023-05-29 3:23 ` beld zhang
2023-05-29 11:38 ` Mika Westerberg
2023-05-29 18:40 ` beld zhang
2023-05-30 5:41 ` Mika Westerberg
2023-05-30 4:12 ` Mario Limonciello
2023-05-30 4:27 ` beld zhang
2023-05-30 9:10 ` Bagas Sanjaya
2023-05-30 8:03 ` Mika Westerberg
2023-05-30 14:38 ` beld zhang
2023-05-31 7:41 ` Mika Westerberg
2023-08-31 9:20 ` Linux regression tracking #update (Thorsten Leemhuis)
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=2023052908-generous-nutrient-ab24@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=beldzhang@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.