lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100617214643N.fujita.tomonori@lab.ntt.co.jp>
Date:	Thu, 17 Jun 2010 21:48:05 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	jaxboe@...ionio.com
Cc:	fujita.tomonori@....ntt.co.jp, akpm@...ux-foundation.org,
	James.Bottomley@...e.de, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH -mm 0/3] remove useless ISA_DMA_THRESHOLD

On Wed, 2 Jun 2010 08:18:15 +0200
Jens Axboe <jaxboe@...ionio.com> wrote:

> On Tue, Jun 01 2010, FUJITA Tomonori wrote:
> > On Tue, 1 Jun 2010 20:24:52 +0200
> > Jens Axboe <jaxboe@...ionio.com> wrote:
> > 
> > > On Mon, May 31 2010, FUJITA Tomonori wrote:
> > > > This patchset removes useless ISA_DMA_THRESHOLD:
> > > > 
> > > > - ISA_DMA_THRESHOLD is irrelevant to the majority of architectures but
> > > >   they have to define it.
> > > > 
> > > > - ISA_DMA_THRESHOLD definition is inconsistent on architectures; ISA
> > > >   DMA addressing restriction, DMA addressing restriction or something
> > > >   else.
> > > > 
> > > > - Everyone (except for SCSI) uses dma_mask instead of ancient
> > > >   ISA_DMA_THRESHOLD.
> > > > 
> > > > Only SCSI uses ISA_DMA_THRESHOLD for ancient drivers with non-zero
> > > > unchecked_isa_dma. We can safely remove ISA_DMA_THRESHOLD usage in
> > > > SCSI. So we can clean up ISA_DMA_THRESHOLD on the whole tree.
> > > 
> > > Looks good. James, it's probably easier if I just carry this patch set.
> > 
> > Thanks,
> > 
> > Any tree works for me, I thought about -mm though.
> > 
> > Can you replace [1/3] with the following?
> > 
> > I fixed the subject and the body, s/aha1532/aha1542/;
> > 
> > Somehow I forgot to remove unused BAD_SG_DMA().
> 
> I'll collect the acks and include this update.

Can you send this to -next via your tree? I want this to be
compile-tested on -next on various architectures.

Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ