linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: Need help in debugging "memory leak in em28xx_init_dev"
Date: Mon, 1 Nov 2021 15:26:01 +0300	[thread overview]
Message-ID: <613828ef-085c-acbb-f54e-7819dc22c769@gmail.com> (raw)
In-Reply-To: <CAD-N9QUcoKnEWw98XnBJZkas3AkwPonNG0K-PMROOwn8kReT5g@mail.gmail.com>

On 11/1/21 15:23, Dongliang Mu wrote:
> drop? I do see some patches from local syzkaller will attach this tag
> to assign credits to syzkaller/syzbot.
> 
> I think this form is good. Thus I copy this tag from them.
> 

Sorry for not being clear :(

I mean, I can't send my "Reviewed-by" tag to the patch. Missed that 
"R-b" can be also decoded as Reported-by


With regards,
Pavel Skripkin

  reply	other threads:[~2021-11-01 12:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  3:02 Need help in debugging "memory leak in em28xx_init_dev" Dongliang Mu
2021-11-01  7:50 ` Pavel Skripkin
2021-11-01  8:55   ` Dongliang Mu
2021-11-01  9:19     ` Pavel Skripkin
2021-11-01  9:41       ` Dongliang Mu
2021-11-01  9:43         ` Pavel Skripkin
2021-11-01  9:58           ` Dongliang Mu
2021-11-01 12:17             ` Pavel Skripkin
2021-11-01 12:23               ` Dongliang Mu
2021-11-01 12:26                 ` Pavel Skripkin [this message]
2021-11-01 12:31                   ` Dongliang Mu
2021-11-01 14:30             ` Dan Carpenter
2021-11-01 14:33               ` Dongliang Mu
2021-11-01 15:05               ` Randy Dunlap
2021-11-01 18:33                 ` Dan Carpenter

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=613828ef-085c-acbb-f54e-7819dc22c769@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mudongliangabcd@gmail.com \
    /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).