From: Jan Moskyto Matejka <mq@suse.cz>
To: Alexey Charkov <alchark@gmail.com>
Cc: David Laight <David.Laight@aculab.com>,
Roger Luethi <rl@hellgate.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: via-rhine: fix compiler warning
Date: Wed, 30 Apr 2014 11:50:15 +0200 [thread overview]
Message-ID: <20140430095015.GC24832@moskyto.dyndns.org> (raw)
In-Reply-To: <CABjd4YzRTPcy1nbhywuNLb0pz4gPVjhzegZJTc_g+_SVc1XJvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
> > So why not just:
> > revision = (unsigned long)match->data;
> > and add a comment that the 0x84 is the revision - #define ??
>
> There is no particular reason why it should be u32 now - this is a
> leftover from the previous iteration of code where revision was a
> separate property in DT (sized u32). It actually mirrors the
> respective field in struct pci_dev, which is u8 - don't see any issue
> defining it as unsigned long (and also changing the definition in
> struct rhine_private).
>
> The comment that it's the revision is right above the match table (cut
> off in the patch) :)
>
> Jan, would you prefer to adjust your patch, or shall I send another
> one to change rp->revision and friends to unsigned long?
I prefer you to make another patch, you obviously know more about this
driver. Also thanks for suggesting (void*)->(unsigned long), I didn't
know that these two are defined to have the same size (in kernel code).
--
Jan Matějka <mq@suse.cz>
SUSE Labs
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-30 9:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 17:36 [PATCH] net: via-rhine: fix compiler warning Jan Moskyto Matejka
2014-04-29 18:09 ` Alexey Charkov
2014-04-29 19:47 ` Jan Moskyto Matejka
2014-04-30 8:49 ` David Laight
2014-04-30 9:22 ` Alexey Charkov
2014-04-30 9:35 ` David Laight
2014-04-30 12:06 ` [PATCH] net: via-rhine: Fix compiler warning re: pointer casting on 64bit Alexey Charkov
2014-04-30 18:21 ` [PATCH] net: via-rhine: Drop revision property, use quirks instead Alexey Charkov
2014-05-02 19:56 ` David Miller
2014-05-03 12:40 ` [PATCH] net: via-rhine: Convert #ifdef USE_MMIO to a runtime flag Alexey Charkov
2014-05-05 19:37 ` David Miller
2014-05-01 9:30 ` [PATCH] net: via-rhine: Fix compiler warning re: pointer casting on 64bit David Laight
2014-05-01 11:33 ` Alexey Charkov
2014-04-30 9:50 ` Jan Moskyto Matejka [this message]
2014-04-30 9:57 ` [PATCH] net: via-rhine: fix compiler warning David Laight
2014-04-30 10:08 ` Jan Moskyto Matejka
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=20140430095015.GC24832@moskyto.dyndns.org \
--to=mq@suse.cz \
--cc=David.Laight@aculab.com \
--cc=alchark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
/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).