From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Nick Desaulniers <nick.desaulniers@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Avoid enum conversion warning (rev2)
Date: Mon, 27 Nov 2017 12:26:16 +0200 [thread overview]
Message-ID: <1511778376.4627.23.camel@linux.intel.com> (raw)
In-Reply-To: <CAH7mPvghJgSYYEKCd9SS3eESf7wygHeJanRr+FdUi9NB4q29oQ@mail.gmail.com>
On Sun, 2017-11-26 at 20:40 -0800, Nick Desaulniers wrote:
> Do I need to be basing my patches on a different tree than Linus'? In
> general, how do people find what tree they should be basing their
> patch off of?
"T:" line from the MAINTAINERS entry would tell you that.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-27 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 7:41 enum conversion warnings Nick Desaulniers
2017-11-23 7:50 ` [PATCH] drm/i915: Avoid enum conversion warning Nick Desaulniers
2017-11-23 7:50 ` Nick Desaulniers
2017-11-23 7:59 ` Daniel Vetter
2017-11-23 7:59 ` [Intel-gfx] " Daniel Vetter
2017-11-27 3:49 ` [PATCH v2] " Nick Desaulniers
2017-11-27 3:49 ` Nick Desaulniers
2017-11-27 10:21 ` Daniel Vetter
2017-11-27 10:21 ` Daniel Vetter
2017-11-23 8:58 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-11-23 11:51 ` Arkadiusz Hiler
2017-11-23 11:41 ` Patchwork
2017-11-23 14:12 ` Patchwork
2017-11-27 3:52 ` ✗ Fi.CI.BAT: failure for drm/i915: Avoid enum conversion warning (rev2) Patchwork
2017-11-27 4:40 ` Nick Desaulniers
2017-11-27 10:26 ` Joonas Lahtinen [this message]
2017-11-28 7:17 ` Nick Desaulniers
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=1511778376.4627.23.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nick.desaulniers@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 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.