mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Michał Lach" <michal.lach@samsung.com>
Cc: linux-kernel@vger.kernel.org, mcgrof@kernel.org,
	russell.h.weight@intel.com, rafael@kernel.org,
	ming.lei@canonical.com, tiwai@suse.de
Subject: Re: [PATCH] drivers/firmware_loader: remove list entry before deallocation
Date: Thu, 8 Dec 2022 19:18:08 +0100	[thread overview]
Message-ID: <Y5IqYBaiwO5Qb/Kw@kroah.com> (raw)
In-Reply-To: <bf8f52d2-1a11-03ed-37e9-4bde42ebc211@samsung.com>

On Thu, Dec 08, 2022 at 05:18:15PM +0100, Michał Lach wrote:
> On 12/8/22 16:42, Greg KH wrote:
> > On Thu, Dec 08, 2022 at 04:23:52PM +0100, Michał Lach wrote:
> >> On 12/8/22 14:18, Greg KH wrote:
> >>> On Thu, Dec 08, 2022 at 11:45:28AM +0100, Michał Lach wrote:
> >>>> Pinging
> >>>
> >>> I have no context here at all.
> >>>
> >>> confused,
> >>
> >> It seems like my mail client messed up the encoding, sorry.
> >> Below quoting the patch message:
> > 
> > Ok, but what does an empty ping here mean?
> > 
> > Are you asking why no one else has reviewed this?  Why it hasn't been
> > accepted?  What else needs to happen?  Something else?
> > 
> 
> It was kind of meant to bump it for other reviewers to review/accept
> this. Please correct me if this is against the netiquette here or 
> should I just mention the reason for the ping in the first place.

Please think about what you would want to see sent to you.  A "naked"
ping has no context at all, right?

How about a normal "It's been two weeks, anything else I need to do here
to get this merged?" sentance would be great.

And to help maintainer's workload, why not help out and review other
patches submitted?  That's the best way to help ensure that a
maintainer's workload is reduced, and help make your patches move to the
top of the list.

thanks,

greg k-h

  reply	other threads:[~2022-12-08 18:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221123111806eucas1p23fdcdbe6e5f4a9e714db428fcd6552b9@eucas1p2.samsung.com>
2022-11-23 11:14 ` Michal Lach
2022-11-29 19:06   ` Russ Weight
2022-12-08 10:45   ` Michał Lach
2022-12-08 13:18     ` Greg KH
2022-12-08 15:23       ` Michał Lach
2022-12-08 15:42         ` Greg KH
2022-12-08 16:18           ` Michał Lach
2022-12-08 18:18             ` Greg KH [this message]
2022-12-09 14:09               ` Michał Lach
2022-12-12  6:04   ` Luis Chamberlain
2022-12-12 17:52     ` Michał Lach
2022-12-13 23:05       ` Luis Chamberlain

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=Y5IqYBaiwO5Qb/Kw@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=michal.lach@samsung.com \
    --cc=ming.lei@canonical.com \
    --cc=rafael@kernel.org \
    --cc=russell.h.weight@intel.com \
    --cc=tiwai@suse.de \
    /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

all inboxes | Powered by JetHome®