From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, coda@cs.cmu.edu
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 25 (coda)
Date: Mon, 25 Oct 2010 16:33:39 -0700 [thread overview]
Message-ID: <20101025163339.a2ffca49.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101025145834.9b68e026.sfr@canb.auug.org.au>
On Mon, 25 Oct 2010 14:58:34 +1100 Stephen Rothwell wrote:
> Hi all,
The coda BKL fixes (git tree) are not in here yet, right?
fs/coda/* currently has 12 warnings like these:
fs/coda/psdev.c:140: error: implicit declaration of function 'lock_kernel'
fs/coda/psdev.c:142: error: implicit declaration of function 'unlock_kernel'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-25 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 3:58 linux-next: Tree for October 25 Stephen Rothwell
2010-10-25 3:59 ` Stephen Rothwell
2010-10-25 23:25 ` [PATCH -next] pch_can: depends on PCI Randy Dunlap
2010-10-25 23:47 ` David Miller
2010-10-25 23:33 ` Randy Dunlap [this message]
2010-10-25 23:52 ` linux-next: Tree for October 25 (coda) Stephen Rothwell
2010-10-25 23:51 ` linux-next: Tree for October 25 (acpi/apei-related) Randy Dunlap
2010-10-25 23:54 ` linux-next: Tree for October 25 (netfilter/xt_socket) Randy Dunlap
2010-10-26 5:02 ` David Miller
2010-10-25 23:55 ` linux-next: Tree for October 25 (netfilter/nf_conntrack_reasm) Randy Dunlap
2010-10-26 5:03 ` David Miller
2010-10-26 16:09 ` David Miller
2010-10-25 23:57 ` linux-next: Tree for October 25 (acpi_video) Randy Dunlap
2010-10-25 23:59 ` linux-next: Tree for October 25 (nouveau_pm) Randy Dunlap
2010-10-26 10:54 ` Martin Peres
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=20101025163339.a2ffca49.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=coda@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.