Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH] reinstate mac rtc
Date: Tue, 14 Oct 2008 13:16:31 +1100 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0810141315010.4862@loopy.telegraphics.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0810132114590.6220@anakin>



On Mon, 13 Oct 2008, Geert Uytterhoeven wrote:

> Any of these I should still try to get into 2.6.28? Or is queueing for 
> 2.6.29 OK?
> 
> Not that there's any risk in breaking non-m68k stuff, but I'm just 
> feeling a bit like the bastard-maintainer-from-hell who's pointing out 
> people about merge windows and such ;-)
> 
> I hope to find some time soon to push the stuff queued for 2.6.28 to 
> Linus...

I don't mind.

I guess, if you think that there is something in there that might lead to 
merge conflicts later, perhaps you should send it now?

Finn

> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> 							    -- Linus Torvalds
> 

  reply	other threads:[~2008-10-14  2:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0810061855300.28882@loopy.telegraphics.com.au>
2008-10-13 19:21 ` [PATCH] reinstate mac rtc Geert Uytterhoeven
2008-10-14  2:16   ` Finn Thain [this message]
2008-10-14  7:30     ` Geert Uytterhoeven
2008-10-15 21:41   ` Riccardo
2008-10-16  1:02     ` Finn Thain
2008-10-16  6:49       ` Brad Boyer
2008-10-18 11:12         ` Riccardo
2008-10-18 17:39           ` Kolbjørn Barmen
2008-10-19  2:53             ` Finn Thain
2008-10-19 16:37               ` Kolbjørn Barmen
2008-10-20  2:03                 ` Finn Thain
2008-10-20  2:05                 ` Michael Schmitz
2008-10-20 19:13                   ` Laurent Vivier
2008-10-22  7:19                     ` Michael Schmitz
2008-10-22 11:09                       ` Kolbjørn Barmen
2008-10-22 22:14                         ` Laurent Vivier
2008-10-23  3:56                           ` Michael Schmitz
2008-10-23  7:28                             ` Geert Uytterhoeven
2008-10-23  7:39                               ` Geert Uytterhoeven
2008-10-24  2:49                                 ` Michael Schmitz
2008-10-25  4:24                               ` Michael Schmitz
2008-10-25  5:10                                 ` Finn Thain
2008-10-25  7:08                                   ` Finn Thain
2008-10-26  3:04                                   ` Michael Schmitz
2008-10-26  3:24                                     ` Finn Thain
2008-10-19 11:52           ` Finn Thain
2008-10-18 16:17       ` Riccardo

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=Pine.LNX.4.64.0810141315010.4862@loopy.telegraphics.com.au \
    --to=fthain@telegraphics.com.au \
    --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