mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Petr Tesarik <petrtesarik@huaweicloud.com>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"open list:PARISC ARCHITECTURE" <linux-parisc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Cc: Roberto Sassu <roberto.sassu@huaweicloud.com>, petr@tesarici.cz
Subject: Re: [PATCH v1] parisc: pci-dma: remove unused and dead EISA code and comment
Date: Thu, 3 Aug 2023 10:04:50 +0200	[thread overview]
Message-ID: <0ff53a6d-4730-1fa5-740d-93dee35c80ea@gmx.de> (raw)
In-Reply-To: <20230802163321.1560-1-petrtesarik@huaweicloud.com>

On 8/2/23 18:33, Petr Tesarik wrote:
> From: Petr Tesarik <petr.tesarik.ext@huawei.com>
>
> Clearly, this code isn't needed, but it gives a false positive when
> grepping the complete source tree for coherent_dma_mask.
>
> Signed-off-by: Petr Tesarik <petr.tesarik.ext@huawei.com>

queued up in parisc git tree.

Thanks!
Helge

> ---
>   arch/parisc/kernel/pci-dma.c | 8 --------
>   1 file changed, 8 deletions(-)
>
> diff --git a/arch/parisc/kernel/pci-dma.c b/arch/parisc/kernel/pci-dma.c
> index d818ece23b4a..3f6b507970eb 100644
> --- a/arch/parisc/kernel/pci-dma.c
> +++ b/arch/parisc/kernel/pci-dma.c
> @@ -417,14 +417,6 @@ void *arch_dma_alloc(struct device *dev, size_t size,
>   	map_uncached_pages(vaddr, size, paddr);
>   	*dma_handle = (dma_addr_t) paddr;
>
> -#if 0
> -/* This probably isn't needed to support EISA cards.
> -** ISA cards will certainly only support 24-bit DMA addressing.
> -** Not clear if we can, want, or need to support ISA.
> -*/
> -	if (!dev || *dev->coherent_dma_mask < 0xffffffff)
> -		gfp |= GFP_DMA;
> -#endif
>   	return (void *)vaddr;
>   }
>


      reply	other threads:[~2023-08-03  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 16:33 Petr Tesarik
2023-08-03  8:04 ` Helge Deller [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=0ff53a6d-4730-1fa5-740d-93dee35c80ea@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=petr@tesarici.cz \
    --cc=petrtesarik@huaweicloud.com \
    --cc=roberto.sassu@huaweicloud.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

all inboxes | Powered by JetHome®