All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: daniel watson <ozzloy@challenge-bot.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: put '{' on struct's first line
Date: Wed, 18 Aug 2021 10:10:44 +0200	[thread overview]
Message-ID: <YRzAhNrPdVW0B5CJ@kroah.com> (raw)
In-Reply-To: <20210818044105.23128-1-ozzloy@challenge-bot.com>

On Tue, Aug 17, 2021 at 09:41:05PM -0700, daniel watson wrote:
> From: Daniel Watson <ozzloy@challenge-bot.com>
> 
> Moved the opening curly brace to the end of the opening
> line of the phy_stat struct for style consistency.
> 
> Signed-off-by: Daniel Watson <ozzloy@challenge-bot.com>
> ---
>  drivers/staging/rtl8723bs/include/rtl8192c_recv.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

This change does not apply to my tree at all.  Make sure that you are
working off of the latest development tree, and not older kernel trees
(like Linus's), otherwise you will end up duplicating work that others
have already done.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: daniel watson <ozzloy@challenge-bot.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: put '{' on struct's first line
Date: Wed, 18 Aug 2021 10:10:44 +0200	[thread overview]
Message-ID: <YRzAhNrPdVW0B5CJ@kroah.com> (raw)
In-Reply-To: <20210818044105.23128-1-ozzloy@challenge-bot.com>

On Tue, Aug 17, 2021 at 09:41:05PM -0700, daniel watson wrote:
> From: Daniel Watson <ozzloy@challenge-bot.com>
> 
> Moved the opening curly brace to the end of the opening
> line of the phy_stat struct for style consistency.
> 
> Signed-off-by: Daniel Watson <ozzloy@challenge-bot.com>
> ---
>  drivers/staging/rtl8723bs/include/rtl8192c_recv.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

This change does not apply to my tree at all.  Make sure that you are
working off of the latest development tree, and not older kernel trees
(like Linus's), otherwise you will end up duplicating work that others
have already done.

thanks,

greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2021-08-18  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  4:41 [PATCH] staging: rtl8723bs: put '{' on struct's first line daniel watson
2021-08-18  4:41 ` daniel watson
2021-08-18  8:10 ` Greg Kroah-Hartman [this message]
2021-08-18  8:10   ` 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=YRzAhNrPdVW0B5CJ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.