devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
	Dragos Bogdan <dragos.bogdan@analog.com>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
	devicetree@vger.kernel.org, kernel-usp@googlegroups.com
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: ad7292: Update SPDX identifier
Date: Sat, 23 Nov 2019 12:25:48 +0000	[thread overview]
Message-ID: <20191123122548.54f0f529@archlinux> (raw)
In-Reply-To: <CAL_JsqJzi_0eYj=rMxwQe+OTh_m3ngocOvcPZd-tykAwAJAw6g@mail.gmail.com>

On Fri, 22 Nov 2019 10:05:52 -0600
Rob Herring <robh@kernel.org> wrote:

> On Sat, Nov 16, 2019 at 2:50 PM Marcelo Schmitt
> <marcelo.schmitt1@gmail.com> wrote:
> >
> > Update SPDX identifier to the preferred dual GPL-2.0 OR BSD-2-Clause
> > licensing.
> >
> > Signed-off-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
> > ---
> > I split the changes into 2 different patches since they are about
> > different issues.
> >
> >  Documentation/devicetree/bindings/iio/adc/adi,ad7292.yaml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)  
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
I've applied this to the fixes-togreg branch so it'll go in during
the early RCs.  Nice not to have a release with a different
license, particularly as this was me running too fast at taking
patches.

Thanks,

Jonathan



  reply	other threads:[~2019-11-23 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 20:50 [PATCH 1/2] dt-bindings: iio: adc: ad7292: Update SPDX identifier Marcelo Schmitt
2019-11-22 16:05 ` Rob Herring
2019-11-23 12:25   ` Jonathan Cameron [this message]
2019-12-02 16:48     ` Rob Herring
2019-12-08 19:14       ` Jonathan Cameron

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=20191123122548.54f0f529@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragos.bogdan@analog.com \
    --cc=kernel-usp@googlegroups.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=robh@kernel.org \
    /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).