From: Wolfram Sang <w.sang@pengutronix.de>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: Zhao Chenhui-B35336 <B35336@freescale.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c-mpc: avoid I2C abnormal after resuming from deep sleep
Date: Wed, 18 Apr 2012 12:33:34 +0200 [thread overview]
Message-ID: <20120418103334.GD2232@pengutronix.de> (raw)
In-Reply-To: <94F013E7935FF44C83EBE7784D62AD3F092D1DC7@039-SN2MPN1-022.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hi,
> We certainly don't want the policy to be against the common practice
> of the community. If it is we can consider changing our policy.
Nice, thanks for being open to discussion!
> However I can't find a clear message stating the consensus of what the
> Linux kernel community think of adding copyright claims. I even found
Well, what I know, the consensus is "common sense". What is obviously
not "clear" in a way you could write it down. At least, Ben agrees.
> some message that encourage adding copyright to maintain the GPL
> license.
I am interested. Do you have a link?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-18 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 10:39 [PATCH] i2c-mpc: avoid I2C abnormal after resuming from deep sleep Zhao Chenhui
2012-02-29 13:02 ` Shubhrajyoti Datta
2012-02-29 18:08 ` Tabi Timur-B04825
2012-02-29 18:45 ` Wolfram Sang
2012-03-01 11:27 ` Ben Dooks
2012-04-17 14:21 ` Wolfram Sang
2012-04-18 10:20 ` Li Yang-R58472
2012-04-18 10:33 ` Wolfram Sang [this message]
2012-04-18 14:44 ` Li Yang
2012-04-18 21:49 ` Tabi Timur-B04825
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=20120418103334.GD2232@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=B35336@freescale.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r58472@freescale.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