linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Jones <luke@ljones.dev>
To: Silvan Jegen <s.jegen@gmail.com>
Cc: linux-input@vger.kernel.org, jikos@kernel.org,
	benjamin.tissoires@redhat.com
Subject: Re: [PATCH V3]: HID: asus: add support for ASUS N-Key keyboard
Date: Tue, 04 Aug 2020 22:32:23 +1200	[thread overview]
Message-ID: <ac137e587f9c7b5e95488313234586088a3ea104.camel@ljones.dev> (raw)
In-Reply-To: <21DR28I61TGRS.30UBU8HRX5ZB4@homearch.localdomain>

On Tue, 2020-08-04 at 10:17 +0200, Silvan Jegen wrote:
> Hi
> 
> Luke Jones <luke@ljones.dev> wrote:
> > [snip...] 
> > 
> > +/*
> > + * This enables triggering events in asus-wmi
> > + */
> > +static int asus_wmi_send_event(struct asus_drvdata *drvdat, u8
> > code)
> > +{
> > + int err;
> > + u32 retval;
> > +
> > + err = asus_wmi_evaluate_method(ASUS_WMI_METHODID_DEVS,
> > + ASUS_WMI_METHODID_NOTIF, code, &retval);
> > + if (err) {
> > + pr_warn("Failed to notify asus-wmi: %d\n", err);
> > + return err;
> > + }
> 
> It looks like your MUA removed all indentation tabs from your patch.
> IIRC,
> the gmail web interface has been accused of this before...
> 
> Most likely this will have to be fixed before someone approves of
> this patch.
> 
> 
> Cheers,
> 
> Silvan
> 
> 
> > [...]

Thank you for the heads up. Turns out Geary, although a nice email
client in general, is not suitable for this type of task.

Cheers,
Luke


      reply	other threads:[~2020-08-04 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  0:11 [PATCH V3]: HID: asus: add support for ASUS N-Key keyboard Luke Jones
2020-08-04  0:59 ` Luke Jones
2020-08-04  8:17 ` Silvan Jegen
2020-08-04 10:32   ` Luke Jones [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=ac137e587f9c7b5e95488313234586088a3ea104.camel@ljones.dev \
    --to=luke@ljones.dev \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=s.jegen@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;
as well as URLs for NNTP newsgroup(s).