From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Bernard, f6bvp" <f6bvp@free.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: [PATCH 0/7] ROSE: Misc fixes
Date: Wed, 20 Jul 2011 18:59:50 +0100 [thread overview]
Message-ID: <20110720175950.GA13753@linux-mips.org> (raw)
In-Reply-To: <4E270D35.9070306@free.fr>
On Wed, Jul 20, 2011 at 07:15:33PM +0200, Bernard, f6bvp wrote:
> All seven patch applied.
> However there are compile errors in rose_route.c
>
> f6bvp-8 linux]# make modules
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALL scripts/checksyscalls.sh
> CC [M] net/rose/af_rose.o
> CC [M] net/rose/rose_dev.o
> CC [M] net/rose/rose_in.o
> CC [M] net/rose/rose_link.o
> CC [M] net/rose/rose_loopback.o
> CC [M] net/rose/rose_out.o
> CC [M] net/rose/rose_route.o
> net/rose/rose_route.c: In function ‘rose_add_node’:
> net/rose/rose_route.c:104: erreur: incompatible type for argument 2
> of ‘atomic_add_return’
> /usr/src/linux-2.6.39/arch/x86/include/asm/atomic.h:173: note:
> expected ‘struct atomic_t *’ but argument is of type ‘atomic_t’
> net/rose/rose_route.c: In function ‘rose_add_loopback_neigh’:
> net/rose/rose_route.c:391: erreur: incompatible type for argument 2
> of ‘atomic_add_return’
> /usr/src/linux-2.6.39/arch/x86/include/asm/atomic.h:173: note:
> expected ‘struct atomic_t *’ but argument is of type ‘atomic_t’
> make[2]: *** [net/rose/rose_route.o] Erreur 1
> make[1]: *** [net/rose] Erreur 2
> make: *** [net] Erreur 2
Odd, the timestamps of my build tree must have been scrambled. I
get the same error messages but only after a full make clean and the
error is quite obvious.
I'm going to send a replacement match for the defective patch in
a minute.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-20 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 9:00 [PATCH 0/7] ROSE: Misc fixes Ralf Baechle
2011-07-20 0:21 ` [PATCH 2/7] NET: ROSE: Factor our common code from functions Ralf Baechle
2011-07-20 0:21 ` [PATCH 1/7] NET: ROSE: Fix race in SIOCRSSL2CALL ioctl accessing userspace Ralf Baechle
2011-07-20 0:37 ` [PATCH 3/7] NET: ROSE: Protect rose_callsign with a spinlock Ralf Baechle
2013-08-06 17:57 ` [PATCH] ax25tools mheard : don't display empty records f6bvp@free
2013-08-07 8:17 ` Thomas Osterried
2013-08-07 10:06 ` f6bvp@free
2013-08-09 8:10 ` Thomas Osterried
2011-07-20 8:11 ` [PATCH 4/7] NET: ROSE: Make neighbour->use atomic Ralf Baechle
2011-07-20 8:11 ` [PATCH 5/7] NET: ROSE: Make rose_neigh_no atomic Ralf Baechle
2011-07-20 18:09 ` [PATCH v2 " Ralf Baechle
2011-07-20 8:11 ` [PATCH 6/7] NET: ROSE: Move return statements hidden behind an if to their own line Ralf Baechle
2011-07-20 8:11 ` [PATCH 7/7] NET: ROSE: Fix formatting Ralf Baechle
2011-07-20 17:15 ` [PATCH 0/7] ROSE: Misc fixes Bernard, f6bvp
2011-07-20 17:59 ` Ralf Baechle DL5RB [this message]
2011-07-22 9:10 ` Bernard, f6bvp
2011-07-22 10:56 ` Ralf Baechle DL5RB
2011-07-22 16:12 ` f6bvp
2011-07-23 13:28 ` Ralf Baechle DL5RB
2011-07-29 22:32 ` f6bvp
2011-08-08 13:40 ` f6bvp
2011-08-08 14:06 ` Ralf Baechle
2011-08-08 15:33 ` f6bvp
2011-08-19 13:07 ` f6bvp
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=20110720175950.GA13753@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=f6bvp@free.fr \
--cc=linux-hams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.