All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: kernelnewbies@kernelnewbies.org
Subject: What to do when a patch set gets no reply for 3 weeks ?
Date: Tue, 29 Sep 2020 12:26:20 +0200	[thread overview]
Message-ID: <20041735453424947069@scdbackup.webframe.org> (raw)

Hi,

i sent my first patch set three weeks ago. See:
  https://lore.kernel.org/linux-scsi/20200908120207.5014-1-scdbackup@gmx.net/T/#u

It was made with
  git format-patch
and sent by
  git send-email
to the addresses which were proposed here. In linux-scsi it showed up
after a day.

Then i followed the advise in Documentation/process/submitting-patches.rst
  "Wait for a minimum of
   one week before resubmitting or pinging reviewers - possibly longer"

Still no reply yet. Neither to my mail address nor visible in the thread
display of lore.kernel.org.

Could some merciful person have a look at my patch set and point me to
obvious reasons why it does not get considered ?

--------------------------------------------------------------------------

If no obvious shortcomming disqualifies my patches, what to do next ?

- Ping everybody ?

- Repost ?

- Post one of the patch sets which i made during my time of patience ?
  I have
  - 3 bug fixes for cdrom+sr
  - 1 augmentation of cdrom+sr for multi-session DVD and BD media
  - 1 wish for a new ioctl CDROM_SIMUL_CHANGE in cdrom+sr
  - 2 bug fixes for isofs


Have a nice day :)

Thomas


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2020-09-29 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 10:26 Thomas Schmitt [this message]
2020-09-29 10:34 ` What to do when a patch set gets no reply for 3 weeks ? Greg KH
2020-09-29 12:07   ` Thomas Schmitt

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=20041735453424947069@scdbackup.webframe.org \
    --to=scdbackup@gmx.net \
    --cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.