All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobin C. Harding <me@tobin.cc>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Stefano Manni <stefano.manni@gmail.com>,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse
Date: Sat, 25 Nov 2017 08:37:09 +1100	[thread overview]
Message-ID: <20171124213709.GH17858@eros> (raw)
In-Reply-To: <20171124124511.g2rigyszy26t2ze3@mwanda>

On Fri, Nov 24, 2017 at 04:02:09PM +0300, Dan Carpenter wrote:
> On Fri, Nov 24, 2017 at 09:20:20AM +1100, Tobin C. Harding wrote:
> > My current favourite review of all time was done by you on a what was
> > at the time a pretty hard patch for me. It was
> > 
> > 	Nope
> > 
> 
> Wow...  I know I've said that to other people but I can't believe I sent
> that to *you*...  Sorry.  You write good patches.

Not always :) No apology needed, I was genuinely encouraged to tighten
my game.

thanks,
Tobin

WARNING: multiple messages have this Message-ID (diff)
From: "Tobin C. Harding" <me@tobin.cc>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Stefano Manni <stefano.manni@gmail.com>,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	lustre-devel@lists.lustre.org
Subject: Re: [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse
Date: Sat, 25 Nov 2017 08:37:09 +1100	[thread overview]
Message-ID: <20171124213709.GH17858@eros> (raw)
In-Reply-To: <20171124124511.g2rigyszy26t2ze3@mwanda>

On Fri, Nov 24, 2017 at 04:02:09PM +0300, Dan Carpenter wrote:
> On Fri, Nov 24, 2017 at 09:20:20AM +1100, Tobin C. Harding wrote:
> > My current favourite review of all time was done by you on a what was
> > at the time a pretty hard patch for me. It was
> > 
> > 	Nope
> > 
> 
> Wow...  I know I've said that to other people but I can't believe I sent
> that to *you*...  Sorry.  You write good patches.

Not always :) No apology needed, I was genuinely encouraged to tighten
my game.

thanks,
Tobin

  reply	other threads:[~2017-11-24 21:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 19:38 [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse Stefano Manni
2017-11-22 19:38 ` [PATCH 1/4] staging: lustre: fixed signedness of some socklnd params Stefano Manni
2017-11-23 12:13   ` [lustre-devel] " Dan Carpenter
2017-11-23 12:13     ` Dan Carpenter
2017-11-23 23:47     ` Stefano Manni
2017-11-24 12:49       ` [lustre-devel] " Dan Carpenter
2017-11-24 12:49         ` Dan Carpenter
2017-11-22 19:38 ` [PATCH 2/4] staging: lustre: fixed signedness of llite Stefano Manni
2017-11-22 19:38 ` [PATCH 3/4] staging: lustre: fixed signedness of lov Stefano Manni
2017-11-24 15:42   ` [lustre-devel] " Greg Kroah-Hartman
2017-11-24 15:42     ` Greg Kroah-Hartman
2017-11-22 19:38 ` [PATCH 4/4] staging: lustre: fixed signedness of obdclass Stefano Manni
2017-11-23  4:59 ` [lustre-devel] [PATCH 0/4] staging: lustre: fixed some signedness warns from sparse Tobin C. Harding
2017-11-23  4:59   ` Tobin C. Harding
2017-11-23 11:51   ` [lustre-devel] " Dan Carpenter
2017-11-23 11:51     ` Dan Carpenter
2017-11-23 22:20     ` [lustre-devel] " Tobin C. Harding
2017-11-23 22:20       ` Tobin C. Harding
2017-11-23 23:32       ` Stefano Manni
2017-11-24 13:02       ` [lustre-devel] " Dan Carpenter
2017-11-24 13:02         ` Dan Carpenter
2017-11-24 21:37         ` Tobin C. Harding [this message]
2017-11-24 21:37           ` Tobin C. Harding

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=20171124213709.GH17858@eros \
    --to=me@tobin.cc \
    --cc=andreas.dilger@intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    --cc=stefano.manni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.