From: Luciano Coelho <luciano.coelho@intel.com>
To: Izzy Kulbe <kernel@unikorn.me>, Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: add device ID for Rivet Networks Killer Wireless-AC 1550
Date: Tue, 27 Mar 2018 15:37:34 +0300 [thread overview]
Message-ID: <1522154254.3786.269.camel@intel.com> (raw)
In-Reply-To: <2c826451177bbcb8fe033631dc7b87eb92f5e42d.camel@unikorn.me>
On Tue, 2018-03-27 at 14:03 +0200, Izzy Kulbe wrote:
> On Tue, 2018-03-27 at 14:48 +0300, Kalle Valo wrote:
> > Izzy Kulbe <kernel@unikorn.me> writes:
> >
> > > nvm the last message, attached the wrong file using the 9270
> > > instead of the 9260 firmware, which obviously wouldn't work.
> > > Here's the working patch:
> > >
> > >
> > > Add support for Rivet Networks Killer Wireless-AC 1550 chipset,
> > > which is using the Intel Wireless-AC 9260 chip
> > >
> > > Signed-off-by: Izzy Kulbe <kernel@unikorn.me>
> > >
> > > ---
> >
> > You should put the comment "nvm the last message..." under the "---
> > "
> > line so that git-am can ignore it.
>
> Sorry, still new to the whole process. should i just resend
> that message with the proper order?
Wait a bit. This ID looks strange, someone else reported this already
and it looked strange, with an incorrect subsystem vendor ID.
Can you run lspci like this and let us know the results?
lspci -nv -s 3b:00.0
--
Cheers,
Luca.
next prev parent reply other threads:[~2018-03-27 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 10:54 [PATCH] iwlwifi: add device ID for Rivet Networks Killer Wireless-AC 1550 Izzy Kulbe
2018-03-27 11:48 ` Kalle Valo
2018-03-27 12:03 ` Izzy Kulbe
2018-03-27 12:37 ` Luciano Coelho [this message]
2018-03-27 12:38 ` Luciano Coelho
2018-03-27 12:48 ` Izzy Kulbe
2018-03-27 13:10 ` Luciano Coelho
2018-03-27 14:09 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2018-03-27 10:43 Izzy Kulbe
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=1522154254.3786.269.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=kernel@unikorn.me \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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).