All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>,
	Qiang Zhang <Qiang.Zhang@windriver.com>
Cc: linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>,
	Felipe Balbi <balbi@kernel.org>, Kyungtae Kim <kt0755@gmail.com>
Subject: Re: usb: gadget: function: printer: Fix use-after-free in __lock_acquire()
Date: Mon, 08 Jun 2020 11:01:32 +0000	[thread overview]
Message-ID: <20200608110132.GA296162@kroah.com> (raw)
In-Reply-To: <ae59cac9-d770-36bd-ccb2-e5e442bd5e0a@web.de>

On Mon, Jun 08, 2020 at 12:55:13PM +0200, Markus Elfring wrote:
> > I don't need to add Fix tag to view the code.
> 
> I have got understanding difficulties for this kind of feedback.
> How much do you care for corresponding patch review concerns?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id¯7b4801030c07637840191c69eb666917e4135d#n183

Hi,

This is the semi-friendly patch-bot of Greg Kroah-Hartman.

Markus, you seem to have sent a nonsensical or otherwise pointless review
comment to a patch submission on a Linux kernel developer mailing list.
I strongly suggest that you not do this anymore.  Please do not bother
developers who are actively working to produce patches and features with
comments that, in the end, are a waste of time.

Patch submitter, please ignore Markus's suggestion; you do not needed
to follow it at all.  The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and inability
to adapt to feedback.  Please feel free to also ignore emails from them.

thanks,

greg k-h's patch email bot

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>,
	Qiang Zhang <Qiang.Zhang@windriver.com>
Cc: linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>,
	Felipe Balbi <balbi@kernel.org>, Kyungtae Kim <kt0755@gmail.com>
Subject: Re: usb: gadget: function: printer: Fix use-after-free in __lock_acquire()
Date: Mon, 8 Jun 2020 13:01:32 +0200	[thread overview]
Message-ID: <20200608110132.GA296162@kroah.com> (raw)
In-Reply-To: <ae59cac9-d770-36bd-ccb2-e5e442bd5e0a@web.de>

On Mon, Jun 08, 2020 at 12:55:13PM +0200, Markus Elfring wrote:
> > I don't need to add Fix tag to view the code.
> 
> I have got understanding difficulties for this kind of feedback.
> How much do you care for corresponding patch review concerns?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=af7b4801030c07637840191c69eb666917e4135d#n183

Hi,

This is the semi-friendly patch-bot of Greg Kroah-Hartman.

Markus, you seem to have sent a nonsensical or otherwise pointless review
comment to a patch submission on a Linux kernel developer mailing list.
I strongly suggest that you not do this anymore.  Please do not bother
developers who are actively working to produce patches and features with
comments that, in the end, are a waste of time.

Patch submitter, please ignore Markus's suggestion; you do not needed
to follow it at all.  The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and inability
to adapt to feedback.  Please feel free to also ignore emails from them.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2020-06-08 11:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  8:57 [PATCH] usb: gadget: function: printer: Fix use-after-free in __lock_acquire() Markus Elfring
2020-06-05  8:57 ` Markus Elfring
2020-06-05  9:14 ` Greg Kroah-Hartman
2020-06-05  9:14   ` Greg Kroah-Hartman
2020-06-08  6:54 ` 回复: [PATCH] usb: gadget: function: printer: =?gb2312?B?IEZpeCB1c2UtYWZ Zhang, Qiang
2020-06-08  6:54   ` 回复: [PATCH] usb: gadget: function: printer: Fix use-after-free in __lock_acquire() Zhang, Qiang
2020-06-08 10:55   ` Markus Elfring
2020-06-08 10:55     ` Markus Elfring
2020-06-08 11:01     ` Greg Kroah-Hartman [this message]
2020-06-08 11:01       ` Greg Kroah-Hartman
2020-06-28 13:43 ` [PATCH] usb: gadget: function: printer: The device interface is reset and should return error co Markus Elfring
2020-06-28 13:43   ` [PATCH] usb: gadget: function: printer: The device interface is reset and should return error code Markus Elfring
2020-06-28 14:13   ` [PATCH] usb: gadget: function: printer: The device interface is reset and should return error co Greg Kroah-Hartman
2020-06-28 14:13     ` [PATCH] usb: gadget: function: printer: The device interface is reset and should return error code Greg Kroah-Hartman

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=20200608110132.GA296162@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Markus.Elfring@web.de \
    --cc=Qiang.Zhang@windriver.com \
    --cc=balbi@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kt0755@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.