From: Greg KH <gregkh@linuxfoundation.org>
To: Marcus Wolf <marcus.wolf@wolf-entwicklungen.de>
Cc: Marcus Wolf <linux@wolf-entwicklungen.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH] staging: pi433: Make rf69_set_dc_cut_off_frequency_intern static
Date: Sat, 2 Dec 2017 16:10:40 +0000 [thread overview]
Message-ID: <20171202161040.GB7067@kroah.com> (raw)
In-Reply-To: <c5ce8b67-9246-ad36-c6b9-be3242fda5f6@wolf-entwicklungen.de>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Sat, Dec 02, 2017 at 06:01:59PM +0200, Marcus Wolf wrote:
> Hi!
>
> I am sorry :-/
>
> Can you recover, or do I need to resend?
I do not hand-edit patches, otherwise it would be impossible for me to
keep up with the review workload...
Do what I said earlier, fix all of these, take the time, verify they are
correct and in the correct format, and then send a patch series.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-02 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 15:20 [PATCH] staging: pi433: Make rf69_set_dc_cut_off_frequency_intern static Marcus Wolf
2017-12-02 15:56 ` Greg KH
2017-12-02 16:01 ` Marcus Wolf
2017-12-02 16:10 ` Greg KH [this message]
2017-12-02 16:46 ` Joe Perches
2017-12-02 17:15 ` Marcus Wolf
2017-12-02 18:05 ` Joe Perches
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=20171202161040.GB7067@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@wolf-entwicklungen.de \
--cc=marcus.wolf@wolf-entwicklungen.de \
/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