From: Atis Elsts <atis.elsts@gmail.com>
To: Eduardo Panisset <eduardo.panisset@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Reporting Bugs on This List
Date: Tue, 23 Mar 2010 21:22:30 +0200 [thread overview]
Message-ID: <7f9bf5711003231222u6198e589mba31ffaa50d9cc24@mail.gmail.com> (raw)
In-Reply-To: <b7b22e81003231205v38fa8774y81da6da5278c99a2@mail.gmail.com>
You need to submit patches in a proper format, and with [PATCH] in
subject line, so they get tracked automatically.
Reading this may be helpful: http://www.kernel.org/pub/linux/docs/lkml/#s1-10
Patches to netdev also need to apply clearly to net-2.6 (right?) Linux
kernel tree.
Also, be prepared that it may take much more time than one day until
someone reviews them.
On Tue, Mar 23, 2010 at 9:05 PM, Eduardo Panisset
<eduardo.panisset@gmail.com> wrote:
> Hi All,
>
> I have already reported two bugs on XFRM framework since yesterday.
> However my reports haven't been answered yet (I thought strange as
> this list is very active) and one of my questions simply disappeared
> even if its a simple plain text messages without offensive terms
> neither I think any other constraint.
> So I would like to know How would be the better way to report bugs on
> this list ?
>
> Thanks in advance,
> Eduardo Panisset.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
~Atis
next prev parent reply other threads:[~2010-03-23 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 19:05 Reporting Bugs on This List Eduardo Panisset
2010-03-23 19:22 ` Atis Elsts [this message]
2010-03-23 19:27 ` David Miller
2010-03-23 20:06 ` Eduardo Panisset
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=7f9bf5711003231222u6198e589mba31ffaa50d9cc24@mail.gmail.com \
--to=atis.elsts@gmail.com \
--cc=eduardo.panisset@gmail.com \
--cc=netdev@vger.kernel.org \
/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