linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nadim Almas <nadim.902@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, markh@compro.ne,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue
Date: Sun, 2 Oct 2016 22:11:12 +0530	[thread overview]
Message-ID: <CANQNnfHSTJp6E0-4xN+pw4SZLyNiGokKeY+zRPVEDAfaW0afjw@mail.gmail.com> (raw)
In-Reply-To: <20161002160917.GA22039@kroah.com>

So my first patch is correct?

On Sun, Oct 2, 2016 at 9:39 PM, Greg KH <gregkh@linuxfoundation.org> 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

  reply	other threads:[~2016-10-02 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 21:49 [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue Nadim Almas
2016-10-02 15:23 ` Greg KH
     [not found]   ` <CANQNnfGy50kygxezO3WEt+zHh5EH5RRgvKkJA0OFU7BFPMn5KQ@mail.gmail.com>
     [not found]     ` <20161002153937.GA21118@kroah.com>
2016-10-02 15:43       ` Fwd: " Nadim Almas
2016-10-02 16:09         ` Greg KH
2016-10-02 16:41           ` Nadim Almas [this message]
2016-10-02 17:49             ` 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=CANQNnfHSTJp6E0-4xN+pw4SZLyNiGokKeY+zRPVEDAfaW0afjw@mail.gmail.com \
    --to=nadim.902@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.ne \
    /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).