Skip to contentSkip to conversation

What to do when a patch set gets no reply for 3 weeks ?

DISCUSSION Thomas Schmitt 2 participants 3 messages Sep 29, 2020

lore
Share & tools
lore
#0 lore raw

Hi,

i sent my first patch set three weeks ago. See:
https://lore.kernel.org/linux-scsi/[email protected]/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
[email protected]
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

#1 lore raw
Quoted 22 lines · Thomas Schmitt

Hi,

i sent my first patch set three weeks ago. See:
https://lore.kernel.org/linux-scsi/[email protected]/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 ?

Quoted 7 lines

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

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

- Ping everybody ?

- Repost ?

repost it and don't worry about it, maintainers get behind.

Also, I think the scsi list wants developers to help review other patches, right? Why not help out with that while you wait for your patches to be reviewed?

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
[email protected]
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

#2 lore raw

Hi,

Quoted 1 line · Greg KH

repost it and don't worry about it, maintainers get behind.

Will do.

Quoted 3 lines

Also, I think the scsi list wants developers to help review other patches, right? Why not help out with that while you wait for your patches to be reviewed?

My SCSI knowledge is concentrated on optical drives, which i am used to operate from userland via ioctl(SG_IO). So if it's not about cdrom or sr (or isofs), i am not qualified to have an own opinion.

I saw no patch sets which would deal with my topics, other than the very broad one by Christoph Hellwig which by two patches affects sr:
https://lore.kernel.org/linux-scsi/[email protected]/T/#t

I studied it, but the only thought it gave me was that my wished new ioctl had to become more independent of the entrails of general block device handling. (Now it is much leaner and less needy of justifications that it is indeed harmless.)

Hm. Jens Axboe writes "Applied". Maybe i can learn to which repo and rebase my patch for that one ...

Have a nice day :)

Thomas

_______________________________________________
Kernelnewbies mailing list
[email protected]
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies