From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Failed IRQ assignment for INT0002 on Braswell
Date: Thu, 23 Nov 2017 22:15:50 +0100 [thread overview]
Message-ID: <1518924.dC7gVaPWNF@natalenko.name> (raw)
In-Reply-To: <CAHp75VcfOYmOwsYgH0ri0ZDNSP_5gb0QyttBKUMuBHm1qxhkUw@mail.gmail.com>
On čtvrtek 23. listopadu 2017 22:08:29 CET Andy Shevchenko wrote:
> On Wed, Nov 22, 2017 at 8:13 PM, Oleksandr Natalenko
>
> <oleksandr@natalenko.name> wrote:
> > Hi, Hans.
> >
> > With this patch applied the warning is not emitted anymore with threadirqs
> > enabled, and relevant kthread (irq/9-INT0002) is created.
> >
> > Feel free to add Reported-by/Tested-by from me once you do a submission.
>
> First of all, please stop top-posting.
>
> Second, we are using patchwork which can automatically add tags based
> on given in followup emails.
> So, if you wish to see your tag in the commit message at the end,
> please, send a reply with
>
> Reported-by:
> Tested-by:
>
> tags.
>
> Thanks.
Right.
Reported-by: Oleksandr Natalenko <oleksandr@natalenko.name>
Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
next prev parent reply other threads:[~2017-11-23 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 22:35 Failed IRQ assignment for INT0002 on Braswell Oleksandr Natalenko
2017-11-22 10:48 ` Hans de Goede
2017-11-22 12:48 ` Oleksandr Natalenko
2017-11-22 15:50 ` Hans de Goede
2017-11-22 18:13 ` Oleksandr Natalenko
2017-11-23 21:08 ` Andy Shevchenko
2017-11-23 21:15 ` Oleksandr Natalenko [this message]
2017-11-23 21:22 ` Andy Shevchenko
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=1518924.dC7gVaPWNF@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=andy.shevchenko@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 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).