From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: devel@driverdev.osuosl.org, gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues
Date: Sun, 4 Apr 2010 15:56:21 +0200 [thread overview]
Message-ID: <20100404135621.GA16351@lunn.ch> (raw)
In-Reply-To: <p2x506b70dc1004031845p81705070o325d93f839c80e9a@mail.gmail.com>
> Sorry about the conflict, thanks for redoing the changes. Where can I
> find the current and development branches? I want to avoid doing this
> mistake again in the future. Specially since I'm planning on doing
> some janitorial work on Staging for a while if it's OK with you guys.
> I see it as nice experience and practice while learning and getting
> ready for more valuable contributions :)
Sven has told you about how batman uses different repositories. You
can find some more information at:
http://www.open-mesh.org/wiki/UsingBatmanGit
When working on other staging drivers i suggest you work on either the
linux-next tree, or contact the driver maintainers and ask if they
have there own development tree. Staging drivers tend to be fast
moving. They change a lot. What is in the current release kernel,
which is effectively 3 months old, can be very different to the latest
development version. I've received many patches to things we have
fixed months ago and are either waiting in linux-next for the next
kernel release, or our in or development tree. I'm sure the same
applies to other drivers in staging.
Another option for interesting work to get involved in the kernel is
to ask GregKH if there is a staging driver which is not being actively
worked on. Some drivers just get dumped there and nobody spends the
time and effort needed to get them merged. After a while they get
thrown out of the staging. You could adopt such a driver, get hold of
the hardware and do the work needed to get it out of staging and into
the main tree.
Andrew
next prev parent reply other threads:[~2010-04-04 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <batman-adv>
[not found] ` <1270341625-28764-1-git-send-email-luisbg@ubuntu.com>
2010-04-04 1:12 ` [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues Sven Eckelmann
2010-04-04 1:24 ` [B.A.T.M.A.N.] [PATCHv2-maint] " Sven Eckelmann
2010-04-04 17:09 ` Marek Lindner
2010-04-04 17:51 ` Luis de Bethencourt
2010-04-04 1:44 ` [B.A.T.M.A.N.] [PATCHv2-trunk] " Sven Eckelmann
2010-04-04 2:48 ` Marek Lindner
2010-04-04 16:33 ` [B.A.T.M.A.N.] [PATCH] batctl: Parse allowed settings for sysfs without whitespace before newline Sven Eckelmann
2010-04-06 5:33 ` Marek Lindner
2010-04-04 1:45 ` [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues Luis de Bethencourt
2010-04-04 10:46 ` Sven Eckelmann
2010-04-04 11:10 ` Luis de Bethencourt
2010-04-04 11:30 ` Sven Eckelmann
2010-04-04 12:39 ` Luis de Bethencourt
2010-04-04 14:42 ` Marek Lindner
2010-04-04 15:02 ` Luis de Bethencourt
2010-04-04 15:14 ` Sven Eckelmann
2010-04-04 15:19 ` Luis de Bethencourt
2010-04-04 13:56 ` Andrew Lunn [this message]
2010-04-04 14:56 ` Luis de Bethencourt
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=20100404135621.GA16351@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox