From: Joe Perches <joe@perches.com>
To: Nasir Abed <nasirabed+kernel@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: alarm: Renamed pr_alarm to alarm_dbg
Date: Mon, 21 May 2012 14:15:41 -0700 [thread overview]
Message-ID: <1337634941.13812.42.camel@joe2Laptop> (raw)
In-Reply-To: <CAMXkaZEhDaj_qtPp8wu315HD1Nw_nK88cuZ1_jpaWqf8y1qvow@mail.gmail.com>
On Mon, 2012-05-21 at 23:04 +0200, Nasir Abed wrote:
> I am using: http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
A couple bits of advice:
Please read Documentation/development-process
When doing cleanup work, always start with the latest
next-YYYYMMDD tagged entry in Stephen Rothwell's -next tree
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
This is old and out-of-date, but it contains some clues
how -next works.
http://linux.f-seidel.de/linux-next/pmwiki/pmwiki.php?n=Linux-next.FAQ
cheers, Joe
prev parent reply other threads:[~2012-05-21 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 19:44 Nasir Abed
2012-05-21 20:14 ` Joe Perches
2012-05-21 21:04 ` Nasir Abed
2012-05-21 21:15 ` Joe Perches [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=1337634941.13812.42.camel@joe2Laptop \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nasirabed+kernel@gmail.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
all inboxes | Powered by JetHome®