From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
me@jue.yt, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
wsa@the-dreams.de, Juergen Fitschen <jfi@ssv-embedded.de>
Subject: Re: [PATCH v4 3/3] i2c: at91: added slave mode support
Date: Mon, 31 Dec 2018 12:53:48 +0200 [thread overview]
Message-ID: <20181231105348.GV10650@smile.fi.intel.com> (raw)
In-Reply-To: <20181227151311.20107-4-ludovic.desroches@microchip.com>
> Slave mode driver is based on the concept of i2c-designware driver.
> +/*
> + * i2c slave support for Atmel's AT91 Two-Wire Interface (TWI)
> + *
> + * Copyright (C) 2017 Juergen Fitschen <me@jue.yt>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + */
Perhaps, you can use SPDX instead of boiler plate license text in the files?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-12-31 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 15:13 [PATCH v4 0/3] i2c: at91: slave mode support Ludovic Desroches
2018-12-27 15:13 ` [PATCH v4 1/3] i2c: at91: segregate master mode specific code from probe and init func Ludovic Desroches
2018-12-27 15:13 ` [PATCH v4 2/3] i2c: at91: split driver into core and master file Ludovic Desroches
2018-12-27 15:13 ` [PATCH v4 3/3] i2c: at91: added slave mode support Ludovic Desroches
2018-12-31 10:53 ` Andy Shevchenko [this message]
2019-01-01 10:23 ` Wolfram Sang
2019-01-04 19:37 ` kbuild test robot
2019-01-15 22:43 ` Wolfram Sang
2019-02-15 9:18 ` Wolfram Sang
2019-02-20 6:32 ` Ludovic Desroches
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=20181231105348.GV10650@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jfi@ssv-embedded.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=me@jue.yt \
--cc=nicolas.ferre@microchip.com \
--cc=wsa@the-dreams.de \
/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).