From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: torvalds@linux-foundation.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, neilb@suse.de, bfields@redhat.com
Subject: Re: linux-next: build failure after merge of the final tree (linus' tree related)
Date: Mon, 29 Aug 2011 12:22:55 -0400 (EDT) [thread overview]
Message-ID: <20110829.122255.265886922137556485.davem@davemloft.net> (raw)
In-Reply-To: <20110829154704.776d9afeb0da5dacd958f5e9@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 29 Aug 2011 15:47:04 +1000
> I have applied this patch for today:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 29 Aug 2011 15:43:40 +1000
> Subject: [PATCH] sparc: Remove another reference to nfsservctl
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Applied, thanks Stephen.
next prev parent reply other threads:[~2011-08-29 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 5:47 linux-next: build failure after merge of the final tree (linus' tree related) Stephen Rothwell
2011-08-29 16:22 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-21 6:23 Stephen Rothwell
2012-03-30 3:31 linux-next: build failure after merge of the final tree (Linus' " Stephen Rothwell
2012-03-30 3:39 ` David Miller
2012-03-30 5:45 ` David Miller
2012-03-30 6:31 ` Stephen Rothwell
2011-06-17 5:38 Stephen Rothwell
2011-06-17 5:34 ` KAMEZAWA Hiroyuki
2011-01-15 2:34 linux-next: build failure after merge of the final tree (linus' " Stephen Rothwell
2011-01-15 13:19 ` Rafael J. Wysocki
2011-01-15 15:44 ` Stephen Rothwell
2011-01-15 20:01 ` Rafael J. Wysocki
2010-07-22 3:58 linux-next: build failure after merge of the final tree (Linus' " Stephen Rothwell
2010-05-28 5:08 linux-next: build failure after merge of the final tree (linus' " Stephen Rothwell
2010-05-28 12:50 ` Steven Rostedt
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=20110829.122255.265886922137556485.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bfields@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sfr@canb.auug.org.au \
--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