From: Ryder Lee <ryder.lee@mediatek.com>
To: Roy Luo <royluo@google.com>
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
YF Luo <yf.luo@mediatek.com>,
Yiwei Chung <yiwei.chung@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] mt76: switch to SPDX tag instead of verbose boilerplate text
Date: Wed, 24 Jul 2019 11:15:46 +0800 [thread overview]
Message-ID: <1563938146.8010.4.camel@mtkswgap22> (raw)
In-Reply-To: <CA+zupgyq9VZkstdOOX4E_G9KWVN2WB+u0XnLiFAbxGws6Mt4qA@mail.gmail.com>
On Wed, 2019-07-24 at 11:03 +0800, Roy Luo wrote:
> Hi Ryder,
>
> Please follow the convention, some of your header files use //.
>
> C source: // SPDX-License-Identifier: <SPDX License Expression>
> C header: /* SPDX-License-Identifier: <SPDX License Expression> */
>
> Regards,
> Cheng-Hao (Roy) Luo
I also found that - copy paste mistake.
And I will fold this one into 'fix many checkpatch.pl warnings' series
then send v1.
Ryder
> On Tue, Jul 23, 2019 at 2:45 PM Ryder Lee <ryder.lee@mediatek.com> wrote:
> >
> > Add SPDX identifiers to all remaining files in mt76/
> >
> > Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
> > ---
WARNING: multiple messages have this Message-ID (diff)
From: Ryder Lee <ryder.lee@mediatek.com>
To: Roy Luo <royluo@google.com>
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
YF Luo <yf.luo@mediatek.com>,
Yiwei Chung <yiwei.chung@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
<linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] mt76: switch to SPDX tag instead of verbose boilerplate text
Date: Wed, 24 Jul 2019 11:15:46 +0800 [thread overview]
Message-ID: <1563938146.8010.4.camel@mtkswgap22> (raw)
In-Reply-To: <CA+zupgyq9VZkstdOOX4E_G9KWVN2WB+u0XnLiFAbxGws6Mt4qA@mail.gmail.com>
On Wed, 2019-07-24 at 11:03 +0800, Roy Luo wrote:
> Hi Ryder,
>
> Please follow the convention, some of your header files use //.
>
> C source: // SPDX-License-Identifier: <SPDX License Expression>
> C header: /* SPDX-License-Identifier: <SPDX License Expression> */
>
> Regards,
> Cheng-Hao (Roy) Luo
I also found that - copy paste mistake.
And I will fold this one into 'fix many checkpatch.pl warnings' series
then send v1.
Ryder
> On Tue, Jul 23, 2019 at 2:45 PM Ryder Lee <ryder.lee@mediatek.com> wrote:
> >
> > Add SPDX identifiers to all remaining files in mt76/
> >
> > Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
> > ---
next prev parent reply other threads:[~2019-07-24 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:45 [PATCH] mt76: switch to SPDX tag instead of verbose boilerplate text Ryder Lee
2019-07-23 6:45 ` Ryder Lee
2019-07-24 3:03 ` Roy Luo
2019-07-24 3:15 ` Ryder Lee [this message]
2019-07-24 3:15 ` Ryder Lee
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=1563938146.8010.4.camel@mtkswgap22 \
--to=ryder.lee@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=royluo@google.com \
--cc=sean.wang@mediatek.com \
--cc=yf.luo@mediatek.com \
--cc=yiwei.chung@mediatek.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.