All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Carlos Henrique Lima Melara <charlesmelara@outlook.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"neil@brown.name" <neil@brown.name>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] staging: mt7621-eth/ethtool.c: Correction of SPDX license identifier
Date: Wed, 30 Jan 2019 19:48:33 +0100	[thread overview]
Message-ID: <20190130184833.GF15050@lunn.ch> (raw)
In-Reply-To: <20190130181005.GA15653@kroah.com>

> See the patch about all of this from Thomas on lkml yesterday for
> why this is the case.

Hi Greg

Thanks for the info. I had not seen this, and i guess other have not
as well. So here is a link to the patch.

https://lkml.org/lkml/2019/1/28/1975

	Andrew

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Carlos Henrique Lima Melara <charlesmelara@outlook.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"neil@brown.name" <neil@brown.name>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] staging: mt7621-eth/ethtool.c: Correction of SPDX license identifier
Date: Wed, 30 Jan 2019 19:48:33 +0100	[thread overview]
Message-ID: <20190130184833.GF15050@lunn.ch> (raw)
In-Reply-To: <20190130181005.GA15653@kroah.com>

> See the patch about all of this from Thomas on lkml yesterday for
> why this is the case.

Hi Greg

Thanks for the info. I had not seen this, and i guess other have not
as well. So here is a link to the patch.

https://lkml.org/lkml/2019/1/28/1975

	Andrew

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-30 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 14:48 [PATCH v2] staging: mt7621-eth/ethtool.c: Correction of SPDX license identifier Carlos Henrique Lima Melara
2019-01-30 14:48 ` Carlos Henrique Lima Melara
2019-01-30 15:29 ` gregkh
2019-01-30 15:29   ` gregkh
2019-01-30 20:01   ` Carlos Henrique Lima Melara
2019-01-30 20:01     ` Carlos Henrique Lima Melara
2019-01-30 21:12     ` gregkh
2019-01-30 21:12       ` gregkh
2019-01-30 16:38 ` Andrew Lunn
2019-01-30 16:38   ` Andrew Lunn
2019-01-30 18:10   ` gregkh
2019-01-30 18:10     ` gregkh
2019-01-30 18:48     ` Andrew Lunn [this message]
2019-01-30 18:48       ` Andrew Lunn

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=20190130184833.GF15050@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=charlesmelara@outlook.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=neil@brown.name \
    /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.