From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] qed: Attention support patch series
Date: Tue, 01 Mar 2016 17:40:11 -0500 (EST) [thread overview]
Message-ID: <20160301.174011.1852663994206509014.davem@davemloft.net> (raw)
In-Reply-To: <1456655215-16345-1-git-send-email-Yuval.Mintz@qlogic.com>
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Sun, 28 Feb 2016 12:26:51 +0200
> Until now we've only enabled attention generation for the sake of
> management firmware indications [required for link notifications].
>
> This series enables [almost] all the attention sources of the HW,
> currently for the sake of logging information relating to issues
> experienced by HW. In future, infrastructure laid here would also be used
> for the sake of the recovery process.
>
> The first patch in the series is a semantic alignemnt of the code.
> The later 3 patches incremently create said infrastructure and enrich
> the logged information.
> Notice #3 contains quite a bit of structures [consisting of ~1K lines]
> that will eventually be removed and incorporated in the binary fw file.
Series applied, thanks.
prev parent reply other threads:[~2016-03-01 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:26 [PATCH net-next 0/4] qed: Attention support patch series Yuval Mintz
2016-02-28 10:26 ` [PATCH net-next 1/4] qed: Semantic refactoring of interrupt code Yuval Mintz
2016-02-28 10:26 ` [PATCH net-next 2/4] qed: Add support for HW attentions Yuval Mintz
2016-02-28 10:26 ` [PATCH net-next 3/4] qed: Print HW attention reasons Yuval Mintz
2016-02-28 10:26 ` [PATCH net-next 4/4] qed: Print additional HW attention info Yuval Mintz
2016-03-01 22:40 ` 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=20160301.174011.1852663994206509014.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Yuval.Mintz@qlogic.com \
--cc=netdev@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).