From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: vikas gupta <vikas_gupta51013@yahoo.co.in>,
bcrl@kvack.org, linux-aio@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc6-xx-all.diff is not working for 2.6.13 arm kernel
Date: Mon, 3 Oct 2005 11:07:31 +0100 [thread overview]
Message-ID: <20051003100731.GB16717@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200510031227.34961.vda@ilport.com.ua>
On Mon, Oct 03, 2005 at 12:27:34PM +0300, Denis Vlasenko wrote:
> On Monday 03 October 2005 12:22, vikas gupta wrote:
> > hi ben ,
> >
> > I tried to apply 2.6.13-rc6-B0/B1-all.diff to
> > linux-2.6.13 kernel with arm support patches . It's
> > getting applied cleanly...
> > but while building the kernel i am getting some build
> > errors ...
> > i traced the problem and get that this error are
> > coming because of some machine specific files.
> > 1)arch/i386/kernel/semaphore.c
> > 2)include/asm-i386/seamphore.h
> >
> > So can you please tell me that whather any patch is
> > available, in order to support these implementation on
> > arm platform.
>
> How nice that you did not show the actual error message
> and did not show your .config
That's usual in the embedded world - it's a way that embedded folk seem
to write their bug reports to provoke a "response" (the content of the
response doesn't seem to matter, just as long as there is one.)
However, one also has to wonder - "2.6.13 kernel with arm support patches"
"arch/i386/kernel/semaphore.c". Why have "arm" patches been applied (and
what were they) and why i386 is being built.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-10-03 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 9:22 vikas gupta
2005-10-03 9:27 ` Denis Vlasenko
2005-10-03 10:07 ` Russell King [this message]
2005-10-03 10:55 ` vikas gupta
2005-10-03 11:04 ` Russell King
2005-10-03 15:03 ` Benjamin LaHaise
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=20051003100731.GB16717@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
--cc=vikas_gupta51013@yahoo.co.in \
/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
Powered by JetHome