From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
linux-serial@vger.kernel.org, linux@bohmer.net,
marc.pignat@hevs.ch, itai.levi.devel@gmail.com
Subject: Re: [patch 2/3] atmel_serial might lose modem status change
Date: Wed, 14 Jan 2009 16:42:58 +0100 [thread overview]
Message-ID: <20090114164258.6373db9d@hskinnemoen-d830> (raw)
In-Reply-To: <20090114.121339.118371076.nemoto@toshiba-tops.co.jp>
Atsushi Nemoto wrote:
> > @@ -805,6 +805,9 @@ static int atmel_startup(struct uart_por
> > */
> > UART_PUT_IDR(port, -1);
> >
> > + atmel_port->irq_status_prev = UART_GET_CSR(port);
> > + atmel_port->irq_status = atmel_port->irq_status_prev;
> > +
> > /*
> > * Allocate the IRQ
> > */
>
> Looks correct for me too. Then, what is preffered final fix?
>
> Put irq_status initialization into my patch, or replace with Itai's
> patch? These patch put initialization in another place. Any comments
> for preferred place to fix?
I don't think it matters as long as it happens before the interrupts
are enabled. But it's probably enough to do it once ;-)
So the easiest solution is probably to drop your patch
(atmel_serial-might-lose-modem-status-change.patch) and keep Itai's
patch (atmel_serial-might-lose-modem-status-change-fix.patch).
Andrew, if it makes things easier, feel free to drop both patches and
I'll send you a new one.
Haavard
prev parent reply other threads:[~2009-01-14 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 22:17 [patch 2/3] atmel_serial might lose modem status change akpm
2009-01-12 9:42 ` Haavard Skinnemoen
2009-01-14 3:13 ` Atsushi Nemoto
2009-01-14 15:42 ` Haavard Skinnemoen [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=20090114164258.6373db9d@hskinnemoen-d830 \
--to=haavard.skinnemoen@atmel.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anemo@mba.ocn.ne.jp \
--cc=itai.levi.devel@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=marc.pignat@hevs.ch \
/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