From: Greg KH <greg@kroah.com>
To: Nick Fox <fox.nicholas.j@gmail.com>
Cc: arve@android.com, riandrews@android.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: android: ion: Change argument to kmalloc (checkpatch)
Date: Wed, 23 Aug 2017 16:18:00 -0700 [thread overview]
Message-ID: <20170823231800.GE5193@kroah.com> (raw)
In-Reply-To: <CAAmVuH--a1Z0BmTAjvR5O-zobwGsVCQ+BqBZ8Wunsc0SY5W4Dw@mail.gmail.com>
On Wed, Aug 23, 2017 at 12:48:29PM -0400, Nick Fox wrote:
> Apologies for the spam, but I think my last reply got rejected by Google for
> some reason and didn't get delivered to the linux-kernel mailing list. My
> original reply is below:
You can not send html email to vger.kernel.org, it will be rejected,
please fix up your email client. Also please do not top-post on mailing
lists:
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
> "Sorry about that--I'm brand new to contributing and got mixed up about which
> tree to use. Just so I'm understanding correctly, https://git.kernel.org/pub/
> scm/linux/kernel/git/next/linux-next.git/ is the tree I should be using to work
> on staging drivers?
It is the tree you should be using to do any new kernel development on,
but if you specifically want to work on staging drivers, the staging.git
tree on git.kernel.org is the place to work off of, specifically the
staging-next branch there.
hope this helps,
greg k-h
next prev parent reply other threads:[~2017-08-23 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 1:04 [PATCH] drivers: staging: android: Fix style/formatting issues Nick Fox
2017-08-23 1:38 ` Greg KH
2017-08-23 2:55 ` [PATCH 1/2] staging: android: ion: Remove extra line (checkpatch) Nick Fox
2017-08-23 2:55 ` [PATCH 2/2] staging: android: ion: Change argument to kmalloc (checkpatch) Nick Fox
2017-08-23 5:38 ` Greg KH
[not found] ` <CAAmVuH--a1Z0BmTAjvR5O-zobwGsVCQ+BqBZ8Wunsc0SY5W4Dw@mail.gmail.com>
2017-08-23 23:18 ` Greg KH [this message]
2017-08-23 5:38 ` [PATCH 1/2] staging: android: ion: Remove extra line (checkpatch) Greg KH
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=20170823231800.GE5193@kroah.com \
--to=greg@kroah.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=fox.nicholas.j@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
/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