From: Nick Piggin <npiggin@kernel.dk>
To: Valdis.Kletnieks@vt.edu
Cc: Nick Piggin <npiggin@kernel.dk>,
linux-kernel@vger.kernel.org, linux-fs@vger.kernel.org
Subject: Re: 2.6.37-next problems with fs dcache patches.
Date: Tue, 4 Jan 2011 16:54:37 +1100 [thread overview]
Message-ID: <20110104055437.GB3402@amd> (raw)
In-Reply-To: <19902.1293047238@localhost>
On Wed, Dec 22, 2010 at 02:47:18PM -0500, Valdis.Kletnieks@vt.edu wrote:
> And we end with:
>
> git bisect skip
> There are only 'skip'ped commits left to test.
> The first bad commit could be any of:
> 1f42f4566770e4d7bda4be9bfc0f39a237685f54
> 40f9b00323a73859ac53d7d4f2f820c4c8d33165
> 27056795db2de7bfefc5ea5cbc4486ba8f3fe90d
> ff7f5c4c2c1542cd8a8c538b11441aac47d87709
> 3c884da2830985495ddbc8817871070cb6e9d86d
> c06020c90ab49382419e71f87ed341d28f87a166
> 0c259f9c9ee263a5d907030e29c52fd8d206c631
> We cannot bisect more!
>
> Any ideas? Patches that weren't in linux-next as of 12-17?
Hi, sorry for the late reply. I should have since fixed up the
bisectability errors (including this one) in the tree. Please
report if there are any more, and apologes for messing up your
testing.
Thanks,
Nick
prev parent reply other threads:[~2011-01-04 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 19:47 2.6.37-next problems with fs dcache patches Valdis.Kletnieks
2011-01-04 5:54 ` Nick Piggin [this message]
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=20110104055437.GB3402@amd \
--to=npiggin@kernel.dk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-fs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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