All of lore.kernel.org
 help / color / mirror / Atom feed
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 03:11:44 -0800	[thread overview]
Message-ID: <20110110111144.GA29501@ericsson.com> (raw)
In-Reply-To: <20110110114750.7e1849ea@endymion.delvare>

On Mon, Jan 10, 2011 at 05:47:50AM -0500, Jean Delvare wrote:
> On Mon, 10 Jan 2011 02:16:23 -0800, Guenter Roeck wrote:
> > On Mon, Jan 10, 2011 at 03:57:43AM -0500, Jean Delvare wrote:
> > > 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
> 
> Hmm, apparently syncing is down or slow, I don't see it yet. Will look
> again later.
> 
> > 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 ?
> 
> If you send your patches to Linus today, it doesn't actually make a
> difference. So, whatever is easier for you.
> 
Ok, let's do it that way.

Sorry for the whole trouble. The patches you applied do not follow
Documentation/CodingStyle, and I did not want to apply them without your
approval. I thought I sent you a note, but looks like that got lost in my own
vacation.

Guenter

  reply	other threads:[~2011-01-10 11:12 UTC|newest]

Thread overview: 12+ 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  8:57     ` Jean Delvare
2011-01-10 10:16     ` Guenter Roeck
2011-01-10 10:47       ` Jean Delvare
2011-01-10 10:47         ` Jean Delvare
2011-01-10 11:11         ` Guenter Roeck [this message]
  -- 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=20110110111144.GA29501@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.