From: Jean Delvare <khali@linux-fr.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Andrew Morton <akpm@linux-foundation.org>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
David Woodhouse <dwmw2@infradead.org>,
Ralf Baechle <ralf@linux-mips.org>,
Thomas Gleixner <tglx@linutronix.de>,
rtc-linux@googlegroups.com, i2c@lm-sensors.org,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] RTC: SWARM I2C board initialization (#2)
Date: Tue, 13 May 2008 19:17:32 +0200 [thread overview]
Message-ID: <20080513191732.259d0ab2@hyperion.delvare> (raw)
In-Reply-To: <Pine.LNX.4.55.0805131747590.7267@cliff.in.clinika.pl>
On Tue, 13 May 2008 17:51:32 +0100 (BST), Maciej W. Rozycki wrote:
> > > I have renamed i2c-swarm.c to swarm-i2c.c for consistency with names
> > > of other files under arch/mips/.
> >
> > But you forgot to update the log message accordingly...
>
> I did not, unless I am missing something.
printk(KERN_ERR
"i2c-swarm: cannot register board I2C devices\n");
> > > Please note this patch trivially depends on
> > > patch-2.6.26-rc1-20080505-swarm-core-16 -- 2/6 of this set.
> >
> > OK, so I should just wait for patch 2/6 to get upstream before I add
> > this one to my i2c tree?
>
> Either this or you can apply both and remove the local copy of the former
> when it comes back from upstream. Whatever you prefer -- it is your
> choice.
I don't really want to include a mips arch patch in my public i2c tree,
that would be confusing. I think I'll just wait. I have the mips patch
in my local tree, so quilt will tell me when it hits upstream.
--
Jean Delvare
next prev parent reply other threads:[~2008-05-13 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 3:27 [PATCH 3/6] RTC: SWARM I2C board initialization (#2) Maciej W. Rozycki
2008-05-13 11:34 ` Jean Delvare
2008-05-13 16:51 ` Maciej W. Rozycki
2008-05-13 17:17 ` Jean Delvare [this message]
2008-05-13 17:53 ` Maciej W. Rozycki
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=20080513191732.259d0ab2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=dwmw2@infradead.org \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
/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).