From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
wenyou.yang@atmel.com, ludovic.desroches@atmel.com,
leilei.zhao@atmel.com, voice.shen@atmel.com, josh.wu@atmel.com,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] tty/serial: at91: use correct type for dma_sync_*_for_cpu() and dma_sync_*_for_device()
Date: Fri, 9 Jan 2015 14:19:27 -0800 [thread overview]
Message-ID: <20150109221927.GA19100@kroah.com> (raw)
In-Reply-To: <54AFF037.1000004@atmel.com>
On Fri, Jan 09, 2015 at 04:13:59PM +0100, Nicolas Ferre wrote:
> Le 09/12/2014 14:31, Cyrille Pitchen a écrit :
> > dma_sync_*_for_cpu() and dma_sync_*_for_device() use 'enum dma_data_direction',
> > not 'enum dma_transfer_direction'
> >
> > Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>
> Sure:
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> Here it's difficult to add a "stable" tag as the error was introduced by
> several different patches.
So that means it's not ok for older kernels? That doesn't make sense...
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] tty/serial: at91: use correct type for dma_sync_*_for_cpu() and dma_sync_*_for_device()
Date: Fri, 9 Jan 2015 14:19:27 -0800 [thread overview]
Message-ID: <20150109221927.GA19100@kroah.com> (raw)
In-Reply-To: <54AFF037.1000004@atmel.com>
On Fri, Jan 09, 2015 at 04:13:59PM +0100, Nicolas Ferre wrote:
> Le 09/12/2014 14:31, Cyrille Pitchen a ?crit :
> > dma_sync_*_for_cpu() and dma_sync_*_for_device() use 'enum dma_data_direction',
> > not 'enum dma_transfer_direction'
> >
> > Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>
> Sure:
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> Here it's difficult to add a "stable" tag as the error was introduced by
> several different patches.
So that means it's not ok for older kernels? That doesn't make sense...
next prev parent reply other threads:[~2015-01-09 22:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 13:31 [PATCH 0/5] tty/serial: at91: fix atmel_serial_probe(), dma_sync_* and the Hardware Handshaking support Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` [PATCH 1/5] tty/serial: at91: use correct type for dma_sync_*_for_cpu() and dma_sync_*_for_device() Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2015-01-09 15:13 ` Nicolas Ferre
2015-01-09 15:13 ` Nicolas Ferre
2015-01-09 15:13 ` Nicolas Ferre
2015-01-09 22:19 ` Greg KH [this message]
2015-01-09 22:19 ` Greg KH
2014-12-09 13:31 ` [PATCH 2/5] tty/serial: at91: enable peripheral clock before accessing I/O registers Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2015-01-09 15:12 ` Nicolas Ferre
2015-01-09 15:12 ` Nicolas Ferre
2015-01-09 15:12 ` Nicolas Ferre
2014-12-09 13:31 ` [PATCH 3/5] tty/serial: at91: fix error handling in atmel_serial_probe() Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2015-01-09 15:28 ` Nicolas Ferre
2015-01-09 15:28 ` Nicolas Ferre
2015-01-09 15:28 ` Nicolas Ferre
2014-12-09 13:31 ` [PATCH 4/5] tty/serial: at91: fix RTS line management when hardware handshake is enabled Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2015-01-09 15:40 ` Nicolas Ferre
2015-01-09 15:40 ` Nicolas Ferre
2015-01-09 15:40 ` Nicolas Ferre
2014-12-09 13:31 ` [PATCH 5/5] tty/serial: at91: fix typo and indentation Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2014-12-09 13:31 ` Cyrille Pitchen
2015-01-09 15:41 ` Nicolas Ferre
2015-01-09 15:41 ` Nicolas Ferre
2015-01-09 15:41 ` Nicolas Ferre
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=20150109221927.GA19100@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cyrille.pitchen@atmel.com \
--cc=josh.wu@atmel.com \
--cc=leilei.zhao@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.com \
--cc=wenyou.yang@atmel.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 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.