linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Laurent Pinchart <laurentp@cse-semaphore.com>,
	Jochen Friedrich <jochen@scram.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Alessandro Zummo <alessandro.zummo@towertech.it>,
	i2c@lm-sensors.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH] rtc-pcf8563: Add device ids table
Date: Wed, 23 Apr 2008 14:47:56 +0200	[thread overview]
Message-ID: <20080423144756.3fc9b1bf@hyperion.delvare> (raw)
In-Reply-To: <200804231412.40038.laurentp@cse-semaphore.com>

On Wed, 23 Apr 2008 14:12:37 +0200, Laurent Pinchart wrote:
> On Wednesday 23 April 2008 13:16, Jean Delvare wrote:
> > I still don't know exactly what happened there... I think I saw some
> > "OpenFirmware i2c" patches go upstream yesterday? But not the ones
> > listed below, which I thought they depended upon.
> 
> The code that went upstream introduces helper functions to create i2c devices 
> from information supplied by the OF device tree. It doesn't strictly depend 
> on the below patches, but the new devices won't be properly bound to a driver 
> without them.

OK. So... Out of the 7 patches Jochen sent originally, only 1 ([3/7] OF
helpers for the i2c API) went upstream. Am I correct?

Jochen, I'm a bit confused by the dependencies that exist - or not -
between these 7 patches you sent at once. I thought they had to be
applied in sequence but it seems not? And some of them should
apparently go through me i2c tree but others (e.g. [7/7]) not?

I would appreciate if you could summarize quickly which patches depend
on others in which way. If we can make smaller subsets of patches, that
will be easier for me to review and push upstream on my limited time.

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2008-04-23 12:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804171708.32847.laurentp@cse-semaphore.com>
     [not found] ` <20080418235451.2643183b@i1501.lan.towertech.it>
     [not found]   ` <20080419113417.19f5567a@hyperion.delvare>
     [not found]     ` <4809EF23.7070902@scram.de>
     [not found]       ` <20080419162358.746b714c@hyperion.delvare>
2008-04-19 16:43         ` [PATCH] rtc-pcf8563: Add device ids table Jochen Friedrich
2008-04-21 11:56           ` Laurent Pinchart
2008-04-21 12:12             ` Stefan Roese
2008-04-23 11:09               ` Jean Delvare
2008-04-23 11:35                 ` Stefan Roese
2008-04-23 11:45                   ` Jochen Friedrich
2008-04-22 14:11           ` Laurent Pinchart
2008-04-23 11:16             ` Jean Delvare
2008-04-23 12:12               ` Laurent Pinchart
2008-04-23 12:47                 ` Jean Delvare [this message]
2008-04-23 13:26                   ` Jochen Friedrich
2008-04-23 13:46                     ` Jon Smirl
2008-04-27 12:18                     ` Jean Delvare
2008-04-23 13:53                   ` Laurent Pinchart
2008-04-23 13:11               ` Jon Smirl
2008-04-17 15:02 Laurent Pinchart
2008-04-17 15:05 ` Kumar Gala

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=20080423144756.3fc9b1bf@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=i2c@lm-sensors.org \
    --cc=jochen@scram.de \
    --cc=laurentp@cse-semaphore.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rtc-linux@googlegroups.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).