EHEA: Is there a size limit below 80K for patches?
Subsystems (2)
Hello,
we tried two times to send a patch set. In both cases the second (largest) patch got lost. The first one was a bit above 100k, the second one we tried was like 75K.
Any idea what might be the problem?
Thanks,
Jan-Bernd Themann
Quoted 6 lines · Jan-Bernd Themann
Hello,
we tried two times to send a patch set. In both cases the second (largest) patch got lost. The first one was a bit above 100k, the second one we tried was like 75K.
Any idea what might be the problem?
It might be size, or tripping a spam filter.
For a new driver, do the sane thing and just post a URL.
Jeff
well, now I'm confused...
2 People, two opinions....
Here's a URL for a complete tarball, "sharing" the download location with our other driver.
http://prdownloads.sourceforge.net/ibmehcad/ehea_EHEA_0002.tgz
We're waiting for a sourceforge project now since 9 days to put out a tgz, and it looks like many other people get upset right now by their response time.
So what's the "right"/preferred way to proceed?
Christop R.
Quoted 1 line
We're currently developing a new Ethernet device driver for a 10G IBM
chip
Quoted 5 lines
for System p. (ppc64)
A later version of the driver should end up in mainline kernel. How should we proceed to get first comments by the community? Either post this code as a patch to netdev or
yes
Quoted 1 line
put a full tarball on for example sourceforge?
nope.
Please read and observe: Documentation/SubmittingPatches and Section 3 of it, References, for other sources of expectations/requirements.
The -mm tree also contains Documentation/SubmitChecklist that you may find useful.
---
~Randy
Jeff Garzik <jeff@xxxxx> wrote on 08.06.2006 13:34:36:
Quoted 18 lines
Quoted 8 lines · Jan-Bernd Themann
Hello,
we tried two times to send a patch set. In both cases the second (largest) patch
got lost. The first one was a bit above 100k, the second one we tried was like 75K.Any idea what might be the problem?
It might be size, or tripping a spam filter.
For a new driver, do the sane thing and just post a URL.
Jeff
Quoted 8 lines · Christoph Raisch
well, now I'm confused...
2 People, two opinions....Here's a URL for a complete tarball, "sharing" the download location with our other driver.
http://prdownloads.sourceforge.net/ibmehcad/ehea_EHEA_0002.tgz
Quoted 5 lines
We're waiting for a sourceforge project now since 9 days to put out a tgz, and it looks like many other people get upset right now by their response time.
So what's the "right"/preferred way to proceed?
Patches and new drivers should always go to the mailing list...... except for the case where they are too big to be posted to the mailing list. For that special case, a URL to a patch should be posted.
Jeff