From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Define some additional always off clocks
Date: Fri, 2 Dec 2011 22:25:55 +0000 [thread overview]
Message-ID: <20111202222555.GA4986@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1908355.tlHtlhx9rP@flatron>
On Fri, Dec 02, 2011 at 10:31:26PM +0100, Tomasz Figa wrote:
> OK, I will start adding sign offs from now on. I'm not experienced in
> submitting patches to mainline and I didn't know about importance of them.
Yeah, basically Signed-off-by is a purely legal thing - it means that
you're saying that you know where the code came from and that there's no
legal issue submitting it (see the full text in SubmittingPatches before
you start doing this!) so if someone else takes your work they should
keep your signoff.
> I have much more things that I should have submitted already long time ago,
> it's a shame that I can't find time to do that. The whole tree is dedicated to
> features and fixes needed to run Linux on mobile devices with S3C6410 (Samsung
> Galaxy Spica GT-i5700 in particular), but I work on it in my free time, which
> usually is pretty limited.
Hopefully other people can help you out there - it's great having the
code at all. I know I saw a few things that might be interesting for my
systems.
prev parent reply other threads:[~2011-12-02 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 15:57 [PATCH] ARM: S3C64XX: Define some additional always off clocks Mark Brown
2011-12-02 19:16 ` Tomasz Figa
2011-12-02 19:37 ` Mark Brown
2011-12-02 19:45 ` Tomasz Figa
2011-12-02 21:13 ` Mark Brown
2011-12-02 21:31 ` Tomasz Figa
2011-12-02 22:25 ` Mark Brown [this message]
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=20111202222555.GA4986@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).