From: Dan Carpenter <dan.carpenter@oracle.com>
To: Geliang Tang <geliangtang@163.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
gregkh@linuxfoundation.org, HPDD-discuss@ml01.01.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: lnet: fix type warning in lib-socket.c
Date: Mon, 29 Jun 2015 11:26:34 +0300 [thread overview]
Message-ID: <20150629082634.GH28762@mwanda> (raw)
In-Reply-To: <1435472070-16218-1-git-send-email-geliangtang@163.com>
This patch isn't the correct fix.
The lustre people need to go through and cleanup this stuff, it's not
really a good patch for a newbie to start with.
regards,
dan carpenter
next prev parent reply other threads:[~2015-06-29 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 6:14 [PATCH] staging: lustre: lnet: fix type warning in lib-socket.c Geliang Tang
2015-06-29 8:26 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 10:05 William Blough
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=20150629082634.GH28762@mwanda \
--to=dan.carpenter@oracle.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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