From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH 1/2] TIPC: Updated topology subscription protocol according to latest spec
Date: Mon, 05 Apr 2010 19:18:58 -0700 (PDT) [thread overview]
Message-ID: <20100405.191858.258288325.davem@davemloft.net> (raw)
In-Reply-To: <1270516572-27789-1-git-send-email-jon.maloy@ericsson.com>
You're going to need to provide a descriptive commit log message with
these changes explaining what exactly is changing and why, as well as
provide a proper signoff for the patch.
Please read Documentation/SubmittingPatches at a minimum...
next prev parent reply other threads:[~2010-04-06 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <../outgoing_patches/>
2010-04-06 1:16 ` [PATCH 1/2] TIPC: Updated topology subscription protocol according to latest spec Jon Maloy
2010-04-06 2:18 ` David Miller [this message]
2010-04-06 5:11 ` [PATCH 1/2] TIPC: Updated topology subscriptionprotocol " Suryanarayana.Garlapati
2010-04-06 1:16 ` [PATCH 2/2] TIPC: Minor change to comment field in API Jon Maloy
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=20100405.191858.258288325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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).