From: Greg KH <gregkh@linuxfoundation.org>
To: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
Cc: devel@driverdev.osuosl.org, florian.c.schilhabel@googlemail.com,
trivial@kernel.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com,
lkcamp@lists.libreplanetbr.org, nishkadg.linux@gmail.com,
Larry.Finger@lwfinger.net
Subject: Re: [PATCH] staging: rtl8712: align block comments
Date: Mon, 7 Oct 2019 12:27:35 +0200 [thread overview]
Message-ID: <20191007102735.GA345628@kroah.com> (raw)
In-Reply-To: <20191006203420.11202-1-gabrielabittencourt00@gmail.com>
On Sun, Oct 06, 2019 at 05:34:20PM -0300, Gabriela Bittencourt wrote:
> Cleans up warnings of "Block comments should align the * on each line"
>
> Signed-off-by: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
> ---
> drivers/staging/rtl8712/recv_linux.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8712/recv_linux.c b/drivers/staging/rtl8712/recv_linux.c
> index 84c4c8580f9a..70a4dcd4a1e5 100644
> --- a/drivers/staging/rtl8712/recv_linux.c
> +++ b/drivers/staging/rtl8712/recv_linux.c
> @@ -115,8 +115,8 @@ void r8712_recv_indicatepkt(struct _adapter *adapter,
> skb->protocol = eth_type_trans(skb, adapter->pnetdev);
> netif_rx(skb);
> recvframe->u.hdr.pkt = NULL; /* pointers to NULL before
> - * r8712_free_recvframe()
> - */
> + * r8712_free_recvframe()
> + */
> r8712_free_recvframe(recvframe, free_recv_queue);
> return;
> _recv_indicatepkt_drop:
This patch did not apply to my tree at all. Be sure you are working
against the staging-next branch of the staging.git tree, or off of
linux-next which includes this branch as well.
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2019-10-07 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 20:34 [PATCH] staging: rtl8712: align block comments Gabriela Bittencourt
2019-10-07 10:27 ` Greg KH [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=20191007102735.GA345628@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gabrielabittencourt00@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=nishkadg.linux@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=trivial@kernel.org \
/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).