From: "O.Sezer" <sezeroz@ttnet.net.tr>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.4.28-pre1] more gcc3.4 inline fixes [9/10] [3/4]
Date: Thu, 26 Aug 2004 02:09:12 +0300 [thread overview]
Message-ID: <412D1C18.2050709@ttnet.net.tr> (raw)
Marcelo:
Initially some non-inline/non-gcc34 related backports
sneaked in the original patch and this was why I splitted
the patch up.
These hunk are, as they're labelled, fixes from 2.6 while
we are working on the intermezzo directory: While hunting
for the many changes for the intermezzo inline fixes in
the other trees, I also caught these ones and thought that
you may be interested in them.
Feel free to apply or dump them.
Ozkan
On Mon, Aug 23, 2004 at 08:15:28PM +0300, O.Sezer wrote:
> splitted-up the fs/* gcc3.4-inline-patches.
>
> [3/4] intermezzo, while we're here
>
>
Ozkan,
What is this about?
I can't understand this as trivial gcc3.4 inline fixes.
next reply other threads:[~2004-08-25 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 23:09 O.Sezer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-23 17:15 [PATCH] [2.4.28-pre1] more gcc3.4 inline fixes [9/10] [3/4] O.Sezer
2004-08-25 11:08 ` 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=412D1C18.2050709@ttnet.net.tr \
--to=sezeroz@ttnet.net.tr \
--cc=linux-kernel@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