linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-next@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: linux-next: i2c build failure
Date: Thu, 15 May 2008 20:39:57 +1000	[thread overview]
Message-ID: <20080515203957.6a35eb19.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080515102215.62378c4f@hyperion.delvare>

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Hi Jean,

On Thu, 15 May 2008 10:22:15 +0200 Jean Delvare <khali@linux-fr.org> wrote:
>
> Thanks for the notification and sorry for the trouble. I thought that I
> knew about all users of struct i2c_board_info and that they were all
> converted by now but obviously not. I didn't know that fsl_soc.c had
> been partly forked for the pasemi platform.

This is one of the reasons linux-next is here.  However, grep -R (or git
grep) is you friend. :-)


> Stephen, I'm updating my i2c tree now and you'll get this patch under
> the name i2c-02-switch-pasemi-to-module-aliases.patch. Note that this
> will cause one more conflict with Greg KH driver tree, which you can
> solve the same way you solved the other ones.

OK, that will be in linux-next tomorrow.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-15 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  2:12 linux-next: i2c build failure Stephen Rothwell
2008-05-15  8:22 ` Jean Delvare
2008-05-15 10:39   ` Stephen Rothwell [this message]
2008-05-15 19:47   ` Olof Johansson
2008-05-23  1:32 Stephen Rothwell
2008-05-23  1:58 ` Greg KH

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=20080515203957.6a35eb19.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=khali@linux-fr.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).