From: Jiri Slaby <jslaby@suse.cz>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: introduce up_to_u8250p() macro
Date: Mon, 14 Jul 2014 12:32:57 +0200 [thread overview]
Message-ID: <53C3B1D9.5020403@suse.cz> (raw)
In-Reply-To: <1405328191.5102.131.camel@smile.fi.intel.com>
On 07/14/2014 10:56 AM, Andy Shevchenko wrote:
> On Mon, 2014-07-14 at 10:47 +0200, Jiri Slaby wrote:
>> On 07/14/2014 10:41 AM, Andy Shevchenko wrote:
>>> It helps to convert struct uart_port to struct uart_8250_port.
>>
>> Hi, I don't know what conversion you mean (yet),
>
> Dynamic object casting if you like.
>
>> but could that be a
>> static inline instead of the macro?
>
> Yes, I could. Would like me to do so?
Yes, please.
--
js
suse labs
prev parent reply other threads:[~2014-07-14 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 8:41 [PATCH] serial: 8250: introduce up_to_u8250p() macro Andy Shevchenko
2014-07-14 8:47 ` Jiri Slaby
2014-07-14 8:56 ` Andy Shevchenko
2014-07-14 10:32 ` Jiri Slaby [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=53C3B1D9.5020403@suse.cz \
--to=jslaby@suse.cz \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-serial@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