Re: [ANNOUNCE] battery2 git repository

From: Anton Vorontsov
Date: Sat Apr 28 2007 - 08:33:40 EST


On Sat, Apr 28, 2007 at 04:51:48AM -0700, Andrew Morton wrote:
> On Fri, 27 Apr 2007 03:29:02 +0400 Anton Vorontsov <cbou@xxxxxxx> wrote:
>
> > To not confuse with David own battery-2.6 repository, it's called
> > battery2-2.6, and can be found here:
> >
> > http://git.infradead.org/?p=users/cbou/battery2-2.6.git;a=summary
> >
> > You can get it using "git clone --reference linux-2.6 \
> > git://git.infradead.org/users/cbou/battery2-2.6.git" command.
>
> i386 `make allmodconfig':
>
> ERROR: "battery_is_external_power_supplied" [drivers/battery/ds2760_battery.ko] undefined!
> ERROR: "battery_unregister" [drivers/battery/ds2760_battery.ko] undefined!
> ERROR: "battery_register" [drivers/battery/ds2760_battery.ko] undefined!
> ERROR: "battery_status_changed" [drivers/battery/ds2760_battery.ko] undefined!

:-/

It should be fixed 37 hours ago by

http://git.infradead.org/?p=users/cbou/battery2-2.6.git;a=commit;h=cbb1e1b9e3a2cbf62ce4c13ef95d146ebc5e7274

Should I ask git-pull when such fixes happens? And I wonder why it isn't
already in -mm, because you've added this git repository after that
commit...

Though, I'm doing "allmodconfig" once again, to be sure, it will take
some time. (I've done defconfig, with modular W1, BATTERY,
DS2760_BATTERY already, and error doesn't show up).

---

Also, much thanks for accepting it to the -mm.

I have one question though... battery2-2.6 have two branches,
"linus" (clean Linus' tree) and "master" (with battery stuff).

When I'll want to sync battery tree with Linus' once again,
should I just pull from linus, or it's better to rebase master against
linus, and then "git push -f" to the battery2-2.6 master branch?
Or it will break something on your side (as commits will change their
hash)?

Thanks,

--
Anton Vorontsov
email: cbou@xxxxxxx
backup email: ya-cbou@xxxxxxxxx
irc://irc.freenode.org/bd2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/