From: Christoph Hellwig <hch@lst.de> To: Chen-Yu Tsai <wens@kernel.org> Cc: Russell King <linux@armlinux.org.uk>, Christoph Hellwig <hch@lst.de>, Andrew Morton <akpm@linux-foundation.org>, Chen-Yu Tsai <wens@csie.org>, Robin Murphy <robin.murphy@arm.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH RESEND v2] ARM: dma-api: fix max_pfn off-by-one error in __dma_supported() Date: Thu, 9 Jan 2020 15:38:59 +0100 [thread overview] Message-ID: <20200109143859.GA22907@lst.de> (raw) In-Reply-To: <20191224030239.5656-1-wens@kernel.org> Looks good: Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Chen-Yu Tsai <wens@kernel.org> Cc: Russell King <linux@armlinux.org.uk>, stable@vger.kernel.org, linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>, Andrew Morton <akpm@linux-foundation.org>, Robin Murphy <robin.murphy@arm.com>, Christoph Hellwig <hch@lst.de>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH RESEND v2] ARM: dma-api: fix max_pfn off-by-one error in __dma_supported() Date: Thu, 9 Jan 2020 15:38:59 +0100 [thread overview] Message-ID: <20200109143859.GA22907@lst.de> (raw) In-Reply-To: <20191224030239.5656-1-wens@kernel.org> Looks good: Reviewed-by: Christoph Hellwig <hch@lst.de> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-09 14:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-24 3:02 [PATCH RESEND v2] ARM: dma-api: fix max_pfn off-by-one error in __dma_supported() Chen-Yu Tsai 2019-12-24 3:02 ` Chen-Yu Tsai 2020-01-09 14:38 ` Christoph Hellwig [this message] 2020-01-09 14:38 ` Christoph Hellwig
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=20200109143859.GA22907@lst.de \ --to=hch@lst.de \ --cc=akpm@linux-foundation.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=robin.murphy@arm.com \ --cc=stable@vger.kernel.org \ --cc=wens@csie.org \ --cc=wens@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: linkBe 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.