From: David Miller <davem@davemloft.net>
To: mkubecek@suse.cz
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net
Subject: Re: [PATCH net] ipv4: fix redirect handling for TCP packets
Date: Mon, 27 May 2013 23:23:50 -0700 (PDT) [thread overview]
Message-ID: <20130527.232350.1126293930261151421.davem@davemloft.net> (raw)
In-Reply-To: <20130527080120.424C662C67@unicorn.suse.cz>
From: Michal Kubecek <mkubecek@suse.cz>
Date: Mon, 27 May 2013 09:47:56 +0200
> Issue was introduced by commit 4895c771c (v3.6-rc1).
This string in parenthesis is not from the commit that introduced the
problem, it's from some random release tag after the commit.
You should always reference changes like this:
$SHA1ID ("Header line of the $SHA1ID commits message.")
Please fix this up and resubmit, thanks.
next prev parent reply other threads:[~2013-05-28 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 7:47 [PATCH net] ipv4: fix redirect handling for TCP packets Michal Kubecek
2013-05-28 6:23 ` David Miller [this message]
2013-05-28 6:26 ` [PATCH net v2] " Michal Kubecek
2013-05-28 6:40 ` 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=20130527.232350.1126293930261151421.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).