From: Ben Hutchings <bhutchings@solarflare.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Ramesh Nagappa <ramesh.nagappa@ericsson.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"michel@digirati.com.br" <michel@digirati.com.br>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>
Subject: Re: [PATCH] net: fix neigh_resolve_output can cause skb_under_panic
Date: Mon, 1 Oct 2012 19:00:40 +0100 [thread overview]
Message-ID: <1349114440.2577.26.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <20120929005721.GA13335@kroah.com>
On Fri, 2012-09-28 at 17:57 -0700, gregkh@linuxfoundation.org wrote:
[...]
> > > You need a blank line before the first Signed-off-by: line.
> > > Surely one of the reviewers should have caught this basic thing?
> >
> > Outlook mangled the patch. I am unable to use git send-email because of
> > a corporate firewall on the build machine.
>
> Then your patch would also be corrupted, Outlook, and Exchange, can not
> handle patches at all. Please read Documentation/email_clients.txt for
> more details.
>
> Also, ask your coworkers who properly submit patches what they do to
> work around your broken email infrastructure.
I successfully send patches using git-imap-send and Evolution talking to
Exchange 2010 through its IMAP and SMTP submission interfaces. (I think
the previous version worked as well.) But I would agree that Outlook is
probably hopeless.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2012-10-01 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 23:40 Ramesh Nagappa
2012-09-28 23:52 ` gregkh
2012-09-29 0:17 ` Ramesh Nagappa
2012-09-29 0:26 ` Ramesh Nagappa
2012-09-29 0:57 ` gregkh
2012-10-01 18:00 ` Ben Hutchings [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=1349114440.2577.26.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@digirati.com.br \
--cc=netdev@vger.kernel.org \
--cc=ramesh.nagappa@ericsson.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
all inboxes | Powered by JetHome®