Re: [alsa-devel] [PATCH v2 0/3] Switch to ioremap_wc in the SRAM allocator code
From: gregkh@xxxxxxxxxxxxxxxxxxx
Date: Sun Mar 01 2015 - 11:43:43 EST
On Sun, Mar 01, 2015 at 10:00:37PM +0530, Abhilash Kesavan wrote:
> Hi Greg,
>
> On Fri, Feb 6, 2015 at 9:14 PM, Catalin Marinas <catalin.marinas@xxxxxxx> wrote:
> > On Fri, Feb 06, 2015 at 01:45:25PM +0000, Abhilash Kesavan wrote:
> >> Fix alignment faults seen during play-back of files with specific
> >> sampling rates such as 44.1K. This is based on the discussion here:
> >> http://www.spinics.net/lists/arm-kernel/msg384647.html
> >>
> >> Patch 1 is needed as m32r arch does not define ioremap_wc. Patch 2 adds a
> >> resource managed helper function for ioremap_wc which is used in patch 3.
> >>
> >> Changes since v1:
> >> - Fix the compilation error with m32r due to missing ioremap_wc
> >> definition.
> >> - Fixed minor indentation issues.
> >>
> >> Note: Other architectures either have ioremap_wc defined or are including
> >> generic "io.h"/"iomap.h". c6x arch is the only one I am not sure of.
> >>
> >> Abhilash Kesavan (3):
> >> m32r: add definition of ioremap_wc to io.h
> >> lib: devres: add a helper function for ioremap_wc
> >> misc: sram: switch to ioremap_wc from ioremap
> >>
> >> Documentation/driver-model/devres.txt | 1 +
> >> arch/m32r/include/asm/io.h | 1 +
> >> drivers/misc/sram.c | 17 ++++++++++++++---
> >> include/linux/io.h | 2 ++
> >> lib/devres.c | 28 ++++++++++++++++++++++++++++
> >> 5 files changed, 46 insertions(+), 3 deletions(-)
> >
> > For the series:
> >
> > Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx>
>
> These patches still apply cleanly on linux-next and have been ack'ed
> by Catalin and Philipp. Would you like me to collect the tags and
> resend the series or can they be applied as is ?
I can take them as-is, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/