From: Andrew Morton <akpm@linux-foundation.org> To: Brian Starkey <brian.starkey@arm.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Catalin Marinas <catalin.marinas@arm.com>, Dan Williams <dan.j.williams@intel.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RESEND2 PATCH 1/3] memremap: add MEMREMAP_WC flag Date: Wed, 17 Feb 2016 11:02:31 -0800 [thread overview] Message-ID: <20160217110231.d4040207cc1456bd991ff0e7@linux-foundation.org> (raw) In-Reply-To: <20160217115347.GA28433@e106950-lin.cambridge.arm.com> On Wed, 17 Feb 2016 11:53:48 +0000 Brian Starkey <brian.starkey@arm.com> wrote: > Hi Andrew, > > Would you pick these up if I rebase onto linux-next? Sure. > How strongly do you feel about the input argument modification vs. > staying in-line with the rest of the function? I see no reason why memremap() is modifying `flags' as it proceeds - these flags are all disjoint so it's pointless. I suggest you simply take all that out in a preparatory patch.
WARNING: multiple messages have this Message-ID (diff)
From: akpm@linux-foundation.org (Andrew Morton) To: linux-arm-kernel@lists.infradead.org Subject: [RESEND2 PATCH 1/3] memremap: add MEMREMAP_WC flag Date: Wed, 17 Feb 2016 11:02:31 -0800 [thread overview] Message-ID: <20160217110231.d4040207cc1456bd991ff0e7@linux-foundation.org> (raw) In-Reply-To: <20160217115347.GA28433@e106950-lin.cambridge.arm.com> On Wed, 17 Feb 2016 11:53:48 +0000 Brian Starkey <brian.starkey@arm.com> wrote: > Hi Andrew, > > Would you pick these up if I rebase onto linux-next? Sure. > How strongly do you feel about the input argument modification vs. > staying in-line with the rest of the function? I see no reason why memremap() is modifying `flags' as it proceeds - these flags are all disjoint so it's pointless. I suggest you simply take all that out in a preparatory patch.
next prev parent reply other threads:[~2016-02-17 19:02 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-08 17:30 [RESEND2 PATCH 0/3] Fix kernel panic in dma-coherent Brian Starkey 2016-02-08 17:30 ` Brian Starkey 2016-02-08 17:30 ` [RESEND2 PATCH 1/3] memremap: add MEMREMAP_WC flag Brian Starkey 2016-02-08 17:30 ` Brian Starkey 2016-02-08 18:30 ` Greg Kroah-Hartman 2016-02-08 18:30 ` Greg Kroah-Hartman 2016-02-09 9:15 ` Brian Starkey 2016-02-09 9:15 ` Brian Starkey 2016-02-16 11:14 ` Brian Starkey 2016-02-16 11:14 ` Brian Starkey 2016-02-17 0:43 ` Greg Kroah-Hartman 2016-02-17 0:43 ` Greg Kroah-Hartman 2016-02-17 10:07 ` Brian Starkey 2016-02-17 10:07 ` Brian Starkey 2016-02-08 20:03 ` Andrew Morton 2016-02-08 20:03 ` Andrew Morton 2016-02-09 10:23 ` Brian Starkey 2016-02-09 10:23 ` Brian Starkey 2016-02-17 11:53 ` Brian Starkey 2016-02-17 11:53 ` Brian Starkey 2016-02-17 19:02 ` Andrew Morton [this message] 2016-02-17 19:02 ` Andrew Morton 2016-02-08 17:30 ` [RESEND2 PATCH 2/3] drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP Brian Starkey 2016-02-08 17:30 ` Brian Starkey 2016-02-08 17:30 ` [RESEND2 PATCH 3/3] drivers: dma-coherent: use memset_io for DMA_MEMORY_IO mappings Brian Starkey 2016-02-08 17:30 ` Brian Starkey 2016-02-08 17:50 ` [RESEND2 PATCH 0/3] Fix kernel panic in dma-coherent Mark Rutland 2016-02-08 17:50 ` Mark Rutland 2016-02-08 17:59 ` Robin Murphy 2016-02-08 17:59 ` Robin Murphy 2016-02-08 18:04 ` Mark Rutland 2016-02-08 18:04 ` Mark Rutland
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=20160217110231.d4040207cc1456bd991ff0e7@linux-foundation.org \ --to=akpm@linux-foundation.org \ --cc=brian.starkey@arm.com \ --cc=catalin.marinas@arm.com \ --cc=dan.j.williams@intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-arm-kernel@lists.infradead.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: 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.