linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
	Bastien Philbert <bastienphilbert@gmail.com>,
	Julian Calaby <julian.calaby@gmail.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode
Date: Wed, 6 Apr 2016 15:34:13 -0400	[thread overview]
Message-ID: <20160406193413.GE7369@thunk.org> (raw)
In-Reply-To: <20160406184149.GA6388@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

On Wed, Apr 06, 2016 at 11:41:49AM -0700, Greg KH wrote:
> > > > Is this Nick Krause?  An email reply that Martin forwarded but the 
> > > > list didn't pick up (because it had a html part) suggests this. 
> > > >  What you're doing is what got you banned from LKML the last time: 
> > > > sending patches without evidence there's a problem or understanding 
> > > > the code you're patching.  Repeating the behaviour under a new 
> > > > identity isn't going to help improve your standing.
> > > > 
> > > No I am not Nick Krause. I am just aware of how he got banned a few 
> > > years ago. That email was a mistake by typo and was hoping nobody 
> > > picked it up as they would then believe I was Nick Krause.
> > 
> > Hm, OK, but currently you are repeating his behaviour ... please don't
> > send any more patches until they're about real problems backed by
> > actual data.
> 
> He's Nick, look at the email headers for proof.
> 
> James, and everyone else, please drop his patches.  I'll go get him
> banned from vger again.
> 
> Nick, please stop, you have violated the DCO now, a much worse thing
> than before.

Even if Bastien is going to try to claim that he happens to live in
the same house as Nick, the following two patches clearly shows that
even if Bastien is violating the DCO by using a fake sock puppet, he's
violated the DCO by failing to give Nick credit for writing the
identical patch.

						- Ted


[-- Attachment #2: evidence.gz --]
[-- Type: application/gzip, Size: 7182 bytes --]

  reply	other threads:[~2016-04-06 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 21:19 [PATCH] csiostor: Fix backwards locking in the function __csio_unreg_rnode Bastien Philbert
2016-04-06  7:48 ` Julian Calaby
2016-04-06 13:21   ` Bastien Philbert
2016-04-06 13:38     ` James Bottomley
2016-04-06 14:11       ` Bastien Philbert
2016-04-06 14:24         ` James Bottomley
2016-04-06 14:36           ` Bastien Philbert
2016-04-06 17:14             ` James Bottomley
2016-04-06 17:23               ` Bastien Philbert
2016-04-06 17:28                 ` James Bottomley
2016-04-06 17:35                   ` Bastien Philbert
2016-04-06 18:41                   ` Greg KH
2016-04-06 19:34                     ` Theodore Ts'o [this message]
     [not found] <1441300143-1143-1-git-send-email-xerofoify@gmail.com>
2015-09-04 22:44 ` [PATCH] csiostor:Fix " Anish Bhatt

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=20160406193413.GE7369@thunk.org \
    --to=tytso@mit.edu \
    --cc=bastienphilbert@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).