From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Sachin Kamat <spk.linux@gmail.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 4
Date: Fri, 4 Jul 2014 20:48:47 -0400 [thread overview]
Message-ID: <20140705004846.GA11659@fieldses.org> (raw)
In-Reply-To: <20140705011058.198ae810@canb.auug.org.au>
On Sat, Jul 05, 2014 at 01:10:58AM +1000, Stephen Rothwell wrote:
> Hi Sachin,
>
> On Fri, 4 Jul 2014 14:12:11 +0530 Sachin Kamat <spk.linux@gmail.com> wrote:
> >
> > Was bisecting a kernel crash on Arndale octa board (Exynos5420). It
> > points to a merge
> > commit:
> > 40556a4c485d12d324f1ea196cc30f590e564237 is the first bad commit
> > ("Merge remote-tracking branch 'nfsd/nfsd-next'").
> >
> > How do I proceed with this?
>
> I guess we get the owner of the tree (possibly) in question involved
> (cc'd).
Looking at the total diffstat for that branch, it's almost all contained
in fs/nfsd with a little in include/linux/sunrpc/ and net/sunrpc. So
it's extremely unlikely that it would be causing a problem unless you're
actually testing nfsd.
> You should also post your information about the crash you are
> diagnosing as others may have seen it as well - or know what may cause
> it.
Yes, please.
--b.
next prev parent reply other threads:[~2014-07-05 0:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 6:42 linux-next: Tree for Jul 4 Stephen Rothwell
2014-07-04 8:42 ` Sachin Kamat
2014-07-04 15:10 ` Stephen Rothwell
2014-07-05 0:48 ` J. Bruce Fields [this message]
2014-07-05 14:57 ` Sachin Kamat
2014-07-06 4:54 ` Nick Krause
2014-07-06 5:17 ` Nick Krause
2014-07-06 5:21 ` Nick Krause
2014-07-06 5:34 ` Nick Krause
2014-07-06 5:42 ` Nick Krause
2014-07-05 14:56 ` Sachin Kamat
-- strict thread matches above, loose matches on Subject: below --
2023-07-04 3:43 Stephen Rothwell
2022-07-04 8:21 Stephen Rothwell
2019-07-04 12:09 Stephen Rothwell
2019-07-04 12:24 ` Stephen Rothwell
2019-07-04 12:40 ` Greg Kroah-Hartman
2019-07-06 8:34 ` Greg Kroah-Hartman
2019-07-06 9:44 ` Stephen Rothwell
2019-07-06 9:46 ` Greg Kroah-Hartman
2019-07-06 10:17 ` Stephen Rothwell
2019-07-06 14:33 ` Greg Kroah-Hartman
2019-07-06 15:42 ` Greg Kroah-Hartman
2018-07-04 5:57 Stephen Rothwell
2017-07-04 5:44 Stephen Rothwell
2016-07-04 8:43 Stephen Rothwell
2013-07-04 6:06 Stephen Rothwell
2013-07-04 7:41 ` Sedat Dilek
2013-07-04 8:21 ` Sedat Dilek
2013-07-04 8:40 ` Sedat Dilek
2013-07-04 8:45 ` Andrew Morton
2013-07-04 9:12 ` Sedat Dilek
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=20140705004846.GA11659@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=spk.linux@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).