From: sjhill@realitydiluted.com
To: Jeroen Vreeken <pe1rxq@amsat.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] ADM5120 for 2.6.10
Date: Thu, 27 Jan 2005 15:01:31 -0600 (CST) [thread overview]
Message-ID: <E1CuGlf-0000cy-Pl@real.realitydiluted.com> (raw)
In-Reply-To: <41F9503E.5030004@amsat.org>
Greetings.
First, thank you for your patch. However, there are a number of things
that you have to do before it will be accepted.
1) You should be creating your patch against the Linux/MIPS kernel
tree present in CVS. You can go to http://www.linux-mips.org/
to see how to get the latest code.
2) Change your machine config definition of 'MIPS_AM5120' to be
'MIPS_ADM5120' as it makes more sense.
3) A number of your files, 'arch/mips/am5120/5120_rtc.c' for an
example, has an unacceptable copyright banner in it. Your code
will not be accepted unless it is licensed under GPL or a shared
BSD style license. Please speak with your management and get
approval. You will also need to sign off your code contribution.
4) It might be good to have your serial driver up in 'drivers/serial'
instead of down in 'arch/mips' somewhere. Perhaps someone else
will have comments on that.
5) Your PCI code should be located in 'arch/mips/pci'.
6) Your change to 'include/linux/init.h' for early init calls
is unnecessary. The latest tree already supports this and
the linker script takes care of placing them in the proper
section.
After you have addressed the issues above, please re-submit your patch.
Thanks!
-Steve
next prev parent reply other threads:[~2005-01-27 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 20:34 [PATCH] ADM5120 for 2.6.10 Jeroen Vreeken
2005-01-27 21:01 ` sjhill [this message]
2005-01-27 21:17 ` Jeroen Vreeken
2005-01-27 21:32 ` sjhill
2005-01-27 22:00 ` Jeroen Vreeken
2005-01-27 22:00 ` Jeroen Vreeken
2005-01-28 16:56 ` Tsang-Ren Chang
2005-01-28 17:03 ` sjhill
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=E1CuGlf-0000cy-Pl@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=linux-mips@linux-mips.org \
--cc=pe1rxq@amsat.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