public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: "Mukker, Atul" <Atulm@lsil.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	"'bunk@fs.tum.de'" <bunk@fs.tum.de>,
	"'Andrew Morton'" <akpm@osdl.org>,
	"'Matt_Domsch@dell.com'" <Matt_Domsch@dell.com>,
	"Ju, Seokmann" <sju@lsil.com>
Subject: RE: [PATCH]: megaraid 2.20.4: Fixes a data corruption bug
Date: 05 Oct 2004 14:27:36 -0500	[thread overview]
Message-ID: <1097004463.2064.85.camel@mulgrave> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570230C98F@exa-atlanta>

On Tue, 2004-10-05 at 14:15, Bagalkote, Sreenivas wrote:
> The latest megaraid driver on bk://linux-scsi.bkbits.net/scsi-misc-2.6 still
> has
> CONFIG_COMPAT around register_ioctl32_conversion. Will it remain in the
> source
> or should it go?

I'd like to see a patch taking it out, please.

James



  reply	other threads:[~2004-10-05 19:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 19:15 [PATCH]: megaraid 2.20.4: Fixes a data corruption bug Bagalkote, Sreenivas
2004-10-05 19:27 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06 15:23 Bagalkote, Sreenivas
2004-10-01 22:52 Bagalkote, Sreenivas
2004-10-01 23:09 ` James Bottomley
2004-10-01 21:39 Bagalkote, Sreenivas
2004-10-01 20:32 Bagalkote, Sreenivas
2004-10-01 20:43 ` James Bottomley
2004-10-01 20:08 Bagalkote, Sreenivas
2004-10-01 20:24 ` James Bottomley
2004-10-01 20:58 ` James Bottomley
2004-09-30 16:19 Mukker, Atul
2004-09-29 21:28 Mukker, Atul
2004-09-30  3:16 ` James Bottomley
2004-09-29  1:31 Bagalkote, Sreenivas

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=1097004463.2064.85.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Atulm@lsil.com \
    --cc=Matt_Domsch@dell.com \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sju@lsil.com \
    --cc=sreenib@lsil.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