netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Bizon <mbizon@freebox.fr>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] sctp: rfc conformance fixes
Date: Wed, 22 Oct 2008 07:32:09 +0200	[thread overview]
Message-ID: <1224653529.6597.40.camel@localhost.localdomain> (raw)
In-Reply-To: <200810221601.27588.jk@ozlabs.org>


On Wed, 2008-10-22 at 16:01 +1100, Jeremy Kerr wrote:

Hi Jeremy,

> That's correct - patchwork uses the content of the mail to determine
> if it contains a patch, not the subject.

Thanks for explaining.

I sent a patch sunday (using git-format-patch/git-send-email), and
patchwork seems to have missed it, I can't see it even with all filters
removed.

From:   Maxime Bizon <mbizon@freebox.fr>
To:     jgarzik@pobox.com
Cc:     linux-mips@linux-mips.org, netdev@vger.kernel.org, Maxime Bizon <mbizon@freebox.fr>
Message-Id: <1224382023-24388-1-git-send-email-mbizon@freebox.fr>
Subject: [PATCH/RFC v1 09/12] [MIPS] BCM63XX: Add integrated ethernet mac support.
Sender: netdev-owner@vger.kernel.org

Any idea ?

-- 
Maxime


  reply	other threads:[~2008-10-22  5:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  2:08 [PATCH] sctp: rfc conformance fixes Vlad Yasevich
2008-10-22  2:08 ` [PATCH 1/4] sctp: Drop ICMP packet too big message with MTU larger than current PMTU Vlad Yasevich
2008-10-23  8:00   ` David Miller
2008-10-22  2:08 ` [PATCH 2/4] sctp: Add check for the TSN field of the SHUTDOWN chunk Vlad Yasevich
2008-10-23  8:00   ` David Miller
2008-10-22  2:08 ` [PATCH 3/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN-PENDING state Vlad Yasevich
2008-10-23  8:00   ` David Miller
2008-10-22  2:08 ` [PATCH 4/4] sctp: Fix to handle SHUTDOWN in SHUTDOWN_RECEIVED state Vlad Yasevich
2008-10-23  8:01   ` David Miller
2008-10-22  4:05 ` [PATCH] sctp: rfc conformance fixes David Miller
2008-10-22  4:44   ` Maxime Bizon
2008-10-22  4:47     ` David Miller
2008-10-22  5:01       ` Jeremy Kerr
2008-10-22  5:32         ` Maxime Bizon [this message]
2008-10-22  5:35           ` Jeremy Kerr
2008-10-22  6:02             ` Maxime Bizon
2008-10-22 13:03             ` Vlad Yasevich
2008-10-22 22:54               ` Jeremy Kerr
2008-10-22 23:46                 ` David Miller
2008-10-22 23:48                   ` David Miller
2008-10-23  1:24                     ` Vlad Yasevich
2008-10-23  4:06                       ` David Miller
2008-10-23  6:15                         ` Simon Horman
2008-10-23  8:06                           ` David Miller
     [not found]                 ` <48FFBA06.50609@hp.com>
2008-10-23  0:43                   ` Jeremy Kerr
2008-10-23  3:34                     ` Jeremy Kerr
2008-10-23  4:11                       ` David Miller
2008-10-23  5:47                         ` Benjamin Herrenschmidt
2008-10-23  5:54                           ` Jeremy Kerr
2008-10-22  6:12           ` David Miller
2008-10-22 16:48             ` Maxime Bizon
2008-10-22 21:10               ` David Miller
2008-10-22 23:42   ` Vlad Yasevich
2008-10-23  4:12     ` David Miller

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=1224653529.6597.40.camel@localhost.localdomain \
    --to=mbizon@freebox.fr \
    --cc=davem@davemloft.net \
    --cc=jk@ozlabs.org \
    --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;
as well as URLs for NNTP newsgroup(s).