kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: kernelnewbies@kernelnewbies.org
Cc: greg@kroah.com
Subject: Re: What to do when a patch set gets no reply for 3 weeks ?
Date: Tue, 29 Sep 2020 14:07:55 +0200	[thread overview]
Message-ID: <13946735447207132811@scdbackup.webframe.org> (raw)
In-Reply-To: <20200929103405.GA954079@kroah.com>

Hi,

Greg KH wrote:
> repost it and don't worry about it, maintainers get behind.

Will do.


> 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/b5e51c24-b9a6-979f-8fe0-f762f113bba3@kernel.dk/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
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-09-29 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 10:26 What to do when a patch set gets no reply for 3 weeks ? Thomas Schmitt
2020-09-29 10:34 ` Greg KH
2020-09-29 12:07   ` Thomas Schmitt [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=13946735447207132811@scdbackup.webframe.org \
    --to=scdbackup@gmx.net \
    --cc=greg@kroah.com \
    --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 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).