From: Paul Bolle <pebolle@tiscali.nl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Steven Newbury <steve@snewbury.org.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing
Date: Fri, 07 Mar 2014 10:48:18 +0100 [thread overview]
Message-ID: <1394185698.5608.5.camel@x41> (raw)
In-Reply-To: <CAErSpo6uj_Kuk0_F97nRsnM1Pss4C7=HeEaVu6D-NwFFK=1cvA@mail.gmail.com>
Bjorn Helgaas schreef op ma 10-02-2014 om 14:33 [-0700]:
> I wouldn't start bisecting yet, but if you're in the mood, this
> commit: 96702be56037 "Merge branch 'pci/resource' into next" looks
> like a good place to start, so you could try the pre-merge commit:
> 04f982beb900 "Merge branch 'pci/msi' into next". If 04f982beb900 is
> good, there are only about 15 commits on the pci/resource branch to
> look at.
This might end up not being relevant. And this is surely documented
somewhere, but anyhow:
- what git magic returns the hashes of the 15 commits that merge commit
96702be56037 added to the tree; and
- how can I use the list of those hashes to limit the range of commits
to do a git bisect?
Paul Bolle
next prev parent reply other threads:[~2014-03-07 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 19:06 agp/intel: can't ioremap flush page - no chipset flushing Paul Bolle
2014-02-08 19:59 ` Daniel Vetter
2014-02-08 20:22 ` Paul Bolle
2014-02-09 0:02 ` Daniel Vetter
2014-02-09 13:15 ` [Intel-gfx] " Steven Newbury
2014-02-09 13:25 ` Paul Bolle
2014-02-09 13:32 ` Steven Newbury
2014-02-10 21:33 ` Bjorn Helgaas
2014-03-06 20:25 ` Paul Bolle
2014-03-06 21:38 ` Bjorn Helgaas
2014-03-07 20:33 ` Bjorn Helgaas
2014-03-07 9:48 ` Paul Bolle [this message]
2014-03-07 16:55 ` Bjorn Helgaas
2014-03-07 17:16 ` Paul Bolle
2014-03-07 20:40 ` Bjorn Helgaas
2014-03-07 21:03 ` Paul Bolle
2014-03-07 22:07 ` Bjorn Helgaas
2014-03-08 14:12 ` Bjorn Helgaas
2014-03-08 14:44 ` Paul Bolle
2014-03-10 18:24 ` Bjorn Helgaas
2014-03-10 23:45 ` Paul Bolle
2014-03-11 0:07 ` Bjorn Helgaas
2014-03-11 0:15 ` Paul Bolle
2014-03-11 2:07 ` Bjorn Helgaas
2014-03-11 9:20 ` Paul Bolle
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=1394185698.5608.5.camel@x41 \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=bhelgaas@google.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@snewbury.org.uk \
--cc=yinghai@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