From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Is anyone working on fixing warnings these Documentation files ?
Date: Wed, 22 Apr 2020 21:45:31 +0200 [thread overview]
Message-ID: <be840fef-784b-77d0-41d6-152ed09faba9@gmail.com> (raw)
In-Reply-To: <20200422210903.6a99a51d@coco.lan>
On 4/22/20 9:09 PM, Mauro Carvalho Chehab wrote:
> Em Wed, 22 Apr 2020 19:53:42 +0200
> Saheed Bolarinwa <refactormyself@gmail.com> escreveu:
>
>> Sorry for taking long to reply.
>>
>> I think I got different warnings because I was checking for warnings on
>> the stable tree. I get a different set of
>>
>> warnings now with linux-next. Just to confirm, here is what I am doing:
>>
>> - update my local repo to linux-main
>>
>> - run this command make htmldocs > doc_make.log 2>&1
>>
>> - check doc_make.log for warnings
> No, the best is to use the latest tag at linux next (with are updated
> every day).
>
> So, you should do something like:
>
> # in case your tree is not based on linux-next:
> $ git remote add linux-next git://github.com/sfrothwell/linux-next.git
>
>
> Then:
>
> $ git checkout -b my_docs_next_branch next-20200422
> $ make htmldocs
>
> Thanks,
> Mauro
Okay, I have done that and I see the warnings. Please, do you have any
suggestion on where to start?
Thank you.
- Saheed
_______________________________________________
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-04-22 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 0:56 [Linux-kernel-mentees] Is anyone working on fixing warnings these Documentation files ? Saheed Bolarinwa
2020-04-20 6:36 ` Mauro Carvalho Chehab
2020-04-21 9:04 ` Saheed Bolarinwa
2020-04-21 10:45 ` Mauro Carvalho Chehab
2020-04-22 17:53 ` Saheed Bolarinwa
2020-04-22 19:09 ` Mauro Carvalho Chehab
2020-04-22 19:45 ` Saheed Bolarinwa [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=be840fef-784b-77d0-41d6-152ed09faba9@gmail.com \
--to=refactormyself@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=mchehab+huawei@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.