public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	david@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH 1/3] s390x: Add SPDX and header comments for s390x/* and lib/s390x/*
Date: Wed, 28 Jul 2021 13:41:34 +0200	[thread overview]
Message-ID: <d1c3e9f0-57c0-e941-3e3f-94a897ace177@linux.ibm.com> (raw)
In-Reply-To: <2e391a1a-54d4-8713-4a93-104a6b4cfaf1@linux.ibm.com>

On 7/28/21 1:36 PM, Janosch Frank wrote:
> On 7/28/21 12:36 PM, Thomas Huth wrote:
>> On 28/07/2021 12.32, Claudio Imbrenda wrote:
>>> On Wed, 28 Jul 2021 10:13:26 +0000
>>> Janosch Frank <frankja@linux.ibm.com> wrote:
>>>
>>>> Seems like I missed adding them.
>>>>
>>>> The s390x/sieve.c one is a bit of a head scratcher since it came with
>>>> the first commit but I assume it's lpgl2-only since that's what the
>>>> COPYRIGHT file said then.
>>>>
>>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>>> ---
>>>>   lib/s390x/uv.c   |  9 +++++++++
>>>>   s390x/mvpg-sie.c |  9 +++++++++
>>>>   s390x/sie.c      | 10 ++++++++++
>>>>   x86/sieve.c      |  5 +++++
>>>>   4 files changed, 33 insertions(+)
>> [...]
>>>> diff --git a/x86/sieve.c b/x86/sieve.c
>>>> index 8150f2d9..b89d5f80 100644
>>>> --- a/x86/sieve.c
>>>> +++ b/x86/sieve.c
>>>> @@ -1,3 +1,8 @@
>>>> +/* SPDX-License-Identifier: LGPL-2.0-only */
>>>
>>> do you really need to fix something in the x86 directory? (even though
>>> it is also used on other archs)
>>
>> I just realized that s390x/sieve.c is just a symlink, not a copy of the file :-)
> 
> You're not the only one...
> 
>>
>>> maybe you can split out this as a separate patch, so s390x stuff is
>>> more self contained, and others can then discuss the sieve.c patch
>>> separately if needed?
>>
>> That might make sense, indeed.
> 
> Yup will do

On second thought I'm just gonna drop that hunk since x86 doesn't really
have SPDX or header comments for most of their files anyway.

> 
>>
>>   Thomas
>>
> 


  reply	other threads:[~2021-07-28 11:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 10:13 [kvm-unit-tests PATCH 0/3] s390x: SPDX and header comment fixes Janosch Frank
2021-07-28 10:13 ` [kvm-unit-tests PATCH 1/3] s390x: Add SPDX and header comments for s390x/* and lib/s390x/* Janosch Frank
2021-07-28 10:32   ` Claudio Imbrenda
2021-07-28 10:36     ` Thomas Huth
2021-07-28 11:36       ` Janosch Frank
2021-07-28 11:41         ` Janosch Frank [this message]
2021-07-28 11:56           ` Thomas Huth
2021-07-28 10:33   ` Thomas Huth
2021-07-28 12:56   ` [kvm-unit-tests PATCH v2] " Janosch Frank
2021-07-28 13:25     ` Claudio Imbrenda
2021-07-28 14:35     ` Thomas Huth
2021-07-28 10:13 ` [kvm-unit-tests PATCH 2/3] s390x: Add SPDX and header comments for the snippets folder Janosch Frank
2021-07-28 10:28   ` Claudio Imbrenda
2021-07-28 10:33   ` Thomas Huth
2021-07-28 10:13 ` [kvm-unit-tests PATCH 3/3] s390x: Fix my mail address in the headers Janosch Frank
2021-07-28 10:28   ` Claudio Imbrenda
2021-07-28 10:34   ` Thomas Huth

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=d1c3e9f0-57c0-e941-3e3f-94a897ace177@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=thuth@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