From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: Yuval.Mintz@cavium.com, ariel.elior@cavium.com,
everest-linux-l2@cavium.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bnx2x: fix spelling mistake in macros HW_INTERRUT_ASSERT_SET_*
Date: Tue, 04 Apr 2017 10:05:01 -0700 (PDT) [thread overview]
Message-ID: <20170404.100501.1641679451321837920.davem@davemloft.net> (raw)
In-Reply-To: <20170403101910.27480-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Mon, 3 Apr 2017 11:19:10 +0100
> From: Colin Ian King <colin.king@canonical.com>
>
> Trival fix, rename HW_INTERRUT_ASSERT_SET_* to HW_INTERRUPT_ASSERT_SET_*
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied.
prev parent reply other threads:[~2017-04-04 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:19 [PATCH] bnx2x: fix spelling mistake in macros HW_INTERRUT_ASSERT_SET_* Colin King
2017-04-04 13:27 ` Mintz, Yuval
2017-04-04 17:05 ` 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=20170404.100501.1641679451321837920.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Yuval.Mintz@cavium.com \
--cc=ariel.elior@cavium.com \
--cc=colin.king@canonical.com \
--cc=everest-linux-l2@cavium.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).