All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Several patches agains linuxppc_devel-2.4.19-pre8
Date: Thu, 16 May 2002 11:26:33 +0200	[thread overview]
Message-ID: <3CE37B49.6000508@elsoft.ch> (raw)
In-Reply-To: 20020515155200.GN721@opus.bloom.county


Tom Rini schrieb:
> On Wed, May 15, 2002 at 01:35:55PM +0200, "David M?ller (ELSOFT AG)" wrote:
>
>
>>The attached patch fixes the following issues:
>
>
> Looks good, except:
> Don't #ifdef externs, if they aren't used it's OK.
> Since this code only has to work in recent'ish kernels (in reality only
> 'current' kernels) don't bother with the
> #ifdef MODULE_LICENSE
> ...
> #endif
>
> Just use it.
>

I have copied the MODULE_LICENSE stuff from another driver.
Does anybody knows if this feature is tagged to be a remove candiate in
future kernels and/or in the modutils?


Another question:

I've noticed that (at least) the following files have their executable
bit set, although they are simple C source files.
./include/asm-ppc/ppc405_dma.h
./arch/ppc/kernel/ppc405_dma.c
./arch/ppc/kernel/ppc405_pci.c
./arch/ppc/kernel/ppc4xx_setup.c
./arch/ppc/platforms/walnut.c
./arch/ppc/platforms/cpc700_pic.c

On the other hand, the PPCBoot kernel packer script in
./arch/ppc/boot/utils/mkimage.wrapper have the exec bit cleared.

Is it a bit task to fix this?


Dave


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-05-16  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 11:35 [PATCH] Several patches agains linuxppc_devel-2.4.19-pre8 "David Müller (ELSOFT AG)"
2002-05-15 15:52 ` Tom Rini
2002-05-16  9:26   ` "David Müller (ELSOFT AG)" [this message]
2002-05-16 13:56     ` Tom Rini
2002-05-17  6:31       ` "David Müller (ELSOFT AG)"
2002-05-17 12:59 ` "David Müller (ELSOFT AG)"

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=3CE37B49.6000508@elsoft.ch \
    --to=d.mueller@elsoft.ch \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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.