From: Joshua Kinard <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: FIX ME in mc146818rtc.h
Date: Sat, 12 Jul 2014 02:59:48 -0400 [thread overview]
Message-ID: <53C0DCE4.7010906@gentoo.org> (raw)
In-Reply-To: <CAPDOMVhOpxBrjJNxM7wbomvmwe9Mxb+vh0zvsEA0bd6b0XNQNA@mail.gmail.com>
On 07/12/2014 01:50, Nick Krause wrote:
> Hey Ralf and other Mips developers ,
> I was wondering about the fix me in this file and how you want to fix this.
> Cheers Nick
>
# find . -name mc146818rtc.h
./include/linux/mc146818rtc.h
./arch/alpha/include/asm/mc146818rtc.h
./arch/mips/include/asm/mach-loongson/mc146818rtc.h
./arch/mips/include/asm/mach-rm/mc146818rtc.h
./arch/mips/include/asm/mach-jazz/mc146818rtc.h
./arch/mips/include/asm/mach-malta/mc146818rtc.h
./arch/mips/include/asm/mach-ip32/mc146818rtc.h
./arch/mips/include/asm/mach-dec/mc146818rtc.h
./arch/mips/include/asm/mc146818rtc.h
./arch/mips/include/asm/mach-generic/mc146818rtc.h
./arch/m32r/include/asm/mc146818rtc.h
./arch/frv/include/asm/mc146818rtc.h
./arch/parisc/include/asm/mc146818rtc.h
./arch/arm/include/asm/mc146818rtc.h
./arch/sh/include/asm/mc146818rtc.h
./arch/powerpc/include/asm/mc146818rtc.h
./arch/m68k/include/asm/mc146818rtc.h
./arch/mn10300/include/asm/mc146818rtc.h
./arch/ia64/include/asm/mc146818rtc.h
./arch/x86/include/asm/mc146818rtc.h
./arch/sparc/include/asm/mc146818rtc.h
Which copy are you referring to?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
prev parent reply other threads:[~2014-07-12 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 5:50 FIX ME in mc146818rtc.h Nick Krause
2014-07-12 6:59 ` Joshua Kinard [this message]
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=53C0DCE4.7010906@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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