From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/5] Warp Base Platform
Date: Fri, 11 Jan 2008 21:52:16 -0500 [thread overview]
Message-ID: <47882B60.8060803@pikatech.com> (raw)
In-Reply-To: <20080112134005.a262c95c.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Sean,
>
> On Fri, 11 Jan 2008 18:39:15 -0500 Sean MacLennan <smaclennan@pikatech.com> wrote:
>
>> +++ arch/powerpc/platforms/44x/warp-nand.c 2008-01-11 18:04:10.000000000 -0500
>> @@ -0,0 +1,85 @@
>>
>
> You need a copyright/license notice.
>
> The only other concern I have left is the extern in the C file, but that
> can be dealt with later.
>
>
Oops, meant to reply to everybody. Thanks for the copyright catch. Do I
need the GPL blurb, or is just a copyright ok? I notice Linux does not
seem to put the GPL blurb. For example sched.c.
And I also don't like the extern, but I don't see a good solution right now.
And while I have everybody's attention... The FPGA contains a simple
watchdog timer. Would it be ok to put that in the platform/44x/warp.c
file? It is a bit too specific to the taco to ever be accepted in the
drivers/watchdog. Or I could do a warp-watchdog.c .
Cheers,
Sean
next prev parent reply other threads:[~2008-01-12 2:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 20:19 [PATCH 1/5] Warp Base Platform Sean MacLennan
2008-01-09 20:21 ` [PATCH 2/5] Warp Base Platform - dts Sean MacLennan
2008-01-10 2:47 ` David Gibson
2008-01-10 3:14 ` Sean MacLennan
2008-01-10 3:17 ` Josh Boyer
2008-01-10 3:33 ` Sean MacLennan
2008-01-10 3:35 ` David Gibson
2008-01-10 3:36 ` Josh Boyer
2008-01-10 23:59 ` Sean MacLennan
2008-01-11 0:20 ` David Gibson
2008-01-11 5:21 ` Sean MacLennan
2008-01-11 5:32 ` David Gibson
2008-01-11 6:15 ` Sean MacLennan
2008-01-11 17:54 ` Josh Boyer
2008-01-11 23:27 ` Sean MacLennan
2008-01-12 6:13 ` Stefan Roese
2008-01-12 20:32 ` Sean MacLennan
2008-01-09 20:22 ` [PATCH 3/5] Warp Base Platform Sean MacLennan
2008-01-10 2:49 ` David Gibson
2008-01-10 3:17 ` Sean MacLennan
2008-01-10 3:29 ` David Gibson
2008-01-11 0:04 ` Sean MacLennan
2008-01-11 6:17 ` Sean MacLennan
2008-01-11 17:56 ` Josh Boyer
2008-01-09 20:23 ` [PATCH 4/5] Warp Base Platform - defconfig Sean MacLennan
2008-01-09 20:25 ` [PATCH 5/5] Warp Base Platform - cputable Sean MacLennan
2008-01-11 6:21 ` [PATCH 1/5] Warp Base Platform Sean MacLennan
2008-01-11 6:42 ` Stephen Rothwell
2008-01-11 7:10 ` Sean MacLennan
2008-01-11 10:02 ` Stephen Rothwell
2008-01-11 16:26 ` Sean MacLennan
2008-01-11 17:51 ` Josh Boyer
2008-01-11 23:39 ` Sean MacLennan
2008-01-12 2:40 ` Stephen Rothwell
2008-01-12 2:52 ` Sean MacLennan [this message]
2008-01-12 3:00 ` Olof Johansson
2008-01-12 2:55 ` Sean MacLennan
2008-01-12 3:47 ` Olof Johansson
2008-01-12 2:59 ` Sean MacLennan
2008-01-12 6:23 ` Stefan Roese
2008-01-12 6:35 ` Sean MacLennan
2008-01-12 20:30 ` Sean MacLennan
2008-01-12 20:42 ` Sean MacLennan
2008-01-13 0:35 ` Stephen Rothwell
2008-01-14 17:18 ` Sean MacLennan
2008-01-16 23:29 ` Sean MacLennan
2008-01-16 23:36 ` Stephen Rothwell
2008-01-16 23:39 ` Josh Boyer
2008-01-21 17:55 ` Sean MacLennan
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=47882B60.8060803@pikatech.com \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.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).