From: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
Ben Dooks <ben-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
Subject: Re: [PATCH 0/5] remove spi-s3c24xx-gpio driver
Date: Wed, 29 Jun 2011 19:51:10 +0200 [thread overview]
Message-ID: <87ei2c4jch.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BANLkTi=693aHH=8BTAyrKWc1padiozpT6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Grant Likely's message of "Wed, 29 Jun 2011 11:17:51 -0600")
>>>>> "Grant" == Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> writes:
>> Great, will you handle the series or should it go through the spi tree?
Grant> With the big spi driver rename, it should probably either go via the
Grant> spi tree, or be put into a topic branch that can be merged by both the
Grant> spi and samsung trees.
Both is fine by me. Let me know if you want me to do something.
--
Bye, Peter Korsgaard
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
WARNING: multiple messages have this Message-ID (diff)
From: jacmet@sunsite.dk (Peter Korsgaard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] remove spi-s3c24xx-gpio driver
Date: Wed, 29 Jun 2011 19:51:10 +0200 [thread overview]
Message-ID: <87ei2c4jch.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BANLkTi=693aHH=8BTAyrKWc1padiozpT6A@mail.gmail.com> (Grant Likely's message of "Wed, 29 Jun 2011 11:17:51 -0600")
>>>>> "Grant" == Grant Likely <grant.likely@secretlab.ca> writes:
>> Great, will you handle the series or should it go through the spi tree?
Grant> With the big spi driver rename, it should probably either go via the
Grant> spi tree, or be put into a topic branch that can be merged by both the
Grant> spi and samsung trees.
Both is fine by me. Let me know if you want me to do something.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-06-29 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 12:49 [PATCH 0/5] remove spi-s3c24xx-gpio driver Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
2011-06-28 12:49 ` [PATCH 3/5] mach-gta2: remove unused spi-gpio.h include Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
[not found] ` <1309265357-15879-1-git-send-email-jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
2011-06-28 12:49 ` [PATCH 1/5] mach-jive: convert to spi_gpio Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
2011-06-28 12:49 ` [PATCH 2/5] mach-qt2410: " Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
2011-06-28 12:49 ` [PATCH 4/5] spi: remove obsolete spi-s3c24xx-gpio driver Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
2011-06-28 12:49 ` [PATCH 5/5] mach-s3c2410: remove unused spi-gpio.h file Peter Korsgaard
2011-06-28 12:49 ` Peter Korsgaard
2011-06-28 21:24 ` [PATCH 0/5] remove spi-s3c24xx-gpio driver Ben Dooks
2011-06-28 21:24 ` Ben Dooks
2011-06-29 17:00 ` Peter Korsgaard
2011-06-29 17:00 ` Peter Korsgaard
2011-06-29 17:17 ` Grant Likely
2011-06-29 17:17 ` Grant Likely
[not found] ` <BANLkTi=693aHH=8BTAyrKWc1padiozpT6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-29 17:51 ` Peter Korsgaard [this message]
2011-06-29 17:51 ` Peter Korsgaard
2011-07-04 16:51 ` Grant Likely
2011-07-04 16:51 ` Grant Likely
2011-07-05 5:45 ` Kukjin Kim
2011-07-05 5:45 ` Kukjin Kim
2011-07-04 16:48 ` Grant Likely
2011-07-04 16:48 ` Grant Likely
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=87ei2c4jch.fsf@macbook.be.48ers.dk \
--to=jacmet-ofaju3cklf1/szgsgea1oa@public.gmane.org \
--cc=ben-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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 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.