lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B0740B.5040006@garzik.org>
Date:	Mon, 11 Feb 2008 11:12:59 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Sreenivasa Honnur <Sreenivasa.Honnur@...erion.com>
CC:	netdev@...r.kernel.org, support@...erion.com
Subject: Re: [Patch 2.6.24 1/3]S2io: Support for vlan_rx_kill_vid entry point

Sreenivasa Honnur wrote:
> - Added s2io_vlan_rx_kill_vid entry point function for unregistering vlan.
> - Fix to aggregate vlan packets. IP offset is incremented by
>   4 bytes if the packet contains vlan header.
> - resubmit for 2.6.24 kernel
> 
> Signed-off-by: Surjit Reang <surjit.reang@...erion.com>
> Signed-off-by: Ramkrishna Vepa <ram.vepa@...erion.com>

it's difficult to sort through these patches, because they clash a bit 
with the kernel development model.

You always need to send against the latest kernel (generally davem's 
tree if it's during -rc bug fix cycle, or linus's otherwise).

Once the changes are in place, then email the commit ids or backported 
patches to stable@...nel.org for inclusion in an already-released kernel.

In this case, 2.6.24 was well on its way to being released weeks ago, 
when this set of patches was last resend (and then I subsequently 
screwed up, and apparently applied a wrong patch, as discussed)

So what we need are patches against the latest kernel 
(torvalds/linux-2.6.git), and after those are applied, email 
stable@...nel.org with whatever you want in 2.6.24.x.

	Jeff



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ