From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Dorine Tipo <dorine.a.tipo@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Helen Koike <helen.koike@collabora.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Nick Terrell <terrelln@fb.com>,
Daniel Stone <daniels@collabora.com>,
Rob Clark <robdclark@gmail.com>,
Linux Outreachy <outreachy@lists.linux.dev>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH Resend] Fix line Length
Date: Mon, 30 Oct 2023 18:36:34 +0700 [thread overview]
Message-ID: <3f1fdfa2-e30b-42c6-b290-bb02283b3589@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2310300712310.3533@hadrien>
On 30/10/2023 13:12, Julia Lawall wrote:
>
>
> On Mon, 30 Oct 2023, Bagas Sanjaya wrote:
>
>> Hi Julia,
>>
>> The submitter touched one of CI scripts for the DRM subsystem. To test
>> this patch, there must be a way to run these scripts locally (which
>> may requires non-trivial setup).
>>
>> Cc'ed DRM maintainers.
>
> There is a DRM outreachy project. I think that motivated this patch.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-10-30 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231029144312.5895-1-dorine.a.tipo@gmail.com>
[not found] ` <alpine.DEB.2.22.394.2310291610030.3136@hadrien>
2023-10-29 23:50 ` Bagas Sanjaya
2023-10-30 6:12 ` Julia Lawall
2023-10-30 11:36 ` Bagas Sanjaya [this message]
2023-10-31 18:36 ` Helen Koike
2023-11-01 2:10 ` Bagas Sanjaya
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=3f1fdfa2-e30b-42c6-b290-bb02283b3589@gmail.com \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dorine.a.tipo@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=helen.koike@collabora.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=robdclark@gmail.com \
--cc=terrelln@fb.com \
--cc=tomeu.vizoso@collabora.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
all inboxes | Powered by JetHome®