From: Andi Kleen <ak@suse.de>
To: blaisorblade@yahoo.it
Cc: akpm@osdl.org, jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net, ak@suse.de
Subject: Re: [patch 1/1] x86_64: make string func definition work as intended
Date: Mon, 2 May 2005 18:41:14 +0200 [thread overview]
Message-ID: <20050502164114.GG7342@wotan.suse.de> (raw)
In-Reply-To: <20050501190851.5FD5B45EBB@zion>
> I agree this can be a bit kludgy, so if you want add another solution.
Patch is ok for me, but you have a good chance of having broken
other archs too due to the string.c changes. Probably needs some testing.
-Andi
next prev parent reply other threads:[~2005-05-02 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 19:08 [patch 1/1] x86_64: make string func definition work as intended blaisorblade
2005-05-02 16:41 ` Andi Kleen [this message]
[not found] ` <20050501155327.GX3592@stusta.de>
2005-05-02 19:36 ` Setting the hardware clock together with the system one(was: Re: [patch 1/1] x86_64: make string func definition work as intended) Blaisorblade
2005-05-02 22:00 ` Adrian Bunk
2005-05-03 7:21 ` [patch 1/1] x86_64: make string func definition work as intended Andrew Morton
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=20050502164114.GG7342@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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