From: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
To: Dmitry Kasatkin <dmitry.kasatkin@intel.com>
Cc: sparclinux@vger.kernel.org, viro@ZenIV.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix the sparc32 mpilib build mess.
Date: Thu, 02 Feb 2012 00:16:01 +0200 [thread overview]
Message-ID: <4F29B9A1.3090504@intel.com> (raw)
In-Reply-To: <20120126.173202.2207050843577467461.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
I am very sorry...
I was trying to test-forward saved patch mails, but it did work not like
I expected...
Try to find out how to forward email without TO and CC lists..
- Dmitry
On 02/02/2012 12:12 AM, Dmitry Kasatkin wrote:
> From: David Miller<davem@davemloft.net>
>
>
> The long and short of it is that the longlong.h header added by
> the mpilib code is quite old and out of date.
>
> Here I've solved the clz_tab[] multiple definition problem as
> well as the outdated udiv_qrnnd() definition, but long term
> we should probably have a more uptodate longlong.h header
> provides at include/linux/longlong.h to avoid this kind of
> stuff in the future.
>
> It's a part of the libgcc interface and therefore has no
> business being tucked down deep under lib/foo/ somewhere.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6339 bytes --]
prev parent reply other threads:[~2012-02-01 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 22:32 [PATCH 0/2] Fix the sparc32 mpilib build mess David Miller
2012-01-26 22:41 ` Kasatkin, Dmitry
2012-02-01 22:16 ` Dmitry Kasatkin [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=4F29B9A1.3090504@intel.com \
--to=dmitry.kasatkin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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