All of lore.kernel.org
 help / color / mirror / Atom feed
From: Branden Bonaby <brandonbonaby94@gmail.com>
To: gregkh@linuxfoundation.org
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/2] staging: wlan-ng: malformed SPDX-License-Identifier
Date: Thu, 21 Mar 2019 17:19:35 -0400	[thread overview]
Message-ID: <20190321211935.GB17315@Test-Virtual-Machine> (raw)
In-Reply-To: <56aaa0231a140e99ac024570a95c860890c3a58a.1553099252.git.brandonbonaby94@gmail.com>

On Wed, Mar 20, 2019 at 12:53:22PM -0400, Branden Bonaby wrote:
> Correct malformed SPDX-License-Identifier so that it
> matches Linux kernel comment coding style.
> 
> Signed-off-by: Branden Bonaby <brandonbonaby94@gmail.com>
> ---
>  drivers/staging/wlan-ng/hfa384x_usb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
> index 6261881e9bcd..75acdfc30f6a 100644
> --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: (GPL-2.0 OR MPL-1.1)
> +/* SPDX-License-Identifier: (GPL-2.0 OR MPL-1.1) */
>  /* src/prism2/driver/hfa384x_usb.c
>   *
>   * Functions that talk to the USB variantof the Intersil hfa384x MAC
> -- 
> 2.17.1
>

Hi

Please ignore this, it sent again after resuming my VM.
The patch has already been accepted.

Thank you



  reply	other threads:[~2019-03-21 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 17:22 [PATCH 0/2] staging: wlan-ng: malformed SPDX license and typo Branden Bonaby
2019-03-20 17:22 ` [PATCH 1/2] staging: wlan-ng: malformed SPDX-License-Identifier Branden Bonaby
2019-03-21 21:19   ` Branden Bonaby [this message]
2019-03-20 17:22 ` [PATCH 2/2] staging: wlan-ng: Correct typo in comment message Branden Bonaby
2019-03-21 21:20   ` Branden Bonaby
2019-04-10  7:39     ` sbrandyn34
2019-03-21 21:18 ` [PATCH 0/2] staging: wlan-ng: malformed SPDX license and typo Branden Bonaby
2019-04-14  9:09 ` sbrandyn34

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=20190321211935.GB17315@Test-Virtual-Machine \
    --to=brandonbonaby94@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.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.