From: Sorin Dumitru <sdumitru@ixiacom.com>
To: James Hogan <james.hogan@imgtec.com>,
<linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>
Cc: <ralf@linux-mips.org>
Subject: Re: [PATCH] mips: n32: use compat getsockopt syscall
Date: Fri, 20 Jun 2014 13:40:48 +0300 [thread overview]
Message-ID: <53A40FB0.2020503@ixiacom.com> (raw)
In-Reply-To: <53A404D2.3030303@imgtec.com>
On 06/20/14 12:54, James Hogan wrote:
> On 20/06/14 08:53, Sorin Dumitru wrote:
>> Signed-off-by: Sorin Dumitru <sdumitru@ixiacom.com>
>
> A little more commit message wouldn't hurt. Did it break a particular
> program?
Yes, it was found by an internal program trying to get IP_PKTOPTIONS on
a cavium octeon board.
Should I resubmit stating what was broken in the commit message?
Thanks,
Sorin
next prev parent reply other threads:[~2014-06-20 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 7:53 [PATCH] mips: n32: use compat getsockopt syscall Sorin Dumitru
2014-06-20 9:54 ` James Hogan
2014-06-20 10:40 ` Sorin Dumitru [this message]
2014-06-20 10:50 ` James Hogan
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=53A40FB0.2020503@ixiacom.com \
--to=sdumitru@ixiacom.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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