From: Forest Bond <forest@alittletooquiet.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Greg KH <greg@kroah.com>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Marcel Holtmann <marcel@holtmann.org>,
linux-wireless@vger.kernel.org, Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] Add vt6656 driver to drivers/staging.
Date: Fri, 24 Apr 2009 10:54:32 -0400 [thread overview]
Message-ID: <20090424145432.GK2830@storm.local.network> (raw)
In-Reply-To: <49F1D036.6080607@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]
Hi,
On Fri, Apr 24, 2009 at 09:44:06AM -0500, Larry Finger wrote:
> Forest Bond wrote:
> >
> > The following git repository has a vt6655 branch and a vt6656 branch:
> >
> > http://www.alittletooquiet.net/media/code/vt665x.git
> >
> > The vt6655 branch contains pretty much all of the work I'll likely be able to do
> > for that driver. The vt6656 branch needs more work. I've not gone farther than
> > build-testing either, at this point.
>
> It would be a little easier for looking at the code if both vt6655 and vt6656
> directories were in the same branch of the git repo, but it's not a big deal.
>
> > As I've mentioned before, some of this kind of work is really a bit outside my
> > usual domain, so if you do look at it, I'd appreciate feedback.
>
> There are a number of warnings when compiling the vt6655 driver on x86_64
> architecture that arise from pointers having 64 bits while integers have 32
> bits. I think the warnings will not cause any problems.
I'll have a closer look at the warnings.
> There is, however, one error, namely:
>
> CC [M] drivers/staging/vt6655/device_main.o
> drivers/staging/vt6655/device_main.c:347: error: initializer element is not constant
> drivers/staging/vt6655/device_main.c:347: error: (near initialization for
> ‘device_id_table[0].driver_data’)
Hm, didn't see this on my system. Not sure why. Thanks for the patch.
> Driver vt6656 also does not build, but that does not seem to be 64-bit related.
> If it builds on your system, let me know and I'll send you the error messages.
No, I haven't gotten that in a good state yet.
> I didn't look that thoroughly at the code, but I did notice one thing. The
> constructions like "#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,20)" are in the
> code so that it can build on a number of different kernels. Once it is in
> staging, it only has to build on the current kernel and you can trim out those
> conditionals.
Right, my intention was to look at those once the major build issues were sorted
out.
Were you able to look over my changes for net device private data accesses in
the vt6655 driver? That is what I'm most concerned about.
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-04-24 14:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 10:52 [PATCH] Add vt6656 driver to drivers/staging Forest Bond
2009-04-14 11:07 ` Johannes Berg
2009-04-14 11:39 ` Forest Bond
2009-04-14 11:48 ` Johannes Berg
2009-04-14 12:28 ` Marcel Holtmann
2009-04-14 12:43 ` Johannes Berg
2009-04-14 13:02 ` John W. Linville
2009-04-14 14:19 ` Forest Bond
2009-04-15 1:10 ` Greg KH
2009-04-15 1:51 ` Forest Bond
2009-04-19 17:09 ` Forest Bond
2009-04-19 19:52 ` Larry Finger
2009-04-19 20:01 ` Forest Bond
2009-04-19 22:32 ` Greg KH
2009-04-24 11:03 ` Forest Bond
2009-04-24 14:44 ` Larry Finger
2009-04-24 14:54 ` Forest Bond [this message]
2009-04-24 22:58 ` Greg KH
2009-04-25 0:08 ` Forest Bond
2009-04-25 0:14 ` Greg KH
2009-04-25 14:31 ` [PATCH 2/8] Add includes to drivers/staging/vt6655 Forest Bond
2009-04-25 14:31 ` [PATCH 3/8] Integrate drivers/staging/vt6655 into build system Forest Bond
2009-04-25 14:32 ` [PATCH 4/8] Add necessary EXTRA_CFLAGS to drivers/staging/vt6655/Makefile Forest Bond
2009-04-25 14:32 ` [PATCH 5/8] Build vt6655.ko, not viawget.ko Forest Bond
2009-04-25 14:32 ` [PATCH 6/8] drivers/staging/vt6655/device_main.c: Drop obsolete fsuid/fsgid accesses Forest Bond
2009-04-25 14:32 ` [PATCH 7/8] vt6655: Replace net_device->priv accesses with netdev_priv calls Forest Bond
2009-05-01 0:03 ` Forest Bond
2009-04-25 14:32 ` [PATCH 8/8] vt6655: Remove LINUX_VERSION_CODE preprocessor conditionals Forest Bond
2009-04-15 15:43 ` [PATCH] Add vt6656 driver to drivers/staging Dan Williams
2009-04-16 2:51 ` Greg KH
2009-04-15 13:19 ` John W. Linville
2009-04-14 14:52 ` Forest Bond
[not found] ` <18916.37868.64939.574249@gargle.gargle.HOWL>
2009-04-14 15:26 ` John W. Linville
2009-06-01 16:35 ` Gábor Stefanik
2009-06-01 16:52 ` Forest Bond
2009-06-08 17:08 ` Olivier Blin
2009-06-08 17:45 ` Forest Bond
2009-06-08 18:01 ` Olivier Blin
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 19:16 Xose Vazquez Perez
2009-04-15 21:21 ` Greg KH
2009-04-16 5:58 ` Kalle Valo
2009-04-16 8:39 ` Max Filippov
2009-04-16 8:47 ` Kalle Valo
2009-04-16 9:14 ` Max Filippov
2009-04-16 9:52 ` Kalle Valo
2009-04-18 21:18 ` Ivo van Doorn
2009-04-20 13:59 ` John W. Linville
2009-04-21 10:30 ` Ivo Van Doorn
2009-04-21 12:42 ` Ivo Van Doorn
2009-04-21 13:53 ` John W. Linville
2009-04-21 13:52 ` John W. Linville
[not found] <20090414024610.GA3924@storm.local.network>
2009-04-14 2:53 ` Greg KH
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=20090424145432.GK2830@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.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).