From: Andrew Morton <akpm@linux-foundation.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Alessandro Zummo <a.zummo@towertech.it>,
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: [RFC][PATCH 2/4] RTC: SWARM I2C board initialization
Date: Wed, 7 May 2008 00:08:53 -0700 [thread overview]
Message-ID: <20080507000853.17f1316b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080507085953.2c08b854@hyperion.delvare>
On Wed, 7 May 2008 08:59:53 +0200 Jean Delvare <khali@linux-fr.org> wrote:
> I'm not sure how you intend to push these changes upstream. I would
> take a patch only touching drivers/i2c/busses/i2c-sibyte.c in my i2c
> tree, however a patch also touching arch code, must be handled be the
> maintainer for that architecture or platform.
Not "must". The arch maintainer could ask you to merge it or you could ask
the arch maintainer to merge it.
It's some little one-line change like this one appeared to be, it's
fair to assume the arch maintainer won't care much about it. View it as an
i2c patch?
next prev parent reply other threads:[~2008-05-07 7:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 0:40 [RFC][PATCH 2/4] RTC: SWARM I2C board initialization Maciej W. Rozycki
2008-05-07 6:59 ` Jean Delvare
2008-05-07 7:08 ` Andrew Morton [this message]
2008-05-07 21:13 ` Maciej W. Rozycki
2008-05-08 4:51 ` Ralf Baechle
2008-05-08 22:43 ` Maciej W. Rozycki
2008-05-08 8:59 ` Jean Delvare
2008-05-08 23:10 ` Maciej W. Rozycki
2008-05-09 7:28 ` Jean Delvare
2008-05-09 20:27 ` Maciej W. Rozycki
2008-05-09 20:38 ` Jean Delvare
2008-05-10 1:43 ` Maciej W. Rozycki
2008-05-07 7:05 ` Jean Delvare
2008-05-07 7:37 ` Geert Uytterhoeven
2008-05-07 7:43 ` Jean Delvare
2008-05-07 21:25 ` Maciej W. Rozycki
2008-05-08 4:57 ` Ralf Baechle
2008-05-08 7:56 ` Jean Delvare
2008-05-09 19:36 ` 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=20080507000853.17f1316b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.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