From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: linux-next@vger•kernel.org, prarit@redhat•com,
dhowells@redhat•com, kosaki.motohiro@jp•fujitsu.com,
linux-kernel@vger•kernel.org, linux-ia64@vger•kernel.org,
sam@ravnborg•org, kyle@mcmartin•ca, tony.luck@intel•com,
trond.myklebust@fys•uio.no
Subject: Re: linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error)
Date: Sat, 17 Jan 2009 09:49:03 +1100 [thread overview]
Message-ID: <20090117094903.bc0c646d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090117094008.5a0ce562.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi Andrew,
On Sat, 17 Jan 2009 09:40:08 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> > y:/usr/src/git26> who-committed.sh 2c3fb6b1b1a43ca089032e6523207f6687c962c1
>
> And that is one I committed myself because Linus' tree is broken.
It also appears as commit d992c8403a72c4067587a32a7736bcc2af6c408f in the
mfd tree but has not made it into Linus' tree yet.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-16 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090115200315.EBE3.KOSAKI.MOTOHIRO@jp.fujitsu.com>
[not found] ` <20090115093514.f3f6b8ff.akpm@linux-foundation.org>
2009-01-16 1:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 1:59 ` Andrew Morton
2009-01-16 2:49 ` Stephen Rothwell
2009-01-16 3:41 ` KOSAKI Motohiro
2009-01-16 4:34 ` Stephen Rothwell
2009-01-16 22:15 ` Andrew Morton
2009-01-16 22:40 ` Stephen Rothwell
2009-01-16 22:49 ` Stephen Rothwell [this message]
2009-01-16 22:51 ` Andrew Morton
2009-01-17 4:43 ` David Howells
2009-01-17 5:00 ` 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=20090117094903.bc0c646d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=kyle@mcmartin$(echo .)ca \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=prarit@redhat$(echo .)com \
--cc=sam@ravnborg$(echo .)org \
--cc=tony.luck@intel$(echo .)com \
--cc=trond.myklebust@fys$(echo .)uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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