From: Stephen Boyd <sboyd@codeaurora.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] hvc_dcc cleanups and fixes
Date: Thu, 03 Feb 2011 15:19:07 -0800 [thread overview]
Message-ID: <4D4B37EB.7070401@codeaurora.org> (raw)
In-Reply-To: <20110203221742.GA4159@kroah.com>
> On Mon, Dec 20, 2010 at 12:08:35PM -0800, Stephen Boyd wrote:
>> Here are the split patches.
>>
>> The first two patches cleanup and fix the hvc_dcc driver for my
>> compiler. The final patch is more controversial, it removes the
>> v6 and v7 differences in this driver.
>>
>> Stephen Boyd (3):
>> hvc_dcc: Fix bad code generation by marking assembly volatile
>> hvc_dcc: Simplify put_chars()/get_chars() loops
>> hvc_dcc: Simplify assembly for v6 and v7 ARM
>
> Can you redo these against the linux-next tree as they don't apply
> anymore and resend them so I can apply them?
>
Have you tried 'git am -3' on them? I assume it's the movement of the
file that's causing the problem.
Either way, I'll resend and collect the acks in a bit.
next prev parent reply other threads:[~2011-02-03 23:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 19:25 [PATCH] drivers: char: hvc: add arm JTAG DCC console support Daniel Walker
2010-11-30 19:57 ` Nicolas Pitre
2010-11-30 21:17 ` Arnd Bergmann
2010-12-01 5:30 ` Stephen Boyd
2010-12-01 18:54 ` Daniel Walker
2010-12-01 19:28 ` Greg KH
2010-12-18 5:16 ` [PATCH] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-20 17:51 ` Daniel Walker
2010-12-20 18:39 ` Stephen Boyd
2010-12-20 18:46 ` Nicolas Pitre
2010-12-20 20:08 ` [PATCH 0/3] hvc_dcc cleanups and fixes Stephen Boyd
2010-12-20 20:08 ` [PATCH 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile Stephen Boyd
2010-12-20 21:39 ` Nicolas Pitre
2011-01-02 9:00 ` Pavel Machek
2011-01-02 18:49 ` David Brown
2011-01-03 5:50 ` Pavel Machek
2011-01-04 18:49 ` Tony Lindgren
2010-12-20 21:49 ` Arnaud Lacombe
2010-12-20 21:52 ` Stephen Boyd
2010-12-20 22:10 ` Nicolas Pitre
2010-12-20 20:08 ` [PATCH 2/3] hvc_dcc: Simplify put_chars()/get_chars() loops Stephen Boyd
2010-12-20 20:08 ` [PATCH 3/3] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-20 21:44 ` Nicolas Pitre
2011-01-04 18:52 ` Tony Lindgren
2011-01-06 1:49 ` [PATCH 0/3] hvc_dcc cleanups and fixes Stephen Boyd
2011-01-06 3:20 ` Greg KH
2011-02-03 22:17 ` Greg KH
2011-02-03 23:19 ` Stephen Boyd [this message]
2011-02-03 23:30 ` Greg KH
2011-02-03 23:48 ` [PATCHv2 " Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 2/3] hvc_dcc: Simplify put_chars()/get_chars() loops Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 3/3] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-01 20:20 ` [PATCH] drivers: char: hvc: add arm JTAG DCC console support Stephen Boyd
2010-12-07 19:10 ` Stephen Boyd
2011-01-14 19:19 ` Tony Lindgren
2011-01-14 23:49 ` Stephen Boyd
2011-04-07 18:39 ` RONETIX - Asen Dimov
2011-04-07 18:57 ` Mike Frysinger
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=4D4B37EB.7070401@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.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: 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).