From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: daniel watson <ozzloy@challenge-bot.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove trailing whitespace
Date: Mon, 20 Jun 2022 10:04:08 +0200 [thread overview]
Message-ID: <YrAp+KlogDNwjGVa@kroah.com> (raw)
In-Reply-To: <20220620054529.4019-1-ozzloy@challenge-bot.com>
On Sun, Jun 19, 2022 at 10:45:29PM -0700, daniel watson wrote:
> From: Daniel Watson <ozzloy@challenge-bot.com>
>
> remove trailing whitespace found by checkpatch
>
> Signed-off-by: Daniel Watson <ozzloy@challenge-bot.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've taken this, but you should fix your email server DKIM settings as
it is not correct:
Grabbing thread from lore.kernel.org/all/20220620054529.4019-1-ozzloy%40challenge-bot.com/t.mbox.gz
Analyzing 1 messages in the thread
Checking attestation on all messages, may take a moment...
---
✗ [PATCH] staging: rtl8723bs: remove trailing whitespace
---
✗ BADSIG: DKIM/challenge-bot.com
---
Total patches: 1
next prev parent reply other threads:[~2022-06-20 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 5:45 [PATCH] staging: rtl8723bs: remove trailing whitespace daniel watson
2022-06-20 8:04 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-02 5:30 [PATCH] staging: rtl8723bs: Remove " gshahrouzi
2025-04-02 6:14 ` Greg KH
2025-04-02 11:20 ` Gabriel
2025-04-02 11:36 ` Greg KH
2025-04-02 11:31 Gabriel Shahrouzi
2025-04-02 11:38 ` Gabriel
2025-04-02 11:50 ` Greg KH
2025-12-10 8:49 [PATCH] staging: rtl8723bs: remove " Arjun Changla
2025-12-11 5:26 [PATCH] staging: media: atomisp: fix trailing statement Arjun Changla
2025-12-11 5:26 ` [PATCH] staging: rtl8723bs: remove trailing whitespace Arjun Changla
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=YrAp+KlogDNwjGVa@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ozzloy@challenge-bot.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.