From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Pascal Giard <pascal.giard@etsmtl.ca>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
Daniel Nguyen <daniel.nguyen.1@ens.etsmtl.ca>
Subject: Re: [PATCH] HID: sony: fix freeze when inserting ghlive ps3/wii dongles
Date: Tue, 20 Jul 2021 10:17:25 +0200 [thread overview]
Message-ID: <CAO-hwJKb9vy-jGvN9ChBOn14EdrGcJVSQeSRPFFNJr=G9ocfLA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2107152143060.8253@cbobk.fhfr.pm>
On Thu, Jul 15, 2021 at 9:44 PM Jiri Kosina <jikos@kernel.org> wrote:
>
> On Tue, 13 Jul 2021, Pascal Giard wrote:
>
> > We (Daniel and myself) have a patch that we want to submit that will add
> > support for the PS4 version of the Guitar Hero Live dongle ;-) IIUC our
> > patch should be against dtor/master and not Linus' tree.
> >
> > However, we see that dtor/master is still behind, it does not include
> > the fix. Is there something I need to do? Do I just have to be
> > patient?
>
> Just base the patch on Linus' tree, submit the patch to Dmitry and
> indicate that it's based on more recent upstream than his master. He will
> manage :)
FWIW, if the patch in question is
https://patchwork.kernel.org/project/linux-input/patch/20210715195720.169385-1-daniel.nguyen.1@ens.etsmtl.ca/
then this patch is not destinated to Dmitry, but the HID tree like the
current one :)
Cheers,
Benjamin
>
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2021-07-20 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:10 [PATCH] HID: sony: fix freeze when inserting ghlive ps3/wii dongles Pascal Giard
2021-06-05 6:43 ` Greg KH
2021-06-10 0:25 ` Pascal Giard
2021-06-10 5:22 ` Greg KH
2021-06-10 13:53 ` Pascal Giard
2021-06-15 8:53 ` Jiri Kosina
2021-07-13 19:08 ` Pascal Giard
2021-07-15 19:43 ` Jiri Kosina
2021-07-20 8:17 ` Benjamin Tissoires [this message]
2021-07-20 14:04 ` Pascal Giard
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='CAO-hwJKb9vy-jGvN9ChBOn14EdrGcJVSQeSRPFFNJr=G9ocfLA@mail.gmail.com' \
--to=benjamin.tissoires@redhat.com \
--cc=daniel.nguyen.1@ens.etsmtl.ca \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=pascal.giard@etsmtl.ca \
/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).