From: Tristan Lelong <tristan@lelong.xyz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
askb23@gmail.com, john.hammond@intel.com, gdonald@gmail.com,
anhlq2110@gmail.com, fabio.falzoi84@gmail.com, oort10@gmail.com,
agimenez@sysvalve.es, rupran@einserver.de,
surya.seetharaman9@gmail.com, Julia.Lawall@lip6.fr,
joe@perches.com, a.terekhov@gmail.com, liang.zhen@intel.com,
vthakkar1994@gmail.com, amk@cray.com, srikrishanmalik@gmail.com,
rd@radekdostal.com, bergwolf@gmail.com, dan.carpenter@oracle.com,
paul.gortmaker@windriver.com, tapaswenipathak@gmail.com,
email@christophjaeger.info, uja.ornl@gmail.com,
brilliantov@inbox.ru, dmitry.eremin@intel.com,
HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros
Date: Mon, 19 Jan 2015 23:54:48 -0800 [thread overview]
Message-ID: <20150120075448.GA4355@lenderer> (raw)
In-Reply-To: <20150118070222.GA10794@kroah.com>
Greg,
On Sun, Jan 18, 2015 at 04:02:22PM +0900, Greg KH wrote:
> On Sat, Jan 17, 2015 at 10:41:44PM -0800, Tristan Lelong wrote:
> > Hi Greg,
> >
> > On Sat, Jan 17, 2015 at 03:28:27PM -0800, Greg KH wrote:
> > >
> > > I took your v2 version, please send me the difference as this is a
> > > mess...
> >
> > Not sure I understand what you meant here.
> > Do you want me to submit a new patch that contains only the differences between v2 and v3?
>
> Yes please. Make it against the tree you got the email saying when your
> v2 patch was accepted.
>
Just for reference, I submitted this patch as a new patch "[PATCH] staging: lustre: remove kmalloc from fld_proc_hash_seq_write"
I figured out it might trigger some more comments, and didn't want to add to the confusion.
Let me know if this is the right way, or if you would prefer an answer to email with the updated patch.
Regards
prev parent reply other threads:[~2015-01-20 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 0:03 [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros Tristan Lelong
2014-12-24 13:53 ` Tristan Lelong
2015-01-17 23:28 ` Greg KH
2015-01-18 6:41 ` Tristan Lelong
2015-01-18 7:02 ` Greg KH
2015-01-20 7:54 ` Tristan Lelong [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=20150120075448.GA4355@lenderer \
--to=tristan@lelong.xyz \
--cc=HPDD-discuss@ml01.01.org \
--cc=Julia.Lawall@lip6.fr \
--cc=a.terekhov@gmail.com \
--cc=agimenez@sysvalve.es \
--cc=amk@cray.com \
--cc=andreas.dilger@intel.com \
--cc=anhlq2110@gmail.com \
--cc=askb23@gmail.com \
--cc=bergwolf@gmail.com \
--cc=brilliantov@inbox.ru \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dmitry.eremin@intel.com \
--cc=email@christophjaeger.info \
--cc=fabio.falzoi84@gmail.com \
--cc=gdonald@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=john.hammond@intel.com \
--cc=liang.zhen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=oort10@gmail.com \
--cc=paul.gortmaker@windriver.com \
--cc=rd@radekdostal.com \
--cc=rupran@einserver.de \
--cc=srikrishanmalik@gmail.com \
--cc=surya.seetharaman9@gmail.com \
--cc=tapaswenipathak@gmail.com \
--cc=uja.ornl@gmail.com \
--cc=vthakkar1994@gmail.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