From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Helen Koike <helen.koike@collabora.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: Wed, 1 Nov 2023 09:10:39 +0700 [thread overview]
Message-ID: <ZUGzn-xcoymIfoQA@debian.me> (raw)
In-Reply-To: <318c568f-c813-4d16-b577-28f37cde92c7@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Tue, Oct 31, 2023 at 03:36:30PM -0300, Helen Koike wrote:
>
>
> 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
Thanks for the pointer!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-11-01 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 14:43 [PATCH Resend] Fix line Length Dorine Tipo
2023-10-29 15:11 ` Julia Lawall
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
2023-11-01 2:10 ` Bagas Sanjaya [this message]
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=ZUGzn-xcoymIfoQA@debian.me \
--to=bagasdotme@gmail.com \
--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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).