From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Adding a couple of DSI panel fixes to drm-intel-fixes
Date: Wed, 14 Feb 2018 14:35:52 +0200 [thread overview]
Message-ID: <87606z695j.fsf@intel.com> (raw)
In-Reply-To: <6c5034a5-de52-cc45-1053-792a179cd721@redhat.com>
On Wed, 14 Feb 2018, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi All,
>
> I would like to a add a couple of DSI panel fixes from
> dinq to drm-intel-fixes (with the purpose of getting them
> into 4.16).
>
> What is the correct way to do this? Should I just do:
>
> dim checkout-branch drm-intel-fixes
> git pull
> git cherry-pick <hash1>
> git cherry-pick <hash2>
> dim push-branch drm-intel-fixes
>
> And that is it, or is there something special which
> I need to do, or ask someone who is taking care of this?
The maintainers take care of drm-intel-fixes and
drm-intel-next-fixes. In general, this mostly works automagically if you
add Fixes: or Cc: stable tags to the original commits.
Lacking those, please just send email to i915 maintainers with the
commit ids and we'll take of them.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-14 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 12:13 Adding a couple of DSI panel fixes to drm-intel-fixes Hans de Goede
2018-02-14 12:35 ` Jani Nikula [this message]
2018-02-14 12:55 ` Hans de Goede
2018-02-14 19:45 ` Rodrigo Vivi
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=87606z695j.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.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