public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] SCSI, pmcraid: Fix kmalloc() argument order in pmcraid_chr_ioctl()
Date: Mon, 24 Oct 2011 16:17:23 -0700	[thread overview]
Message-ID: <1319498243.2094.9.camel@Joe-Laptop> (raw)
In-Reply-To: <alpine.LNX.2.00.1110250047430.19795@swampdragon.chaosbits.net>

On Tue, 2011-10-25 at 00:51 +0200, Jesper Juhl wrote:
> On Mon, 24 Oct 2011, Joe Perches wrote:
> > On Tue, 2011-10-25 at 00:38 +0200, Jesper Juhl wrote:
> > > The first argument to kmalloc() is the size, the second is
> > > flags. pmcraid_chr_ioctl() gets this wrong and swaps the
> > > arguments. This patch corrects the mistake.
[]
> > James seems to be uninterested in picking up
> > obvious and trivially correct patches.
> I've been getting that impression as well..
> For example: 
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next-history.git;a=commitdiff;h=2abe1b25e56b7c8e65f101fb22282dafeb5ec4ef 
> which I've been sumbitting numerous times over a long period of time 
> (these days akpm has picked it up and sends it on repeatedly, so I don't 
> really bother myself any more)... 
> > >From a year ago...
> > https://lkml.org/lkml/2010/10/31/123
> Ok, so you obviously got there first

That doesn't matter at all to me.

What matters is getting the defects fixed
and not dropping patches on the floor.

Maybe that means there should be a different
or an additional scsi maintainer.


  reply	other threads:[~2011-10-24 23:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 22:38 [PATCH] SCSI, pmcraid: Fix kmalloc() argument order in pmcraid_chr_ioctl() Jesper Juhl
2011-10-24 22:42 ` Joe Perches
2011-10-24 22:50   ` richard -rw- weinberger
2011-10-24 22:54     ` Dave Jones
2011-10-24 23:03       ` richard -rw- weinberger
2011-10-24 23:13         ` Jesper Juhl
2011-10-24 23:06       ` Jesper Juhl
2011-10-24 22:57     ` Jesper Juhl
2011-10-24 23:07       ` Joe Perches
2011-10-24 22:51   ` Jesper Juhl
2011-10-24 23:17     ` Joe Perches [this message]
2011-10-24 23:18   ` Dave Jones
2011-10-24 23:24     ` richard -rw- weinberger
2011-10-25  1:10       ` Joe Perches

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=1319498243.2094.9.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=JBottomley@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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