From: Greg KH <gregkh@linuxfoundation.org>
To: feas <waltfeasel@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Patch procedure
Date: Tue, 15 Nov 2016 08:21:46 +0100 [thread overview]
Message-ID: <20161115072146.GC26760@kroah.com> (raw)
In-Reply-To: <201611141716.uAEHG8Wk001542@debian-laptop.lan>
On Mon, Nov 14, 2016 at 12:16:08PM -0500, feas wrote:
> Here is how I am going about making the patches. It is basically
> what I have picked up from kernel newbies among other sites
> and videos on making patches. I would be greatful for any
> pointers on what seems to be the problem(s) with why it does
> not produce a proper patch.
<snip>
Honestly, it's not our job to review someone's patch creation
proceedures and notes as everyone does it differently. We will be glad
to review your patches that you create.
I think the review that I previously provided should be sufficient to
start with. Again, send a short patch series to verify this, do not
send 100+ patches without getting feedback on them.
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-15 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 17:16 Patch procedure feas
2016-11-15 7:21 ` Greg KH [this message]
2016-11-15 8:55 ` Ioana Ciornei
2016-11-16 7:16 ` Walt Feasel
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=20161115072146.GC26760@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=waltfeasel@gmail.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