linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
	 Hans de Goede <hdegoede@redhat.com>,
	bentiss@kernel.org,  dri-devel@lists.freedesktop.org,
	jelle@vdwaa.nl, jikos@kernel.org,  lee@kernel.org,
	linux-input@vger.kernel.org,  LKML <linux-kernel@vger.kernel.org>,
	linux-leds@vger.kernel.org,  miguel.ojeda.sandonis@gmail.com,
	ojeda@kernel.org, onitake@gmail.com,  cs@tuxedo.de,
	platform-driver-x86@vger.kernel.org
Subject: Re: [RFC PATCH v4 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Date: Wed, 2 Oct 2024 13:01:05 +0300 (EEST)	[thread overview]
Message-ID: <c2694d50-db7c-84ee-288a-06802e10ca8d@linux.intel.com> (raw)
In-Reply-To: <Zv0YlxQOFVGRS/DB@duo.ucw.cz>

On Wed, 2 Oct 2024, Pavel Machek wrote:

> Hi!
> 
> > > +static struct wmi_driver tuxedo_nb04_wmi_ab_driver = {
> > > +	.driver = {
> > > +		.name = "tuxedo_nb04_wmi_ab",
> > > +		.probe_type = PROBE_PREFER_ASYNCHRONOUS,
> > > +	},
> > > +	.id_table = tuxedo_nb04_wmi_ab_device_ids,
> > > +	.probe = probe,
> > > +	.remove = remove,
> > > +	.no_singleton = true,
> > > +};
> > > +
> > > +// We don't know if the WMI API is stable and how unique the GUID is for this ODM. To be on the safe
> > > +// side we therefore only run this driver on tested devices defined by this list.
> > 
> > Please limit comment length to 80 chars and since you need multiple lines 
> > here anyway, use the usual /* */ multiline comment formatting.
> 
> This driver needs to be split into generic part + hw specific part,
> and reasonable kernel/user API needs to be defined for the generic
> part. It is really too soon to tweak comment lengths.

Coding style is not something you add on top of everything after 
everything else is done. It's much better to start with that right from 
the beginning.

-- 
 i.


  reply	other threads:[~2024-10-02 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 18:06 [RFC PATCH v4 0/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 Werner Sembach
2024-10-01 18:06 ` [RFC PATCH v4 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices Werner Sembach
2024-10-02  9:52   ` Ilpo Järvinen
2024-10-02  9:55     ` Pavel Machek
2024-10-02 10:01       ` Ilpo Järvinen [this message]
2024-10-02 10:05         ` Pavel Machek
2024-10-02 14:53     ` Werner Sembach
2024-10-03 10:54       ` Ilpo Järvinen
2024-10-04 14:30         ` Werner Sembach
2024-10-04 14:46           ` Ilpo Järvinen
2024-10-07 16:17             ` Werner Sembach

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=c2694d50-db7c-84ee-288a-06802e10ca8d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bentiss@kernel.org \
    --cc=cs@tuxedo.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=jelle@vdwaa.nl \
    --cc=jikos@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=onitake@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=wse@tuxedocomputers.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 NNTP newsgroup(s).