From: Dan Carpenter <dan.carpenter@oracle.com>
To: Giridhar Prasath R <cristianoprasath@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433 line over 80 characters in multiple places
Date: Mon, 5 Aug 2019 17:36:42 +0300 [thread overview]
Message-ID: <20190805143642.GD1974@kadam> (raw)
In-Reply-To: <20190805000248.4902-1-cristianoprasath@gmail.com>
The subject needs a colon after "pi433:" but also this change isn't
really an improvement so far as readability goes.
regards,
dan carpenter
next prev parent reply other threads:[~2019-08-05 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 0:02 [PATCH] staging: pi433 line over 80 characters in multiple places Giridhar Prasath R
2019-08-05 14:36 ` Dan Carpenter [this message]
2019-08-05 15:03 ` Greg Kroah-Hartman
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=20190805143642.GD1974@kadam \
--to=dan.carpenter@oracle.com \
--cc=cristianoprasath@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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).