dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: daniel.vetter@ffwll.ch, DRI <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/9] make struct drm_mm_node embeddable
Date: Sun, 14 Nov 2010 18:52:35 +0100	[thread overview]
Message-ID: <AANLkTimUqcDN-HEOKL+v=C5Uv9Yh=4ZTkHf9=y0oPHLv@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimoYKi5Q7T320s_eQigr34-RKvhX6ow7Q0j6O3T@mail.gmail.com>

On Sun, Nov 14, 2010 at 6:27 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> On Sun, Nov 14, 2010 at 6:14 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote:
>>> If you could geneate a patchset w/o i915 parts for testing would be cool.
>>> Thanks in advance.
>>
>> Just drop patches 5-9 (you can apply patch 8 without any problems, it's
>> just not gonna do anything without patch 9 ;). After all, this patch
>> series is supposed to be bisectable, so stopping anywhere in between
>> should result in a working kernel.
>>
>> -Daniel
>> --
>> Daniel Vetter
>> Mail: daniel@ffwll.ch
>> Mobile: +41 (0)79 365 57 48
>>
>
> Njet :-(
>
> I am cloning linux-next GIT and pull into drm-next to see if there is
> sth. missing.
>
> - Sedat -
>

NOPE, linux-next is up-to-date what drm-next concerns.

- Sedat -

sd@tbox:/mnt/sdb5/linux-kernel$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Cloning into linux-next...
remote: Counting objects: 3084175, done.
remote: Compressing objects: 100% (404388/404388), done.
remote: Total 3084175 (delta 2687481), reused 3050014 (delta 2653407)
Receiving objects: 100% (3084175/3084175), 513.53 MiB | 566 KiB/s, done.
Resolving deltas: 100% (2687481/2687481), done.

sd@tbox:/mnt/sdb5/linux-kernel$ tar -cf
files/linux-next_git_next-20101112.tar linux-next/

sd@tbox:/mnt/sdb5/linux-kernel$ cd linux-next/

sd@tbox:/mnt/sdb5/linux-kernel/linux-next$ git pull
git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
drm-next
>From git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
 * branch            drm-next   -> FETCH_HEAD
Already up-to-date.

  reply	other threads:[~2010-11-14 17:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 14:03 [PATCH 0/9] make struct drm_mm_node embeddable Sedat Dilek
2010-11-14 14:38 ` Chris Wilson
2010-11-14 15:52   ` Sedat Dilek
2010-11-14 16:13     ` Daniel Vetter
2010-11-14 16:56       ` Sedat Dilek
2010-11-14 17:14         ` Daniel Vetter
2010-11-14 17:27           ` Sedat Dilek
2010-11-14 17:52             ` Sedat Dilek [this message]
2010-11-14 18:14               ` Daniel Vetter
2010-11-14 18:19                 ` Sedat Dilek
2010-11-14 18:31                 ` Sedat Dilek
2010-11-14 18:54                   ` Daniel Vetter
2010-11-14 19:55                     ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2010-11-15 10:31 Sedat Dilek
2010-11-12 17:36 Daniel Vetter
2010-11-12 17:56 ` Chris Wilson
2010-11-15  7:58 ` Thomas Hellstrom
2010-11-15 19:45   ` Daniel Vetter
2010-11-15 20:40     ` Thomas Hellstrom
2010-11-15 20:54       ` Daniel Vetter

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='AANLkTimUqcDN-HEOKL+v=C5Uv9Yh=4ZTkHf9=y0oPHLv@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sedat.dilek@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).