From: max attems <janitor@sternwelten.at>
To: Jay Bourque <kernel@uranium235.org>,
kernel-janitors@lists.osdl.org, netdev@oss.sgi.com
Subject: Re: [Kernel-janitors] ip_gre.c: update last_rx after netif_rx
Date: Mon, 23 Aug 2004 22:36:40 +0200 [thread overview]
Message-ID: <20040823203640.GF1805@stro.at> (raw)
In-Reply-To: <20040821083639.GA1827@stro.at>
hello jay,
On Sat, 21 Aug 2004, maximilian attems wrote:
> On Sat, 14 Aug 2004, Jay Bourque wrote:
>
> > Fix to update last_rx after netif_rx
> > This is my first patch so I'd appreciate any feedback.
> >
> > -Jay
..
> i presume that this task is outdated,
well nobody is really interested in aboves issue,
thanks for bringing up that old dust,
task removed from kernel janitor TODO.
please choose another item of the kj TODO list?
happy to read you soon.
--
maks
kernel janitor http://janitor.kernelnewbies.org/
prev parent reply other threads:[~2004-08-23 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <411E62D3.8070808@uranium235.org>
2004-08-21 8:36 ` [Kernel-janitors] ip_gre.c: update last_rx after netif_rx maximilian attems
2004-08-23 20:36 ` max attems [this message]
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=20040823203640.GF1805@stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@lists.osdl.org \
--cc=kernel@uranium235.org \
--cc=netdev@oss.sgi.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).