From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>, Juerg Haefliger <juergh@gmail.com>
Subject: Re: linux-next: manual merge of the hwmon-staging tree with the jdelvare-hwmon tree
Date: Mon, 10 Jan 2011 02:16:23 -0800 [thread overview]
Message-ID: <20110110101623.GA29314@ericsson.com> (raw)
In-Reply-To: <20110110095743.7616b7b3@endymion.delvare>
On Mon, Jan 10, 2011 at 03:57:43AM -0500, Jean Delvare wrote:
> On Sun, 9 Jan 2011 19:46:38 -0800, Guenter Roeck wrote:
> > On Sun, Jan 09, 2011 at 09:20:57PM -0500, Stephen Rothwell wrote:
> > > Hi Guenter,
> > >
> > > Today's linux-next merge of the hwmon-staging tree got a conflict in
> > > drivers/hwmon/dme1737.c between commit
> > > b7f2a5c8c9190fcf0126d43972a8ad37eb98f5d0 ("hwmon: (dme1737) Minor
> > > cleanups") from the jdelvare-hwmon tree and commit
> > > 9c6e13b411cf0f656b7d7a78ec35bf0069f631bb ("hwmon: (dme1737) Use pr_fmt
> > > and pr_<level>") from the hwmon-staging tree.
> > >
> > > Just context changes. I fixed it up (see below) and can carry the fix as
> > > necessary.
> > > --
> > > Cheers,
> > > Stephen Rothwell sfr@canb.auug.org.au
> > >
> > Hi Stephen,
> >
> > thanks for the note. I suspected that would happen - sorry for the trouble.
> >
> > Jean, do you want to take Joe's pr_fmt change from my tree and apply it to yours,
> > or should we just wait until the first of the trees was merged into Linus' tree ?
> > If the latter, do you want to send your patches to Linus first, or should I go first ?
> > I am ready to go.
>
> Let's be good citizens and sort out the conflict before sending the
> patches to Linus. I shall pick the pr_fmt change patch in my own tree.
>
> But where do I pick it?
> ftp://pub.kernel.org/pub/linux/kernel/people/groeck/linux-staging/ is
> no longer relevant, right? Maybe you can delete it altogether to clear
> up the confusion. Care to point me to somewhere I can download the
> pr_fmt change patch?
>
Try again; I updated it.
hwmon-next/0007-hwmon-dme1737-Use-pr_fmt-and-pr_-level.patch
In general, I keep my git tree up to date.
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/staging.git
You can get it from there as well.
> As for sending your patches to Linus for 2.6.38, yes, please send them
> as soon as possible. I am still not done processing all the mails I
> received during my vacation, and I must send my i2c patches too, so
> it's better if you don't wait for me and send your patches first.
>
Ok. Do you want me to take out the dme1737 patch ?
Guenter
next prev parent reply other threads:[~2011-01-10 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 2:20 linux-next: manual merge of the hwmon-staging tree with the jdelvare-hwmon tree Stephen Rothwell
2011-01-10 3:46 ` Guenter Roeck
2011-01-10 4:32 ` Stephen Rothwell
2011-01-10 8:57 ` Jean Delvare
2011-01-10 10:16 ` Guenter Roeck [this message]
2011-01-10 10:47 ` Jean Delvare
2011-01-10 11:11 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2011-02-21 1:19 Stephen Rothwell
2011-02-21 2:17 ` Guenter Roeck
2011-02-21 2:31 ` Stephen Rothwell
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=20110110101623.GA29314@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=joe@perches.com \
--cc=juergh@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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