From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Martin Kaiser <martin@kaiser.cx>,
Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: r8188eu: use a delayed worker for led updates
Date: Fri, 3 Dec 2021 15:14:31 +0100 [thread overview]
Message-ID: <YaomR72ytUd9jmAt@kroah.com> (raw)
In-Reply-To: <20211129110427.GQ6514@kadam>
On Mon, Nov 29, 2021 at 02:04:27PM +0300, Dan Carpenter wrote:
> This was confusing becuase it should have been [PATCH 4/4 v2]. These
> days I think the prefered way is to just resend the whole series as a
> new thread.
>
> Greg doesn't use patchwork, but these rules especially apply for
> subsystems which use patchwork. People say that patchwork gets confused
> when people use the --in-reply-to option and I guess it's hard to
> apply individual patches in patchwork? Anyway, just always start a new
> thread and resend everything.
>
> Send a reply to the original thread to say "Don't apply this one, it has
> sleeping in atomic bugs", otherwise it might get applied by mistake.
I had already reverted that patch from my tree, so I would not have
applied it again :)
thanks,
greg k-h
prev parent reply other threads:[~2021-12-03 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 16:25 [PATCH 0/4] staging: r8188eu: clean up workers Martin Kaiser
2021-11-25 16:25 ` [PATCH 1/4] staging: r8188eu: remove the _set_workitem wrapper Martin Kaiser
2021-11-25 16:25 ` [PATCH 2/4] staging: r8188eu: remove the _init_workitem wrapper Martin Kaiser
2021-11-25 16:25 ` [PATCH 3/4] staging: r8188eu: remove the _cancel_workitem_sync wrapper Martin Kaiser
2021-11-25 16:25 ` [PATCH 4/4] staging: r8188eu: use a delayed worker for led updates Martin Kaiser
2021-11-26 11:41 ` [PATCH v2] " Martin Kaiser
2021-11-27 7:42 ` Michael Straube
2021-11-29 11:04 ` Dan Carpenter
2021-12-03 14:14 ` Greg Kroah-Hartman [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=YaomR72ytUd9jmAt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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