Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755407AbcKOHVh (ORCPT <rfc822;w@1wt.eu>);
        Tue, 15 Nov 2016 02:21:37 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:48974 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751668AbcKOHVg (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 15 Nov 2016 02:21:36 -0500
Date: Tue, 15 Nov 2016 08:21:46 +0100
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
Message-ID: <20161115072146.GC26760@kroah.com>
References: <201611141716.uAEHG8Wk001542@debian-laptop.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201611141716.uAEHG8Wk001542@debian-laptop.lan>
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 730
Lines: 20

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