From: David Miller <davem@davemloft.net>
To: tlfalcon@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net v1 2/2] ibmvnic: Fix missing brackets in init_sub_crq_irqs
Date: Sat, 29 Oct 2016 17:19:09 -0400 (EDT) [thread overview]
Message-ID: <20161029.171909.1390809298638055569.davem@davemloft.net> (raw)
In-Reply-To: <1477589332-513-2-git-send-email-tlfalcon@linux.vnet.ibm.com>
From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Date: Thu, 27 Oct 2016 12:28:52 -0500
> Signed-off-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
> ---
> v1: caught by kbuild bot with -Wmisleading-indentation after
> after submitting previous patch
Applied.
next prev parent reply other threads:[~2016-10-29 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 17:28 [PATCH net v2 1/2] ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context Thomas Falcon
2016-10-27 17:28 ` [PATCH net v1 2/2] ibmvnic: Fix missing brackets in init_sub_crq_irqs Thomas Falcon
2016-10-29 21:19 ` David Miller [this message]
2016-10-29 21:19 ` [PATCH net v2 1/2] ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context David Miller
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=20161029.171909.1390809298638055569.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tlfalcon@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).