All of lore.kernel.org
 help / color / mirror / Atom feed
From: govind <govindarajulu90@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Kevin Curtis <Kevin.Curtis@farsite.com>,
	"David S. Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: Updated FarSync driver
Date: Sat, 27 Jul 2013 20:39:38 +0000	[thread overview]
Message-ID: <51F42D3A.1070200@gmail.com> (raw)
In-Reply-To: <20130726234122.GH5585@mwanda>

On 07/27/2013 05:11 AM, Dan Carpenter wrote:
> On Fri, Jul 26, 2013 at 11:13:25AM +0100, Kevin Curtis wrote:
>> Hi David,
>>      I'd like to update the FarSync driver for our T-Series cards
>> in the latest Linux Kernel and I would also like to add a new
>> driver for our FarSync Flex USB device.
>>
>> Should I direct the patch to you?
>>
>
> Read Documentation/SubmittingPatches
> Use ./scripts/get_maintainer.pl to find who needs to be CC'd.

you can also go through

Write and Submit your first Linux kernel Patch - Greg KH 
https://www.youtube.com/watch?v=LLBrBBImJt4
Why I dont want your code - Greg KH https://www.youtube.com/watch?v=fMeH7wqOwXA

helped me a lot.

//govind

WARNING: multiple messages have this Message-ID (diff)
From: govind <govindarajulu90@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Kevin Curtis <Kevin.Curtis@farsite.com>,
	"David S. Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: Updated FarSync driver
Date: Sun, 28 Jul 2013 01:57:38 +0530	[thread overview]
Message-ID: <51F42D3A.1070200@gmail.com> (raw)
In-Reply-To: <20130726234122.GH5585@mwanda>

On 07/27/2013 05:11 AM, Dan Carpenter wrote:
> On Fri, Jul 26, 2013 at 11:13:25AM +0100, Kevin Curtis wrote:
>> Hi David,
>>      I'd like to update the FarSync driver for our T-Series cards
>> in the latest Linux Kernel and I would also like to add a new
>> driver for our FarSync Flex USB device.
>>
>> Should I direct the patch to you?
>>
>
> Read Documentation/SubmittingPatches
> Use ./scripts/get_maintainer.pl to find who needs to be CC'd.

you can also go through

Write and Submit your first Linux kernel Patch - Greg KH 
https://www.youtube.com/watch?v=LLBrBBImJt4
Why I dont want your code - Greg KH https://www.youtube.com/watch?v=fMeH7wqOwXA

helped me a lot.

//govind

  reply	other threads:[~2013-07-27 20:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  7:20 [patch] farsync: fix support for over 30 cards Dan Carpenter
2012-10-09  7:20 ` Dan Carpenter
2012-10-09 17:55 ` David Miller
2012-10-09 17:55   ` David Miller
2013-07-26 10:13 ` Updated FarSync driver Kevin Curtis
2013-07-26 10:13   ` Kevin Curtis
2013-07-26 23:41   ` Dan Carpenter
2013-07-26 23:41     ` Dan Carpenter
2013-07-27 20:27     ` govind [this message]
2013-07-27 20:39       ` govind
2013-07-29 11:10   ` Dan Carpenter
2013-07-29 11:42   ` Dan Carpenter
2013-07-29 12:58   ` Kevin Curtis
2013-07-31 13:55   ` Kevin Curtis
2013-07-31 14:50   ` Dan Carpenter
2013-08-30 20:53   ` Dan Carpenter
2013-08-30 21:05   ` Dan Carpenter

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=51F42D3A.1070200@gmail.com \
    --to=govindarajulu90@gmail.com \
    --cc=Kevin.Curtis@farsite.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.