From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: Support for Iomega iConnect
Date: Fri, 30 Mar 2012 23:30:49 +0100 [thread overview]
Message-ID: <201203302330.49834.linux@baker-net.org.uk> (raw)
Hi,
Is anyone aware of any technical reason why support for the Iomega iConnect is
not included in the mainline kernel (e.g. there are significant changes
happening in the area of the Kirkwood CPUs that mean now isn't a good time to
include it). There are several versions floating around the internet but as far
as I can see the only mention of the iConnect on this list is Russell saying
he will remove it from mach types soon as there is no mainline support for it.
Based upon work that Iomega posted to the open source code area on their web
site and code that was submitted to OpenWRT with a sign off line from Wojciech
Dubowik, I have patched support into the 3.2.11 kernel. If there is no
objection in principle to inclusion then I will rebase the patch and submit
it.
Is Linus' git repository still the preferred baseline for linux-arm patches?
Regards
Adam Baker
next reply other threads:[~2012-03-30 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 22:30 Adam Baker [this message]
2012-03-30 23:24 ` Support for Iomega iConnect Jason Cooper
2012-03-31 18:27 ` Jason Cooper
2012-04-02 9:20 ` Arnaud Patard (Rtp)
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=201203302330.49834.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).