All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"James.Bottomley@suse.de" <James.Bottomley@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH -mm 0/3] remove useless ISA_DMA_THRESHOLD
Date: Thu, 17 Jun 2010 14:59:11 +0200	[thread overview]
Message-ID: <4C1A1C1F.5030302@fusionio.com> (raw)
In-Reply-To: <20100617214643N.fujita.tomonori@lab.ntt.co.jp>

On 2010-06-17 14:48, FUJITA Tomonori wrote:
> On Wed, 2 Jun 2010 08:18:15 +0200
> Jens Axboe <jaxboe@fusionio.com> wrote:
> 
>> On Tue, Jun 01 2010, FUJITA Tomonori wrote:
>>> On Tue, 1 Jun 2010 20:24:52 +0200
>>> Jens Axboe <jaxboe@fusionio.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.

Yep, going out now.


-- 
Jens Axboe

      reply	other threads:[~2010-06-17 12:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  6:59 [PATCH -mm 0/3] remove useless ISA_DMA_THRESHOLD FUJITA Tomonori
2010-05-31  6:59 ` [PATCH -mm 1/3] aha1532: remove ISA_DMA_THRESHOLD usage FUJITA Tomonori
2010-05-31  6:59 ` [PATCH -mm 2/3] block: kill " FUJITA Tomonori
2010-05-31  6:59 ` [PATCH -mm 3/3] remove needless ISA_DMA_THRESHOLD FUJITA Tomonori
2010-06-01 18:51   ` David Howells
2010-06-01 18:24 ` [PATCH -mm 0/3] remove useless ISA_DMA_THRESHOLD Jens Axboe
2010-06-01 18:34   ` James Bottomley
2010-06-02  2:30   ` FUJITA Tomonori
2010-06-02  6:18     ` Jens Axboe
2010-06-17 12:48       ` FUJITA Tomonori
2010-06-17 12:59         ` Jens Axboe [this message]

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=4C1A1C1F.5030302@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=James.Bottomley@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@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 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.