From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Subject: Re: How to start with a Marvell driver (non-USB, non-OLPC)
Date: Thu, 15 Feb 2007 09:40:49 +0100 [thread overview]
Message-ID: <200702150940.49306.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <200702090858.26294.hs4233@mail.mn-solutions.de>
Okay, I got encouraging replies to my initial mail. Later I
produced some patches for discussion and posted them into
libertas-dev and marvell8385-devel@linuxtogo.org.
But besides "please make a git repository" no one really cared
(about the patches --- there were other reactions). No patch has
been commented, ridiculed or applied.
If someone is interested, the patches are at
http://projects.linuxtogo.org/plugins/scmsvn/viewcvs.php/trunk/patches/?root=marvell8385
I consider
remove-unused-var.patch
remove-boot-command-define.patch
rename-functions.patch
remove-libertas-sbi-get-priv.patch
as applyable to libertas-2.6, the others are work-in-progress.
I'm now in the process to create a git repository at
infradead.org, maybe this can help the process. However, I don't
have any idea what I can do if I pushed a changeset to infradead
and later learn that this is crap. Can I rebase the HEAD of a
remote git repository?
prev parent reply other threads:[~2007-02-15 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 7:58 How to start with a Marvell driver (non-USB, non-OLPC) Holger Schurig
2007-02-09 12:35 ` John W. Linville
2007-02-09 12:49 ` Dan Williams
2007-02-09 14:24 ` Holger Schurig
2007-02-09 15:49 ` Dan Williams
2007-02-15 8:40 ` Holger Schurig [this message]
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=200702150940.49306.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).