From: "O.Sezer" <sezeroz@ttnet.net.tr>
To: linux-kernel@vger.kernel.org
Cc: marcelo.tosatti@cyclades.com
Subject: Re: [PATCH] [2.4.28-pre1] more gcc3.4 inline fixes [2/10]
Date: Mon, 23 Aug 2004 16:23:18 +0300 [thread overview]
Message-ID: <4129EFC6.1@ttnet.net.tr> (raw)
> mxser_interrupt() is not inline, why are messing around with it?
it calls mxser_transmit_chars and if it's not moved after it
my gcc failed. (I admit the patches become messy if inlines
are simply not removed but I didn't want to do such changes
where possible).
next reply other threads:[~2004-08-23 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 13:23 O.Sezer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 15:14 [PATCH] [2.4.28-pre1] more gcc3.4 inline fixes [2/10] O.Sezer
2004-08-23 11:49 ` Marcelo Tosatti
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=4129EFC6.1@ttnet.net.tr \
--to=sezeroz@ttnet.net.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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