public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [git] m68k
Date: Tue, 02 Dec 2008 17:52:04 -0500	[thread overview]
Message-ID: <4935BC14.5060109@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812022117160.24347@anakin>

Geert Uytterhoeven wrote:
> 	Hi Linus,
> 
> [ First pull request, let's hope I got everything right... ]
> 
> Please pull from
> 
>     git://git.kernel.org:/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
> 
> to receive the following m68k-related updates for 2.6.28:
> 
> Finn Thain (1):
>       macfb: Do not overflow fb_fix_screeninfo.id
> 
> Geert Uytterhoeven (1):
>       m68k: Update defconfigs for 2.6.28-rc7
> 
>  arch/m68k/configs/amiga_defconfig    |  126 +++++++++++++++++++--------------
>  arch/m68k/configs/apollo_defconfig   |  115 +++++++++++++++++-------------
>  arch/m68k/configs/atari_defconfig    |  130 +++++++++++++++++++---------------
>  arch/m68k/configs/bvme6000_defconfig |  112 +++++++++++++++++-------------
>  arch/m68k/configs/hp300_defconfig    |  115 +++++++++++++++++-------------
>  arch/m68k/configs/mac_defconfig      |  125 ++++++++++++++++++--------------
>  arch/m68k/configs/multi_defconfig    |  129 +++++++++++++++++++---------------
>  arch/m68k/configs/mvme147_defconfig  |  112 +++++++++++++++++-------------
>  arch/m68k/configs/mvme16x_defconfig  |  112 +++++++++++++++++-------------
>  arch/m68k/configs/q40_defconfig      |  125 +++++++++++++++++++--------------
>  arch/m68k/configs/sun3_defconfig     |  124 +++++++++++++++++++-------------
>  arch/m68k/configs/sun3x_defconfig    |  115 +++++++++++++++++-------------
>  drivers/video/macfb.c                |   74 +++++++++----------
>  13 files changed, 863 insertions(+), 651 deletions(-)

As a peer git user...  Looks pretty good to me, though I would suggest 
including the overall diff in the email [provided it is under 400k]. 
One last chance for review never hurts, especially during the -rc period.

	Jeff




  reply	other threads:[~2008-12-02 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 20:22 [git] m68k Geert Uytterhoeven
2008-12-02 22:52 ` Jeff Garzik [this message]
2008-12-03  8:03   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2008-12-28 19:15 Geert Uytterhoeven
2009-01-12 20:12 Geert Uytterhoeven
2009-03-26 20:34 Geert Uytterhoeven
2009-04-23 18:37 Geert Uytterhoeven

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=4935BC14.5060109@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=torvalds@linux-foundation.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