From: David Miller <davem@davemloft.net>
To: igor.russkikh@aquantia.com
Cc: netdev@vger.kernel.org, darcari@redhat.com, pavel.belous@aquantia.com
Subject: Re: [PATCH net 0/2] Aquantia various patches 2018-05
Date: Tue, 08 May 2018 00:07:02 -0400 (EDT) [thread overview]
Message-ID: <20180508.000702.1633660948937997965.davem@davemloft.net> (raw)
In-Reply-To: <cover.1525360773.git.igor.russkikh@aquantia.com>
From: Igor Russkikh <igor.russkikh@aquantia.com>
Date: Mon, 7 May 2018 16:10:37 +0300
> These are two patches covering issues found during test cycles:
>
> First is that driver should declare valid vlan_features
> Second fix is about correct allocation of MSI interrupts on some systems.
Series applied, thank you.
prev parent reply other threads:[~2018-05-08 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 13:10 [PATCH net 0/2] Aquantia various patches 2018-05 Igor Russkikh
2018-05-07 13:10 ` [PATCH net 1/2] net: aquantia: driver should correctly declare vlan_features bits Igor Russkikh
2018-05-07 13:10 ` [PATCH net 2/2] net: aquantia: Limit number of vectors to actually allocated irqs Igor Russkikh
2018-05-08 4:07 ` David Miller [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=20180508.000702.1633660948937997965.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=darcari@redhat.com \
--cc=igor.russkikh@aquantia.com \
--cc=netdev@vger.kernel.org \
--cc=pavel.belous@aquantia.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