From: Sonic Zhang <sonic.adi@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH][uart] fit blackfin uart over sport driver into common uart inftrastructure (v3)
Date: Fri, 18 Sep 2009 16:33:36 +0800 [thread overview]
Message-ID: <4e5ebad50909180133n1c04871dl29936b1aaf363a9f@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0909172331l8188d27t32899adc784cb503@mail.gmail.com>
No problem. I can split it up. But, without it this driver won't work
as expected.
Sonic Zhang
On Fri, Sep 18, 2009 at 2:31 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Fri, Sep 18, 2009 at 02:27, sonic zhang wrote:
>
> btw, "v3" and such in the subject should be inside of the [PATCH ...]
> so that git will trim it automatically
>
>> 1. Disable local interrupts in 32-bit reading from SPORT RX MMR to walk
>> around the RX underflow hardware issue when this reading is interrupted
>> by the other IRQ.
>
> i dont think this change should be squashed. it's unrelated to the
> larger issue you're tackling.
> http://git.kernel.org/?p=linux/kernel/git/vapier/blackfin.git;a=commitdiff;h=3393f5776d247fbd241c7fe52e2e420a64e36fa3
> -mike
>
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-09-18 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 6:27 [PATCH][uart] fit blackfin uart over sport driver into common uart inftrastructure (v3) sonic zhang
2009-09-18 6:31 ` Mike Frysinger
2009-09-18 8:33 ` Sonic Zhang [this message]
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=4e5ebad50909180133n1c04871dl29936b1aaf363a9f@mail.gmail.com \
--to=sonic.adi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vapier.adi@gmail.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 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).