From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: Brian Starkey <brian.starkey@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm/vkms: Use index instead of 0 in possible crtc
Date: Tue, 18 Jun 2019 18:51:17 -0300 [thread overview]
Message-ID: <CADKXj+4R=J0mEs3hYGiMS_iK+yhAZyXi_xOg-nRMtTAvSuCz2Q@mail.gmail.com> (raw)
In-Reply-To: <WQuF2MGabt8DxA1rdWhTcZIGSaXav-5XOae4hkdkxq51gom6tklMqrfOLnyN6WSm9TY5sLXp_fxoNQhtC3E7zY9A3dLEpfZ1phdw23m0SI8=@emersion.fr>
On Tue, Jun 18, 2019 at 2:18 AM Simon Ser <contact@emersion.fr> wrote:
>
> On Tuesday, June 18, 2019 5:19 AM, Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com> wrote:
> > I made the patch, but when I started to write the commit message, I just
> > realized that I did not understand why possible_crtcs should not be
> > equal zero. Why can we not use zero?
>
> Hi,
>
> possible_crtcs is a bitfield. If it's zero, it means the plane cannot
> be attached to any CRTC, which makes it rather useless.
Hi,
Thank you very much for your explanation. I'll try to finish the patch.
> Thanks,
>
> Simon
--
Rodrigo Siqueira
https://siqueira.tech
next prev parent reply other threads:[~2019-06-18 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 22:40 [PATCH 0/2] drm/vkms: Introduces writeback support Rodrigo Siqueira
2019-06-06 22:40 ` [PATCH 1/2] drm/vkms: Use index instead of 0 in possible crtc Rodrigo Siqueira
2019-06-07 7:39 ` Daniel Vetter
2019-06-07 14:37 ` Rodrigo Siqueira
2019-06-07 15:04 ` Daniel Vetter
2019-06-18 2:19 ` Rodrigo Siqueira
2019-06-18 5:18 ` Simon Ser
2019-06-18 21:51 ` Rodrigo Siqueira [this message]
2019-06-06 22:41 ` [PATCH 2/2] drm/vkms: Add support for writeback Rodrigo Siqueira
2019-06-07 7:48 ` Daniel Vetter
2019-06-07 7:53 ` Daniel Vetter
2019-06-07 14:58 ` Rodrigo Siqueira
2019-06-10 15:39 ` Liviu Dudau
2019-06-12 13:58 ` Rodrigo Siqueira
2019-06-07 14:17 ` Brian Starkey
2019-06-07 14:51 ` 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='CADKXj+4R=J0mEs3hYGiMS_iK+yhAZyXi_xOg-nRMtTAvSuCz2Q@mail.gmail.com' \
--to=rodrigosiqueiramelo@gmail.com \
--cc=brian.starkey@arm.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.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).