From: Borislav Petkov <bp@alien8.de>
To: vectorflaredesigns@gmail.com, Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 212379] AMD GPIO chip IRQs stops working (ELN4690, WCOM51C7, BMA250E)
Date: Tue, 27 Apr 2021 00:04:01 +0200 [thread overview]
Message-ID: <YIc40YXZh4plkhnc@zn.tnic> (raw)
In-Reply-To: <bug-212379-6385-VMOjMpWM97@https.bugzilla.kernel.org/>
Switching to mail...
On Mon, Apr 26, 2021 at 09:04:38PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=212379
>
> --- Comment #15 from Austin Kilgore (vectorflaredesigns@gmail.com) ---
> Is this ever going to get looked at?
>
> Did I need to @ mention someone? Honestly asking since I don't know what to do.
> I don't even know who needs to be told to take a look at this.
>
> Like I said, if this bug report is lacking information just let me know and
> I'll test, check, or upload whatever is needed. It's really important to me
> that this gets fixed.
>
> --
Grepping through the tree, "amd_gpio" sounds like
drivers/pinctrl/pinctrl-amd.c so maybe Linus might have an idea, CCed.
@Linus, the bugzilla entry has some more info on what happens.
@Austin: in the future, please do not CC everyone including the
postmaster on your bug. Now you're mass-spamming 50+ people
unnecessarily.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next parent reply other threads:[~2021-04-26 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-212379-6385@https.bugzilla.kernel.org/>
[not found] ` <bug-212379-6385-VMOjMpWM97@https.bugzilla.kernel.org/>
2021-04-26 22:04 ` Borislav Petkov [this message]
2021-04-27 14:10 ` [Bug 212379] AMD GPIO chip IRQs stops working (ELN4690, WCOM51C7, BMA250E) Andy Shevchenko
2021-04-27 14:25 ` Andy Shevchenko
2021-04-27 23:42 ` Daniel Drake
2021-04-29 14:31 ` Linus Walleij
2021-04-29 14:58 ` Borislav Petkov
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=YIc40YXZh4plkhnc@zn.tnic \
--to=bp@alien8.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vectorflaredesigns@gmail.com \
/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