From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: "Kim, Heung Jun" <riverful-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: what repo can I base patch works?
Date: Fri, 9 Jul 2010 09:56:40 -0600 [thread overview]
Message-ID: <AANLkTil1rOzwgykIRHDLL9aw7IqJGA7zYWbPV-bl67F_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTineorwtg3hSlb8-9-LlQpdMXLujNt0JhxG_p-N5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Jul 9, 2010 at 9:15 AM, Kim, Heung Jun <riverful-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi everyone,
>
> I have a question.
>
> I found a spi_gpio framework issue need to be changed, so I to make
> the patch based git://git.secretlab.ca/linux-2.6 next-spi.
> Is it right?? what repo can I base patch works?
Yes, you can either base your patch on next-spi or on against Linus'
tree. If anything is sufficiently complex that it won't merge, then
I'll ask you to help me rebase it, but usually that isn't a problem.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
prev parent reply other threads:[~2010-07-09 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 15:15 what repo can I base patch works? Kim, Heung Jun
[not found] ` <AANLkTineorwtg3hSlb8-9-LlQpdMXLujNt0JhxG_p-N5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-09 15:56 ` Grant Likely [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=AANLkTil1rOzwgykIRHDLL9aw7IqJGA7zYWbPV-bl67F_@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=riverful-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).