All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: dmitry.tarnyagin@lockless.no, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net caif: insert missing spaces in pr_* messages and unbreak multi-line strings
Date: Fri, 28 Oct 2016 13:47:47 -0400 (EDT)	[thread overview]
Message-ID: <20161028.134747.1907524803559536162.davem@davemloft.net> (raw)
In-Reply-To: <20161025111842.8110-1-colin.king@canonical.com>

From: Colin King <colin.king@canonical.com>
Date: Tue, 25 Oct 2016 12:18:42 +0100

> From: Colin Ian King <colin.king@canonical.com>
> 
> Some of the pr_* messages are missing spaces, so insert these and also
> unbreak multi-line literal strings in pr_* messages
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Applied.

      reply	other threads:[~2016-10-28 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 11:18 [PATCH] net caif: insert missing spaces in pr_* messages and unbreak multi-line strings Colin King
2016-10-28 17:47 ` 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=20161028.134747.1907524803559536162.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=colin.king@canonical.com \
    --cc=dmitry.tarnyagin@lockless.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.