From: "Remy Bohmer" <linux@bohmer.net>
To: "Andrew Victor" <avictor.za@gmail.com>
Cc: "Andrew Victor" <linux@maxim.org.za>,
RT <linux-rt-users@vger.kernel.org>,
"ARM Linux Mailing List"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"Steven Rostedt" <rostedt@goodmis.org>,
"David Brownell" <david-b@pacbell.net>,
hskinnemoen@atmel.com
Subject: Re: [PATCH]: Atmel Serial Console interrupt handler splitup
Date: Fri, 7 Dec 2007 21:38:17 +0100 [thread overview]
Message-ID: <3efb10970712071238v4c3f1e03q60114a37b6d11b2e@mail.gmail.com> (raw)
In-Reply-To: <cd73a99e0712071157t6b5fe850l52e21dd31a6b8411@mail.gmail.com>
Hello Andrew,
> The serial driver is also used for Atmel's AVR32 architecture.
> There was some bug in the DMA patch that causes it to fail there -
> Haavard was going to look into in when he had time.
> Once that is resolved, the DMA patch will be submitted to mainline.
In that case, shall I create a new patchset for this compared to mainline?
Then we can merge the DMA patch in the interrupt handler later on. (it
is really difficult to do)
Kind Regards,
Remy
next prev parent reply other threads:[~2007-12-07 20:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 15:24 [PATCH]: Atmel Serial Console interrupt handler splitup Remy Bohmer
2007-12-07 18:31 ` David Brownell
2007-12-07 19:57 ` Andrew Victor
2007-12-07 20:38 ` Remy Bohmer [this message]
2007-12-07 21:16 ` Remy Bohmer
2007-12-12 21:10 ` Steven Rostedt
2007-12-12 22:29 ` Remy Bohmer
2007-12-13 16:40 ` Remy Bohmer
2007-12-13 17:33 ` Andrew Victor
2007-12-13 20:32 ` Remy Bohmer
2007-12-13 20:35 ` Remy Bohmer
2007-12-14 11:46 ` Remy Bohmer
2007-12-17 12:17 ` Haavard Skinnemoen
2007-12-17 18:13 ` Haavard Skinnemoen
2007-12-17 20:56 ` Remy Bohmer
2007-12-17 23:12 ` Haavard Skinnemoen
2007-12-18 7:32 ` Remy Bohmer
2007-12-17 23:49 ` Russell King - ARM Linux
2007-12-18 9:07 ` Haavard Skinnemoen
[not found] <AANLkTi=TyvXEtoZGatP5pxymLSna9g6ULV46i72bYgc4@mail.gmail.com>
2010-10-29 13:52 ` Remy Bohmer
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=3efb10970712071238v4c3f1e03q60114a37b6d11b2e@mail.gmail.com \
--to=linux@bohmer.net \
--cc=avictor.za@gmail.com \
--cc=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=rostedt@goodmis.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: 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;
as well as URLs for NNTP newsgroup(s).