linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Tom Rix <trix@redhat.com>
Cc: lars@metafoo.de, andrea.merello@iit.it,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: fix spdx format
Date: Sat, 28 Jan 2023 16:23:37 +0000	[thread overview]
Message-ID: <20230128162337.64f61d19@jic23-huawei> (raw)
In-Reply-To: <20230124194301.656518-1-trix@redhat.com>

On Tue, 24 Jan 2023 11:43:01 -0800
Tom Rix <trix@redhat.com> wrote:

> checkpatch reports
> WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
> FILE: drivers/iio/imu/bno055/bno055_ser_trace.c:1:
> +//SPDX-License-Identifier: GPL-2.0
> 
> Add a space
> 
> Fixes: 2eef5a9cc643 ("iio: imu: add BNO055 serdev driver")
> Signed-off-by: Tom Rix <trix@redhat.com>
Applied to the togreg branch of iio.git and pushed out as testing
so other patches in my queue get tested (not going to find anything in this one!)

> ---
>  drivers/iio/imu/bno055/bno055_ser_trace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/imu/bno055/bno055_ser_trace.c b/drivers/iio/imu/bno055/bno055_ser_trace.c
> index 48397b66daef..ab564186d19c 100644
> --- a/drivers/iio/imu/bno055/bno055_ser_trace.c
> +++ b/drivers/iio/imu/bno055/bno055_ser_trace.c
> @@ -1,4 +1,4 @@
> -//SPDX-License-Identifier: GPL-2.0
> +// SPDX-License-Identifier: GPL-2.0
>  
>  /*
>   * bno055_ser Trace Support


      reply	other threads:[~2023-01-28 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 19:43 [PATCH] iio: imu: fix spdx format Tom Rix
2023-01-28 16:23 ` Jonathan Cameron [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=20230128162337.64f61d19@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andrea.merello@iit.it \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).