From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Rayagond Kokatanur <rayagond@vayavyalabs.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: which git repo to use for new network driver
Date: Sat, 24 May 2014 16:41:40 +0200 [thread overview]
Message-ID: <5380AFA4.1090708@hartkopp.net> (raw)
In-Reply-To: <CAJ3bTp5CsoWPmpQQ90o5M7DFQR_WZ3o5XkeVDN3aQMJKBr7kbA@mail.gmail.com>
On 24.05.2014 16:37, Rayagond Kokatanur wrote:
> Hi All,
>
> Which git repo should be used for developing new network driver,
> net-next.git or net.git.
New drivers and features always go via net-next.
The net-tree is just for fixes.
If you have e.g. a new wireless/bluetooth/CAN driver there's a
wireless/bluetooth/CAN mailing list to post to alternatively.
Regards,
Oliver
next prev parent reply other threads:[~2014-05-24 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 14:37 which git repo to use for new network driver Rayagond Kokatanur
2014-05-24 14:41 ` Oliver Hartkopp [this message]
2014-05-24 14:45 ` Rayagond Kokatanur
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=5380AFA4.1090708@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=netdev@vger.kernel.org \
--cc=rayagond@vayavyalabs.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;
as well as URLs for NNTP newsgroup(s).