From: jim.cromie@gmail.com
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to test device driver?
Date: Mon, 17 May 2021 12:48:38 -0600 [thread overview]
Message-ID: <CAJfuBxwGeM+dqRy3ZScrSuCEz61hsUBcx7e7VAjX0iSJ2+0e4g@mail.gmail.com> (raw)
In-Reply-To: <20210517152813.GA59315@hyeyoo>
On Mon, May 17, 2021 at 9:28 AM Hyeonggon Yoo <42.hyeyoo@gmail.com> wrote:
>
> Hello, there are lots of drivers in linux.
>
> My questions are:
>
> - how can we test driver? is it just using that device for a long
> time as a user?
>
testing is hard. Having the device is highly recommended.
ISTM essential if adding a Tested-by: tag
Do you have a particular device in mind ?
> - what to do if there's a bug (like syzbot report), fixed it,
> but if we don't have that device?
>
You could reply to that report email, with your patch included.
0day/lkp robot watches many email lists, and might test your patch
automatically, for you on different architectures
at least Ive seen it happening on kbuild, kbuild-all lists
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-05-17 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:28 How to test device driver? Hyeonggon Yoo
2021-05-17 18:48 ` jim.cromie [this message]
2021-05-17 23:53 ` Hyeonggon Yoo
2021-05-18 1:09 ` jim.cromie
2021-05-18 13:58 ` Valdis Klētnieks
2021-05-18 19:53 ` Jeffrey Walton
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=CAJfuBxwGeM+dqRy3ZScrSuCEz61hsUBcx7e7VAjX0iSJ2+0e4g@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=kernelnewbies@kernelnewbies.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.