From: Greg KH <gregkh@suse.de>
To: Philippe Langlais <philippe.langlais@stericsson.com>
Cc: linux-serial@vger.kernel.org, linux@treblig.org,
STEricsson_nomadik_linux@list.st.com,
loic.pallardy@stericsson.com, vincent.guittot@stericsson.com
Subject: Re: [PATCH] serial: fix port type conflict between NS16550A & U6_16550A
Date: Tue, 31 Aug 2010 06:29:06 -0700 [thread overview]
Message-ID: <20100831132906.GA2429@suse.de> (raw)
In-Reply-To: <1283257149-3370-1-git-send-email-philippe.langlais@stericsson.com>
On Tue, Aug 31, 2010 at 02:19:09PM +0200, Philippe Langlais wrote:
> Bug seen by Dr. David Alan Gilbert with sparse
sparse found this? nice.
But odds are we should switch this to an enum to try to find it earlier,
right?
I'll go queue this up.
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-31 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 12:19 [PATCH] serial: fix port type conflict between NS16550A & U6_16550A Philippe Langlais
2010-08-31 13:29 ` Greg KH [this message]
2010-08-31 18:11 ` Dr. David Alan Gilbert
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=20100831132906.GA2429@suse.de \
--to=gregkh@suse.de \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux@treblig.org \
--cc=loic.pallardy@stericsson.com \
--cc=philippe.langlais@stericsson.com \
--cc=vincent.guittot@stericsson.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).