From: Chen Liqin <liqin.chen@sunplusct.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [GIT PULL, v4] S+core architecture (arch/score) support
Date: Thu, 27 Aug 2009 11:28:59 +0800 [thread overview]
Message-ID: <1251343739.23810.24.camel@ad3ser01> (raw)
In-Reply-To: <200908261931.52645.arnd@arndb.de>
On Wed, 2009-08-26 at 19:31 +0200, Arnd Bergmann wrote:
> On Wednesday 26 August 2009, Chen Liqin (Gmail) wrote:
>
> Hi Liqin,
>
> Similarly, the split of your patches is good for review, but it
> is useless to have 33 commits in your changelog with just the
> file names listed in the history text.
I will remove these changelog from repository.
>
> What is missing OTOH is a description of changes you made since
> the last version you posted, which would be needed to help
> people that have already reviewed your code before.
> Also, you have dropped the descriptions of changes that I
> contributed, committing the changed files as your own. If you
> see a need to do that next time, please ask before you do it,
> or find a way to keep the original commit logs.
How can I add old commit logs to our repository?
Or add people's contribute to the log?
> What is the status of the port now? Do you have a working glibc
> and LTP test results, or are do you still need to fix more
> bugs that got introduced in the 2.6.30 port?
In fact, we still need define
__ARCH_WANT_SYSCALL_NO_AT,
__ARCH_WANT_SYSCALL_NO_FLAGS,
__ARCH_WANT_SYSCALL_OFF_T,
__ARCH_WANT_SYSCALL_DEPRECATED
to make linux/score running, glibc and applictions
need old syscall API.
And now it's really have some problems
in syscall interface part.
But if we use our old syscall interface replace the new one,
score platform will run well.
I am a little confused, whether or not I should commit
score code use new or old syscall part?
Best Regards
Liqin
next prev parent reply other threads:[~2009-08-27 4:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 5:58 [GIT PULL, v4] S+core architecture (arch/score) support Chen Liqin (Gmail)
2009-08-26 17:31 ` Arnd Bergmann
2009-08-27 3:28 ` Chen Liqin [this message]
2009-08-27 14:00 ` Arnd Bergmann
2009-08-31 7:48 ` liqin.chen
2009-08-31 9:56 ` Arnd Bergmann
2009-09-01 6:45 ` liqin.chen
2009-09-01 6:45 ` liqin.chen
-- strict thread matches above, loose matches on Subject: below --
2009-09-14 1:27 liqin.chen
2009-09-14 1:27 ` liqin.chen
2009-09-17 16:31 ` Linus Torvalds
2009-09-18 4:10 ` liqin.chen
2009-09-18 4:36 ` Linus Torvalds
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=1251343739.23810.24.camel@ad3ser01 \
--to=liqin.chen@sunplusct.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).