From: Francesco Dolcini <francesco@dolcini.it>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: Stefan Eichenberger <eichest@gmail.com>,
	Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Subject: Advise needed on stale patches
Date: Fri, 15 Mar 2024 10:33:07 +0100	[thread overview]
Message-ID: <20240315093307.GA5060@francesco-nb> (raw)
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.
[1] https://lore.kernel.org/all/20240209105012.22470-1-eichest@gmail.com/
[2] https://lore.kernel.org/all/20231222183114.30775-1-francesco@dolcini.it/
Thanks,
Francesco
p.s. of course, I know that the Linux merge window is currently open and
these twos are busy weeks, I'm not expecting any action till the merge
window closes.
next             reply	other threads:[~2024-03-15  9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  9:33 Francesco Dolcini [this message]
2024-03-15 18:53 ` Advise needed on stale patches Dmitry Torokhov
2024-06-18 10:10   ` Francesco Dolcini
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=20240315093307.GA5060@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).