Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751634AbcJBQls (ORCPT ); Sun, 2 Oct 2016 12:41:48 -0400 Received: from mail-io0-f180.google.com ([209.85.223.180]:35234 "EHLO mail-io0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750927AbcJBQlr (ORCPT ); Sun, 2 Oct 2016 12:41:47 -0400 MIME-Version: 1.0 In-Reply-To: <20161002160917.GA22039@kroah.com> References: <20160930214912.GA6932@gmail.com> <20161002152355.GB32091@kroah.com> <20161002153937.GA21118@kroah.com> <20161002160917.GA22039@kroah.com> From: Nadim Almas Date: Sun, 2 Oct 2016 22:11:12 +0530 Message-ID: Subject: Re: Fwd: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue To: Greg KH Cc: devel@driverdev.osuosl.org, markh@compro.ne, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 507 Lines: 14 So my first patch is correct? On Sun, Oct 2, 2016 at 9:39 PM, Greg KH wrote: > On Sun, Oct 02, 2016 at 09:13:32PM +0530, Nadim Almas wrote: >> sir i am new in linux kernel hacking so I just want to start with >> something very simple ,so for sake of simplicity and learning I fixed >> only one of these warning > > That's great, but next time try to do a little bit more, just fixing a > single warning like that isn't all that useful overall, right? > > thanks, > > greg k-h