All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <danielyangkang@gmail.com>
Cc: <alibuda@linux.alibaba.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <guwen@linux.alibaba.com>,
	<jaka@linux.ibm.com>, <kuba@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>,
	<syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com>,
	<tonylu@linux.alibaba.com>, <wenjia@linux.ibm.com>
Subject: Re: [PATCH v3 2/2 RESEND] resolve gtp possible deadlock warning
Date: Tue, 15 Oct 2024 17:03:00 -0700	[thread overview]
Message-ID: <20241016000300.70582-1-kuniyu@amazon.com> (raw)
In-Reply-To: <c2ac8e30806af319eb96f67103196b7cda22d562.1729031472.git.danielyangkang@gmail.com>

From: Daniel Yang <danielyangkang@gmail.com>
Date: Tue, 15 Oct 2024 15:48:05 -0700
> From: Daniel Yang <danielyangkang@gmail.com>
> 
> Moved lockdep annotation to separate function for readability.
> 
> Signed-off-by: Daniel Yang <danielyangkang@gmail.com>
> Reported-by: syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com

This tag is bogus, why not squash to patch 1 ?

Also, patch 1 needs Fixes: tag.

  reply	other threads:[~2024-10-16  0:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 22:48 Daniel Yang
2024-10-15 22:48 ` [PATCH v3 1/2 RESEND] resolve gtp possible deadlock warning Daniel Yang
2024-10-15 22:48 ` [PATCH v3 2/2 " Daniel Yang
2024-10-16  0:03   ` Kuniyuki Iwashima [this message]
2024-10-16  0:24     ` Daniel Yang
2024-10-16  0:30       ` Daniel Yang
2024-10-22  2:00   ` D. Wythe
2024-10-16  1:27 ` Jakub Kicinski

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=20241016000300.70582-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=danielyangkang@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.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 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.