From: David Brown <davidb@codeaurora.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Kenneth Heitke <kheitke@codeaurora.org>,
dima@android.com, linux-arm-msm@vger.kernel.org,
tsoni@codeaurora.org, linux-arm-kernel@lists.infradead.org,
swetland@google.com, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver
Date: Fri, 25 Feb 2011 11:00:27 -0800 [thread overview]
Message-ID: <8yak4go9bxw.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1298600621.17118.27.camel@m0nster> (Daniel Walker's message of "Thu, 24 Feb 2011 18:23:41 -0800")
On Thu, Feb 24 2011, Daniel Walker wrote:
>> Based on a patch by Dima Zavin <dima@android.com> that can be found at:
>> http://android.git.kernel.org/?p=kernel/msm.git;a=commitdiff;h=eb060bac4
>
> I don't really like links in the commit text, cause as soon as Google
> deletes this tree the link is worthless.
I'm not sure how to better convey the information. The tree is at least
on kernel.org, and there's good useful information there that works
now. Links in commit text seem fairly common.
I think it is helpful to demonstrate that Ken is trying to be diligent
about indicating where the code comes from.
Thanks,
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver
Date: Fri, 25 Feb 2011 11:00:27 -0800 [thread overview]
Message-ID: <8yak4go9bxw.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1298600621.17118.27.camel@m0nster> (Daniel Walker's message of "Thu, 24 Feb 2011 18:23:41 -0800")
On Thu, Feb 24 2011, Daniel Walker wrote:
>> Based on a patch by Dima Zavin <dima@android.com> that can be found at:
>> http://android.git.kernel.org/?p=kernel/msm.git;a=commitdiff;h=eb060bac4
>
> I don't really like links in the commit text, cause as soon as Google
> deletes this tree the link is worthless.
I'm not sure how to better convey the information. The tree is at least
on kernel.org, and there's good useful information there that works
now. Links in commit text seem fairly common.
I think it is helpful to demonstrate that Ken is trying to be diligent
about indicating where the code comes from.
Thanks,
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-02-25 19:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 22:19 [PATCH v2 0/2] msm: add single-wire serial bus interface (SSBI) driver Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` [PATCH v2 1/2] MAINTAINERS: Add drivers/msm to MSM subsystem Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 23:08 ` Nicolas Pitre
2011-02-24 23:08 ` Nicolas Pitre
2011-02-24 22:19 ` [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-25 2:23 ` Daniel Walker
2011-02-25 2:23 ` Daniel Walker
2011-02-25 2:31 ` David Brown
2011-02-25 2:31 ` David Brown
2011-02-25 2:35 ` Daniel Walker
2011-02-25 2:35 ` Daniel Walker
2011-02-25 2:39 ` Dima Zavin
2011-02-25 2:39 ` Dima Zavin
2011-02-25 3:20 ` David Brown
2011-02-25 3:20 ` David Brown
2011-02-25 3:28 ` Greg KH
2011-02-25 3:28 ` Greg KH
2011-02-25 3:54 ` David Brown
2011-02-25 3:54 ` David Brown
2011-02-25 3:58 ` Greg KH
2011-02-25 3:58 ` Greg KH
2011-02-25 4:06 ` David Brown
2011-02-25 4:06 ` David Brown
2011-02-25 19:00 ` David Brown [this message]
2011-02-25 19:00 ` David Brown
2011-02-25 20:21 ` Brian Swetland
2011-02-25 20:21 ` Brian Swetland
2011-02-25 20:21 ` Brian Swetland
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=8yak4go9bxw.fsf@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=dima@android.com \
--cc=dwalker@fifo99.com \
--cc=kheitke@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=tsoni@codeaurora.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 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.