From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH/review] Blackfin: fix up UART status bit handling
Date: Sun, 20 Apr 2008 03:08:38 -0400 [thread overview]
Message-ID: <200804200308.40844.vapier@gentoo.org> (raw)
In-Reply-To: <20080420063646.B519624657@gemini.denx.de>
On Sunday 20 April 2008, Wolfgang Denk wrote:
> In message <1207721182-29697-2-git-send-email-vapier@gentoo.org> you wrote:
> > Some Blackfin UARTs are read-to-clear while others are write-to-clear.
> > This can cause problems when we poll the LSR and then later try and
> > handle any errors detected.
> >
> > Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>
> I guess I will receive a pull request for the BF custodian repo for
> this and the other "PATCH/review" messages you posted?
anything i post with "PATCH/review" is intended for review only. i'll stick
them into the BF repo and have you pull them later since you didnt like me
asking for straight pulls.
> Do you have any plan when you will send the pull request?
that's why i asked about the merge window. since it's closed, i wont make any
requests until it's open.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080420/f101227f/attachment.pgp
next prev parent reply other threads:[~2008-04-20 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 6:06 [U-Boot-Users] [PATCH/review] Blackfin: make baud calculation more accurate Mike Frysinger
2008-04-09 6:06 ` [U-Boot-Users] [PATCH/review] Blackfin: fix up UART status bit handling Mike Frysinger
2008-04-20 6:36 ` Wolfgang Denk
2008-04-20 7:08 ` Mike Frysinger [this message]
2008-04-20 6:36 ` [U-Boot-Users] [PATCH/review] Blackfin: make baud calculation more accurate Wolfgang Denk
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=200804200308.40844.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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.