From: Jeff Garzik <jeff@garzik.org>
To: Sreenivasa Honnur <Sreenivasa.Honnur@neterion.com>
Cc: netdev@vger.kernel.org, support@neterion.com
Subject: Re: [Patch 2.6.24 1/3]S2io: Support for vlan_rx_kill_vid entry point
Date: Mon, 11 Feb 2008 11:12:59 -0500 [thread overview]
Message-ID: <47B0740B.5040006@garzik.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10802061527330.18812-100000@guinness>
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@neterion.com>
> Signed-off-by: Ramkrishna Vepa <ram.vepa@neterion.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@kernel.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@kernel.org with whatever you want in 2.6.24.x.
Jeff
next prev parent reply other threads:[~2008-02-11 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 20:28 [Patch 2.6.24 1/3]S2io: Support for vlan_rx_kill_vid entry point Sreenivasa Honnur
2008-02-11 16:12 ` Jeff Garzik [this message]
2008-02-11 20:02 ` Ramkrishna Vepa
-- strict thread matches above, loose matches on Subject: below --
2008-01-24 18:13 Sreenivasa Honnur
2008-02-01 18:42 ` Jeff Garzik
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=47B0740B.5040006@garzik.org \
--to=jeff@garzik.org \
--cc=Sreenivasa.Honnur@neterion.com \
--cc=netdev@vger.kernel.org \
--cc=support@neterion.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).