From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: RF class driver
Date: Wed, 21 Sep 2016 09:43:01 +0200 [thread overview]
Message-ID: <20160921074301.GA32442@kroah.com> (raw)
In-Reply-To: <CAEwN+MCTPuCkbUAOXi2rE3-UNNQppCi6S2AsRpC_UA0YKcO2nw@mail.gmail.com>
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 Tue, Sep 20, 2016 at 06:15:46PM +0530, Raul Piper wrote:
> Tree,before that want to have a look at?example RF drivers - Sub Ghz
> Transcievers
I can not understand what you are saying here, please explain further.
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-21 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 12:32 RF class driver Raul Piper
2016-09-20 12:43 ` Greg KH
2016-09-20 12:45 ` Raul Piper
2016-09-21 7:43 ` Greg KH [this message]
2016-09-21 9:39 ` Raul Piper
2016-09-21 10:08 ` Greg KH
2016-09-21 12:43 ` Daniel.
2016-09-21 12:57 ` Hayward, Shaun
2016-09-21 13:05 ` Daniel.
2016-09-21 13:07 ` Daniel.
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=20160921074301.GA32442@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).