From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net, mst@redhat.com,
jasowang@redhat.com, arei.gonglei@huawei.com, harsh@chelsio.com,
giovanni.cabiddu@intel.com, salvatore.benedetto@intel.com
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/5] crypto: chelsio: pr_err() strings should end with newlines
Date: Mon, 25 Sep 2017 16:06:14 +0530 [thread overview]
Message-ID: <1506335776-1887-4-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1506335776-1887-1-git-send-email-arvind.yadav.cs@gmail.com>
pr_err() messages should terminated with a new-line to avoid
other messages being concatenated onto the end.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/crypto/chelsio/chcr_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/chelsio/chcr_core.c b/drivers/crypto/chelsio/chcr_core.c
index b6dd9cb..32618bf 100644
--- a/drivers/crypto/chelsio/chcr_core.c
+++ b/drivers/crypto/chelsio/chcr_core.c
@@ -224,7 +224,7 @@ static int chcr_uld_state_change(void *handle, enum cxgb4_state state)
static int __init chcr_crypto_init(void)
{
if (cxgb4_register_uld(CXGB4_ULD_CRYPTO, &chcr_uld_info))
- pr_err("ULD register fail: No chcr crypto support in cxgb4");
+ pr_err("ULD register fail: No chcr crypto support in cxgb4\n");
return 0;
}
--
1.9.1
next prev parent reply other threads:[~2017-09-25 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 10:36 [PATCH 0/5] crypto " Arvind Yadav
2017-09-25 10:36 ` [PATCH 1/5] crypto: omap-aes: " Arvind Yadav
2017-09-25 10:36 ` [PATCH 2/5] crypto: virtio: " Arvind Yadav
2017-09-25 10:36 ` Arvind Yadav [this message]
2017-09-25 10:36 ` [PATCH 4/5] crypto: qat: " Arvind Yadav
2017-09-25 10:36 ` [PATCH 5/5] crypto: bcm: " Arvind Yadav
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=1506335776-1887-4-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=giovanni.cabiddu@intel.com \
--cc=harsh@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=salvatore.benedetto@intel.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
all inboxes | Powered by JetHome®