kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: nishad kamdar <nishadkamdar@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Process after patch has been reviewed and reviewed-by: tag added
Date: Wed, 18 Aug 2021 13:18:27 +0530	[thread overview]
Message-ID: <CADMaTkOyZWNm5Wcwj5OfBC1h5VT4o6QrHiEgtW4gRCNS8yzAXg@mail.gmail.com> (raw)
In-Reply-To: <YRy6SGbhGE6bQ6iT@kroah.com>


[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]

Ok will do.

Thanks very much.
Nishad

On Wed, Aug 18, 2021, 1:14 PM Greg KH <greg@kroah.com> wrote:

> On Wed, Aug 18, 2021 at 12:25:02PM +0530, nishad kamdar wrote:
> > Hello,
> >
> > I submitted a patch here:
> >
> https://patchwork.kernel.org/project/linux-mmc/patch/20210812065730.3986-1-nishadkamdar@gmail.com/
> >
> > It has been reviewed and the reviewed-by: tag has been added.
> > But since then it has been a week and there is no activity.
> >
> > I wanted to know what happens after this step and is the patch ready for
> > acceptance ?
> > Should I remind some of the maintainers to look into this patch or is
> there
> > nothing to be done from my end?
>
> If nothing happens in 2 weeks, respond to the patch and ask if there is
> anything that needs to be done to have the maintainer pick it up.
>
> thanks,
>
> greg k-h
>

[-- Attachment #1.2: Type: text/html, Size: 1414 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

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

      reply	other threads:[~2021-08-18  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  6:55 Process after patch has been reviewed and reviewed-by: tag added nishad kamdar
2021-08-18  7:44 ` Greg KH
2021-08-18  7:48   ` nishad kamdar [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=CADMaTkOyZWNm5Wcwj5OfBC1h5VT4o6QrHiEgtW4gRCNS8yzAXg@mail.gmail.com \
    --to=nishadkamdar@gmail.com \
    --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).