From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hoang-Nam Nguyen <hnguyen@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 2.6.19 4/4] ehca: ehca_av.c use constant for max mtu
Date: Mon, 06 Nov 2006 09:48:40 +1100 [thread overview]
Message-ID: <1162766921.28571.251.camel@localhost.localdomain> (raw)
In-Reply-To: <200611052142.56722.hnguyen@de.ibm.com>
Can you fix your patch sending technique ? A mangled patch inline with a
non-mangled one in attachment... that's a bit gross. Just get a proper
one inline and be done with it. If your mailer can't be coerced into not
damaging patches, then use another one for sending them.
Cheers,
Ben
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hoang-Nam Nguyen <hnguyen@de.ibm.com>
Cc: rolandd@cisco.com, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 2.6.19 4/4] ehca: ehca_av.c use constant for max mtu
Date: Mon, 06 Nov 2006 09:48:40 +1100 [thread overview]
Message-ID: <1162766921.28571.251.camel@localhost.localdomain> (raw)
In-Reply-To: <200611052142.56722.hnguyen@de.ibm.com>
Can you fix your patch sending technique ? A mangled patch inline with a
non-mangled one in attachment... that's a bit gross. Just get a proper
one inline and be done with it. If your mailer can't be coerced into not
damaging patches, then use another one for sending them.
Cheers,
Ben
next prev parent reply other threads:[~2006-11-05 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 20:42 [PATCH 2.6.19 4/4] ehca: ehca_av.c use constant for max mtu Hoang-Nam Nguyen
2006-11-05 20:42 ` Hoang-Nam Nguyen
2006-11-05 22:48 ` Benjamin Herrenschmidt [this message]
2006-11-05 22:48 ` Benjamin Herrenschmidt
2006-11-08 23:08 ` Roland Dreier
2006-11-08 23:08 ` Roland Dreier
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=1162766921.28571.251.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=hnguyen@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.