linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joe Perches <joe@perches.com>
Subject: Re: [PATCH] Add missing space at end of pr_fmt().
Date: Mon, 17 Oct 2016 12:08:48 -0700	[thread overview]
Message-ID: <580521C0.5070102@gmail.com> (raw)
In-Reply-To: <1476717010-3580-1-git-send-email-frowand.list@gmail.com>

On 10/17/16 08:10, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@am.sony.com>
> 
> Make pr_fmt() in fdt.c consistent with all other files in drivers/of/
> 
> Signed-off-by: Frank Rowand <frank.rowand@am.sony.com>

Rob,

Please ignore due to bad subject (as noted by Joe).  I will resend
with proper subject.

-Frank

      parent reply	other threads:[~2016-10-17 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 15:10 [PATCH] Add missing space at end of pr_fmt() frowand.list
2016-10-17 17:04 ` Joe Perches
2016-10-17 19:08 ` Frank Rowand [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=580521C0.5070102@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).