From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: ravinandan.arakali@s2io.com, netdev@oss.sgi.com,
leonid.grossman@s2io.com, raghavendra.koushik@s2io.com,
rapuru.sriram@s2io.com
Subject: Re: Patch submission for S2io Xframe driver to 2.6 kernel
Date: Thu, 16 Sep 2004 20:07:35 -0700 [thread overview]
Message-ID: <20040916200735.57909f02.rddunlap@osdl.org> (raw)
In-Reply-To: <414A3562.2090803@pobox.com>
On Thu, 16 Sep 2004 20:52:50 -0400 Jeff Garzik wrote:
| Ravinandan Arakali wrote:
| > Jeff,
| > We tried it out with 2.6.7. Can you pls specify the kernel version
| > on which you tried and we will send a patch which works for that version.
| > We will also send a more detailed description of the changes along with
| > that.
For splitting it up :), e.g.:
- 1 patch could be for renaming only, no code/logic changes
(like TxCfg to tx_cfg); maybe including comments/whitespace changes;
- 1 could be to eliminate (most/all) typedefs
- 1 could be for errata/workarounds
- 1 could be for ethtool support (changes)
- 1 for NAPI support (changes)
- 1 for 2BUFF mode
etc...
Q1: why is this change needed?
static inline u64 readq(void *addr)
{
u64 ret = 0;
ret = readl(addr + 4);
- ret <<= 32;
- ret |= readl(addr);
+ (u64) ret <<= 32;
+ (u64) ret |= readl(addr);
|
| Always diff against the latest version of the kernel. You can find out
| the latest version by going to http://www.kernel.org/ You'll typically
| want the latest snapshot (preferably), or the latest pre-patch.
|
| Standard patch submission format is described at
| http://linux.yyz.us/patch-format.html and in
| Documentation/SubmittingPatches.
|
| When submitting a series of patches, it is normal patches to depend on
| preceding patches.
--
~Randy
next prev parent reply other threads:[~2004-09-17 3:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 0:19 Patch submission for S2io Xframe driver to 2.6 kernel Ravinandan Arakali
2004-08-14 4:27 ` TCP hardware assists Leonid Grossman
2004-08-21 6:21 ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
2004-08-21 23:43 ` Francois Romieu
2004-08-28 23:36 ` Jeff Garzik
2004-08-29 5:53 ` Leonid Grossman
2004-08-30 17:25 ` Ravinandan Arakali
2004-09-13 17:09 ` Ravinandan Arakali
2004-09-17 0:38 ` Jeff Garzik
2004-09-17 0:53 ` Ravinandan Arakali
2004-09-17 0:52 ` Jeff Garzik
2004-09-17 3:07 ` Randy.Dunlap [this message]
2004-09-28 0:42 ` Ravinandan Arakali
2004-09-28 3:54 ` Randy.Dunlap
2004-09-28 15:05 ` Jeff Garzik
2004-09-28 17:13 ` Ravinandan Arakali
2004-10-06 20:14 ` Ravinandan Arakali
2004-10-06 20:09 ` Jeff Garzik
2004-10-06 20:20 ` Francois Romieu
2004-10-06 22:52 ` Jeff Garzik
2004-10-07 1:04 ` [PATCH 2.6.9-rc2 1/8] S2io: cosmetic changes Ravinandan Arakali
2004-09-17 3:58 ` Patch submission for S2io Xframe driver to 2.6 kernel Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 22:45 Ravinandan Arakali
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=20040916200735.57909f02.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@s2io.com \
--cc=rapuru.sriram@s2io.com \
--cc=ravinandan.arakali@s2io.com \
/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).