public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Kay Sievers <kay.sievers@vrfy.org>,
	linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the driver-core tree
Date: Thu, 4 Dec 2008 21:42:14 +1100	[thread overview]
Message-ID: <18743.46086.609709.557371@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20081204042154.GA18027@kroah.com>

Greg KH writes:

> Yes, Paul, please apply the patch, and let me know.  It will make things
> much easier in the end for everyone involved.

Hmmm, I don't have it in my inbox, all I can find is an email from Kay
saying it had a problem.  Care to forward it to me?

Paul.

  reply	other threads:[~2008-12-04 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 23:44 linux-next: manual merge of the driver-core tree Stephen Rothwell
2008-12-04  4:21 ` Greg KH
2008-12-04 10:42   ` Paul Mackerras [this message]
2008-12-04 18:00     ` Greg KH
2009-01-04 23:28   ` Stephen Rothwell
2009-01-05  4:36     ` Greg KH
2009-01-05  5:57       ` Stephen Rothwell

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=18743.46086.609709.557371@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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