mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>
Cc: Daniel Stone <daniels@collabora.com>,
	Linux Outreachy <outreachy@lists.linux.dev>,
	Greg KH <gregkh@linuxfoundation.org>,
	Nick Terrell <terrelln@fb.com>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dorine Tipo <dorine.a.tipo@gmail.com>
Subject: Re: [PATCH Resend] Fix line Length
Date: Tue, 31 Oct 2023 15:36:30 -0300	[thread overview]
Message-ID: <318c568f-c813-4d16-b577-28f37cde92c7@collabora.com> (raw)
In-Reply-To: <3f1fdfa2-e30b-42c6-b290-bb02283b3589@gmail.com>



On 30/10/2023 08:36, Bagas Sanjaya wrote:
> 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).

Instructions to test it is on the docs:

https://docs.kernel.org/gpu/automated_testing.html?highlight=drm+ci#how-to-enable-automated-testing-on-your-tree

>>>
>>> Cc'ed DRM maintainers.
>>
>> There is a DRM outreachy project.  I think that motivated this patch.

Yes :)

>>
> 
> OK, thanks!
> 


Thanks
Helen

  reply	other threads:[~2023-10-31 18: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
2023-10-31 18:36         ` Helen Koike [this message]
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=318c568f-c813-4d16-b577-28f37cde92c7@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=bagasdotme@gmail.com \
    --cc=daniels@collabora.com \
    --cc=dorine.a.tipo@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=terrelln@fb.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®