All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] patches vs. 2.6.22 for release - last chance
Date: Thu, 19 Jul 2007 18:27:55 +0000	[thread overview]
Message-ID: <469FAD2B.8070200@hhs.nl> (raw)
In-Reply-To: <20070718203038.GC3406@jupiter.solarsys.private>

Mark M. Hoffman wrote:
> Hi Hans:
> 
> * Hans de Goede <j.w.r.degoede@hhs.nl> [2007-07-18 23:28:16 +0200]:
>> Mark M. Hoffman wrote:
>>> Hi all:
>>>
>>> I'm back from my vacation, and of course the email has piled up.
>>>
>>> Linus released 2.6.22 so I've updated my testing and release trees; they 
>>> are
>>> now identical:
>>>
>>> http://lm-sensors.org/kernel?p=kernel/mhoffman/hwmon-2.6.git;a=shortlog;h=release
>>>
>>> Unless I hear good reasons, I'll ask Linus to pull from this tomorrow.
>>>
>>> Also, I realize there's still a backlog of patches.  In the past, Linus has
>>> not objected to merging brand new drivers in addition to bugfixes after 
>>> -rc1,
>>> so I think there is still the chance to get some of these in if we can work
>>> quickly.  Unfortunately, the alarm file patches qualify as neither of 
>>> these,
>>> so they'll have to wait until the next round.
>>>
>> Mark can you please drop the:
>> "hwmon: fix Abit Uguru3 driver detection on some motherboards" Patch, there 
>> is an updated version in your inbox with skips the dmi vendor check when 
>> the force module param is present.
>>
>> If that is a problem I can make that an incremental patch.
> 
> No problem, I've dropped it.  We'll try to get the updated one in after -rc1.
> 
> BTW: I would have liked to keep a consistent revision history on my release
> branch, but of course dropping a patch will blow that up.  I could just revert
> it to keep the history intact, but I don't think Linus considers *that* to be
> kosher for *him* to pull from.  My mistake, basically: I should have updated
> just the testing tree, and only updated the release tree just before asking
> Linus to pull.  Next time around, that's what I'll do.
> 
> So for other GIT users out there... what this means is if you pulled from my
> release branch yesterday, you should blow that away and redo it.  Sorry.
> 
> (some time later...)
> 
> Argh, at the last second I realized that you didn't mean this one:
> 
> 	"hwmon: fix Abit Uguru3 driver detection on some motherboards"
> 
> you actually meant this one:
> 
> 	PATCH: hwmon-abituguru-check-dmi-vendor.patch
> 
> Since I see that Jean acked it and it's trivial enough, I'll stuff it in there.
> Please let's not make a habit of this last-minute business.
> 

Apologies, next time I'll make any fixes an incremental patch.

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-07-19 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 20:30 [lm-sensors] patches vs. 2.6.22 for release - last chance Mark M. Hoffman
2007-07-18 21:28 ` Hans de Goede
2007-07-18 21:50 ` Juerg Haefliger
2007-07-19  5:50 ` Krzysztof Helt
2007-07-19 14:04 ` Hans de Goede
2007-07-19 18:26 ` Mark M. Hoffman
2007-07-19 18:27 ` Hans de Goede [this message]
2007-07-24 11:59 ` Mark M. Hoffman

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=469FAD2B.8070200@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=lm-sensors@vger.kernel.org \
    /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.