linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	linux-input@vger.kernel.org,
	Stefan Eichenberger <eichest@gmail.com>,
	Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Subject: Re: Advise needed on stale patches
Date: Tue, 18 Jun 2024 12:10:21 +0200	[thread overview]
Message-ID: <20240618101021.GA10395@francesco-nb> (raw)
In-Reply-To: <ZfSZDbyczmodyI_j@google.com>

Hello again Dmitry and Linux Input people,

On Fri, Mar 15, 2024 at 11:53:01AM -0700, Dmitry Torokhov wrote:
> On Fri, Mar 15, 2024 at 10:33:07AM +0100, Francesco Dolcini wrote:
> > Hello Dmitry and Linux Input people,
> > 
> > In the last months I sent (or was involved in) a couple of small patches
> > [1][2] (bug fixes or small addition to an existing driver) and they have
> > been around in the mailing list for quite some time (months, 2023-09-20
> > the oldest one).
> > 
> > I am not sure on how to progress here, therefore looking for some advise.
> > 
> > Maybe they did just fall through the cracks, in this case just take this
> > as a kind head up (or maybe those email did not pass some aggressive
> > spam filtering?).
> > 
> > Or maybe the changes are not deemed correct or something wrong was done,
> > and in this case it would be great to know what we could improve.
> > 
> > Or, maybe you just had other priorities (life and work are challenging
> > at times, I know), in this case, if possible, I would love to know if I
> > can provide some small help in any way.
> 
> Sorry, I am swamped with other projects. I just responded on the
> mailing list for the patch [2].

You got a new patch version 2 months ago and no comment afterward.

What about https://lore.kernel.org/all/20231222183114.30775-1-francesco@dolcini.it/ ?
Those are just a couple of small fixes that should be easy to provide a
feedback on, or eventually just apply? That one is on the LKML since
September 2023.

With that said, sorry for buggering you again, I understand that you
might have other project and priorities, however I do not know how to
move forward.

In the end what I am looking for is some guidance on what's the best way
to contribute in an effective way such kind of small fixes/improvements
to the Linux input subsystem drivers.

Thanks
Francesco


      reply	other threads:[~2024-06-18 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  9:33 Advise needed on stale patches Francesco Dolcini
2024-03-15 18:53 ` Dmitry Torokhov
2024-06-18 10:10   ` Francesco Dolcini [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=20240618101021.GA10395@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eichest@gmail.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=linux-input@vger.kernel.org \
    /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).