From: Grant Likely <grant.likely@secretlab.ca>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Jassi Brar' <jassisinghbrar@gmail.com>,
'padma venkat' <padma.kvr@gmail.com>,
'Tony Nadackal' <tonykn@gmail.com>,
'Padmavathi Venna' <padma.v@samsung.com>,
sbkim73@samsung.com, spi-devel-general@lists.sourceforge.net,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, tony.kn@samsung.com,
naushad@samsung.com
Subject: Re: [PATCH 2/2] SPI: SAMSUNG: Bug fix for SPI with different FIFO level
Date: Wed, 6 Jul 2011 00:30:27 -0600 [thread overview]
Message-ID: <20110706063027.GK9978@ponder.secretlab.ca> (raw)
In-Reply-To: <00c101cc3ba5$0b573910$2205ab30$%kim@samsung.com>
On Wed, Jul 06, 2011 at 03:22:08PM +0900, Kukjin Kim wrote:
> Kukjin Kim wrote:
> >
> > Grant Likely wrote:
> > >
> > > On Mon, Jul 04, 2011 at 07:08:55PM +0900, Kukjin Kim wrote:
> > > > Kukjin Kim wrote:
> > > > >
> > > > > Thanks Grant, Jassi and all,
> > > > >
> > > > > I will apply these 1 and 2 in my -fix tree for 3.0 with your acks.
> > > > >
> > > > Oops, this needs previous 'cleanup spi platform specific code' so
> can't
> > > > apply -fix tree now.
> > >
> > > There may also be conflicts with the heavy rework in the spi tree.
> > > Kgene, when you pick up this series, can you put it into a separate
> > > topic branch and merge that into your main tree? That way if there
> > > are difficult conflicts, then I can also merge that same topic branch
> > > into spi/next to resolve them.
> > >
> > Hi Grant,
> >
> > Sure, no problem. I'm waiting for Padmavathi's new patch which is based on
> old
> > code not new SPI code. When I merge topic branch for this into my tree,
> let you
> > know immediately. Then if any problems, let's talk again :)
>
> Hi,
>
> I made topic branch for this based on 3.0-rc6.
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> #for-spi
Okay. If there are problems, then I'll merge it. Thanks.
g.
next prev parent reply other threads:[~2011-07-06 6:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 12:38 [PATCH 1/2] ARM: SAMSUNG: Added tx_st_done variable in the platform data of SPI Padmavathi Venna
2011-06-30 12:38 ` [PATCH 2/2] SPI: SAMSUNG: Bug fix for SPI with different FIFO level Padmavathi Venna
2011-06-30 7:08 ` Jassi Brar
2011-06-30 9:05 ` padma venkat
2011-06-30 9:52 ` Jassi Brar
[not found] ` <BANLkTi=9c5asfr=Jg6xwjQZW_a369UO64Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-30 11:00 ` Tony Nadackal
2011-07-01 5:46 ` padma venkat
2011-07-01 5:52 ` Jassi Brar
2011-07-01 5:59 ` padma venkat
2011-07-01 6:13 ` Jassi Brar
2011-07-04 6:55 ` Grant Likely
2011-07-04 6:58 ` Grant Likely
2011-07-04 9:54 ` Kukjin Kim
2011-07-04 10:04 ` padma venkat
2011-07-04 10:08 ` Kukjin Kim
2011-07-04 15:06 ` Grant Likely
2011-07-05 5:51 ` Kukjin Kim
2011-07-06 6:22 ` Kukjin Kim
2011-07-06 6:30 ` Grant Likely [this message]
2011-07-06 7:17 ` Kukjin Kim
2011-07-06 17:30 ` 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=20110706063027.GK9978@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=jassisinghbrar@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naushad@samsung.com \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@samsung.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tony.kn@samsung.com \
--cc=tonykn@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;
as well as URLs for NNTP newsgroup(s).