From: Vitor Massaru Iha <vitor@massaru.org>
To: Shuah Khan <skhan@linuxfoundation.org>, kunit-dev@googlegroups.com
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
brendanhiggins@google.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [fixup] kunit: use --build_dir=.kunit as default
Date: Tue, 26 May 2020 20:41:53 -0300 [thread overview]
Message-ID: <adc28ceff89a7fffb8b6af4badc850b29b9e6207.camel@massaru.org> (raw)
In-Reply-To: <ace26347-a78e-1bd1-86f5-f8e644aa93ec@linuxfoundation.org>
On Tue, 2020-05-26 at 16:29 -0600, Shuah Khan wrote:
> On 5/26/20 12:34 PM, Vitor Massaru Iha wrote:
> > To make KUnit easier to use, and to avoid overwriting object and
> > .config files, the default KUnit build directory is set to .kunit
> >
> > * Related bug: https://bugzilla.kernel.org/show_bug.cgi?id=205221
> >
> > Fixed up minor merge conflicts - Shuah Khan <
> > skhan@linuxfoundation.org>
> >
> > Signed-off-by: Vitor Massaru Iha <vitor@massaru.org>
> > Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
> > Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> > ---
> > version after merge on kunit brach:
> > * fix identation (tabs instead of spaces)
>
> You mentioned spaces breaking python. Please include the python
> errors and make it clear in the change log what is fixes.
Of course, I will add this.
>
> thanks,
> -- Shuah
>
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2020-05-26 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 18:34 [Linux-kernel-mentees] [fixup] kunit: use --build_dir=.kunit as default Vitor Massaru Iha
2020-05-26 22:29 ` Shuah Khan
2020-05-26 23:41 ` Vitor Massaru Iha [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=adc28ceff89a7fffb8b6af4badc850b29b9e6207.camel@massaru.org \
--to=vitor@massaru.org \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/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).