From: Greg KH <greg@kroah.com>
To: "Mustafa Ekşi" <mustafa.eskieksi@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Before submitting a driver for Casper Excalibur Laptops
Date: Wed, 21 Feb 2024 09:16:09 +0100 [thread overview]
Message-ID: <2024022114-vendetta-broadside-418a@gregkh> (raw)
In-Reply-To: <acca50d0-f2e9-4a81-b94d-3c8483f12ba7@gmail.com>
On Wed, Feb 21, 2024 at 01:30:11AM +0300, Mustafa Ekşi wrote:
> 2. Where should I put my driver?
> staging/ or platform/x86/? I'm planning to extend my driver to support more
> laptops from the same vendor.
drivers/staging/ is only for code that is not ready to be merged and it
must have a TODO file that lists what needs to be done. I'd recommend
just fixing the issues first and submitting it for drivers/platform/
directly.
> 3. Should I wait to extend support of the driver before submitting it?
No, send it now, no need to wait!
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-02-21 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 22:30 Before submitting a driver for Casper Excalibur Laptops Mustafa Ekşi
2024-02-21 8:16 ` Greg KH [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=2024022114-vendetta-broadside-418a@gregkh \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=mustafa.eskieksi@gmail.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