From: Martino Fontana <tinozzo123@gmail.com>
To: Silvan Jegen <s.jegen@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH v2] HID: nintendo: reinitialize USB Pro Controller after resuming from suspend
Date: Sat, 2 Sep 2023 14:36:06 +0200 [thread overview]
Message-ID: <CAKst+mBUwqMQcY3bAT=rTSMJrmXAzQizL6OWXUkUi8hjmb=12Q@mail.gmail.com> (raw)
In-Reply-To: <2XDNP3MKLE5L5.3MQT6EJ99UJBR@homearch.localdomain>
Hi
Is this patch (alongside "cleanup LED code") expected to land for Linux 6.6?
I'm asking because I can't find the patch in `for-next`.
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/log/?h=for-next
(Since it's my first patch here, I don't know if it's supposed to be seen
there.)
Cheers
On Sun, 23 Jul 2023 at 20:58, Silvan Jegen <s.jegen@gmail.com> wrote:
>
> Heyho
>
> Martino Fontana <tinozzo123@gmail.com> wrote:
> > It is my first patch on the Linux kernel, so I just did kinda what I
> > would do on GitHub (amend and force push).
> > What should I do here in case of trivial adjustments?
>
> I would leave it as is and only respin this one if either there are more
> comments on the old version or if the maintainer tells you to.
>
> BTW, just as a heads-up: posting an email reply at the top of the quoted
> email (aka "top-posting") is frowned upon in the Linux mailing lists. See
>
> https://people.kernel.org/tglx/
>
> for some pointers regarding netiquette.
>
> Cheers,
> Silvan
prev parent reply other threads:[~2023-09-02 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:10 [PATCH] HID: nintendo: reinitialize USB Pro Controller after resuming from suspend Martino Fontana
2023-07-20 19:53 ` Silvan Jegen
2023-07-20 23:31 ` [PATCH v2] " Martino Fontana
2023-07-21 19:02 ` Silvan Jegen
2023-07-22 10:29 ` Martino Fontana
2023-07-23 18:58 ` Silvan Jegen
2023-09-02 12:36 ` Martino Fontana [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='CAKst+mBUwqMQcY3bAT=rTSMJrmXAzQizL6OWXUkUi8hjmb=12Q@mail.gmail.com' \
--to=tinozzo123@gmail.com \
--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).