From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Harry Wentland <harry.wentland@amd.com>,
"Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"Sharma, Swati2" <swati2.sharma@intel.com>
Cc: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Subject: Re: [Intel-gfx] [V2 3/3] drm/amd/display: Move connector debugfs to drm
Date: Wed, 18 May 2022 11:08:47 +0530 [thread overview]
Message-ID: <7a61da79-90ac-b4e2-d06d-758616b12855@intel.com> (raw)
In-Reply-To: <87mtfhhnx4.fsf@intel.com>
On Mon-16-05-2022 02:09 pm, Jani Nikula wrote:
> On Mon, 02 May 2022, Harry Wentland <harry.wentland@amd.com> wrote:
>> Both the kernel and IGT series look good to me.
>>
>> I recommend you merge the entire kernel set as one into drm-next. We
>> can pull it into amd-staging-drm-next so as not to break our CI once
>> the IGT patches land.
@Harry
Can we have your Ack-by to merge this series via drm-misc-next?
IGT patches are already landed. :-)
- Bhanu
>
> Can we read that as an ack to merge via drm-misc-next? :)
>
> BR,
> Jani.
>
>
next prev parent reply other threads:[~2022-05-18 5:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:51 [V2 0/3] Expose max and current bpc via debugfs Bhanuprakash Modem
2022-04-11 9:51 ` [V2 1/3] drm/debug: Expose connector's max supported " Bhanuprakash Modem
2022-04-12 3:07 ` [Intel-gfx] " Murthy, Arun R
2022-04-12 4:03 ` Modem, Bhanuprakash
2022-04-29 14:27 ` Murthy, Arun R
2022-05-02 11:49 ` Jani Nikula
2022-05-02 18:51 ` Harry Wentland
2022-04-11 9:51 ` [V2 2/3] drm/i915/display/debug: Expose crtc current " Bhanuprakash Modem
2022-04-12 3:10 ` [Intel-gfx] " Murthy, Arun R
2022-05-16 8:39 ` Jani Nikula
2022-04-11 9:51 ` [V2 3/3] drm/amd/display: Move connector debugfs to drm Bhanuprakash Modem
2022-04-29 14:32 ` [Intel-gfx] " Murthy, Arun R
2022-05-02 13:28 ` Modem, Bhanuprakash
2022-05-02 13:38 ` Harry Wentland
2022-05-02 14:27 ` Modem, Bhanuprakash
2022-05-02 14:29 ` Harry Wentland
2022-05-02 18:54 ` Harry Wentland
2022-05-16 8:39 ` Jani Nikula
2022-05-18 5:38 ` Modem, Bhanuprakash [this message]
2022-05-18 14:08 ` Harry Wentland
2022-05-02 18:51 ` Harry Wentland
2022-05-10 11:18 ` [V2 0/3] Expose max and current bpc via debugfs Modem, Bhanuprakash
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=7a61da79-90ac-b4e2-d06d-758616b12855@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=swati2.sharma@intel.com \
--cc=ville.syrjala@linux.intel.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).