public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: schmitz <schmitz@biophys.uni-duesseldorf.de>
To: Brad Boyer <flar@allandria.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: m68k-queue
Date: Sat, 18 May 2013 20:38:26 +1200	[thread overview]
Message-ID: <51973E02.6090302@biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <20130518070910.GA26647@cynthia.pants.nu>

Brad,

>> https://git.kernel.org/cgit/linux/kernel/git/geert/linux-m68k.git/log/?h=m68k-queue
>> and click on the commit you're interested in.
>>     
>
> Thank you. I took a look, and I agree with everyone else that this was a
> legacy patch that isn't required.
>
> The original idea was to use the same API for both real ADB requests and
> everything else that goes through the PMU, Egret, or CUDA chips. This
> includes not only RTC/PRAM management, but power control and several
> other things as well. It wasn't such a great idea, honestly.
>   
I'm sure it was one of these 'how can we get some piece of code reused 
to do something almost entirely unrelated' ideas. Sounds like what I'd 
have done just to solve the hwclock handling and get on with hacking 
other stuff without being irritated by constant fscks ...

Code quality has improved a huge lot since. Keep in mind that mac68k was 
developed separate from m68k in the beginning. I have never had Alan's 
instinct for writing good clean code, 'it works' was usually good enough.

Cheers,

    Michael

  reply	other threads:[~2013-05-18  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  9:56 m68k-queue Geert Uytterhoeven
2013-05-14  8:56 ` m68k-queue schmitz
2013-05-15  5:45   ` m68k-queue Brad Boyer
2013-05-15  6:53     ` m68k-queue Geert Uytterhoeven
2013-05-18  7:09       ` m68k-queue Brad Boyer
2013-05-18  8:38         ` schmitz [this message]
2013-05-18 17:53           ` m68k-queue Brad Boyer
2013-05-15  8:47   ` m68k-queue Finn Thain
2013-05-15 22:10     ` m68k-queue Michael Schmitz
2013-05-16  2:55       ` m68k-queue Finn Thain
2013-05-16 22:40         ` m68k-queue Michael Schmitz
2013-05-18  1:48           ` m68k-queue Finn Thain
2013-05-18  5:53             ` m68k-queue Michael Schmitz
2013-05-18  6:28             ` m68k-queue Andreas Schwab
2013-05-18  7:03               ` m68k-queue Geert Uytterhoeven
2013-05-18  7:50           ` m68k-queue Brad Boyer

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=51973E02.6090302@biophys.uni-duesseldorf.de \
    --to=schmitz@biophys.uni-duesseldorf.de \
    --cc=flar@allandria.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox