linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Li Yang-R58472 <r58472-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Zhao Chenhui-B35336
	<B35336-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-RL0Hj/+nBVC81RJBUSuqCa4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>

[-- 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 --]

  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
     [not found] ` <1330511961-22498-1-git-send-email-chenhui.zhao-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-02-29 13:02   ` Shubhrajyoti Datta
     [not found]     ` <CAM=Q2ctLm8FKgTek6u9H0jzWJv1bbBUnvDHZfEA=p2ReK8ybUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-29 18:08       ` Tabi Timur-B04825
2012-02-29 18:45   ` Wolfram Sang
     [not found]     ` <20120229183436.GA30545-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-03-01 11:27       ` Ben Dooks
2012-04-17 14:21       ` Wolfram Sang
     [not found]         ` <20120417142105.GA21802-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-18 10:20           ` Li Yang-R58472
     [not found]             ` <94F013E7935FF44C83EBE7784D62AD3F092D1DC7-RL0Hj/+nBVC81RJBUSuqCa4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2012-04-18 10:33               ` Wolfram Sang [this message]
     [not found]                 ` <20120418103334.GD2232-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-18 14:44                   ` Li Yang
     [not found]                     ` <CADRPPNQRLyZK-zjeLUYCZtLe+8HhFzFALCMyPeaCGX+buaf+ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=B35336-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=r58472-KZfg59tc24xl57MIdRCFDg@public.gmane.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).