public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbou@mail.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-discuss@handhelds.org,
	David Woodhouse <dwmw2@infradead.org>, Greg KH <gregkh@suse.de>
Subject: Re: [ANNOUNCE] battery2 git repository
Date: Sat, 28 Apr 2007 16:31:29 +0400	[thread overview]
Message-ID: <20070428123129.GA2056@zarina> (raw)
In-Reply-To: <20070428045148.9f1ba191.akpm@linux-foundation.org>

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@mail.ru> 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@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.org/bd2

  reply	other threads:[~2007-04-28 12:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 23:29 [ANNOUNCE] battery2 git repository Anton Vorontsov
2007-04-27  0:09 ` Greg KH
2007-04-27  2:05   ` Anton Vorontsov
2007-04-27  6:03   ` David Woodhouse
2007-04-27 23:55     ` Greg KH
2007-04-28 17:23       ` Anton Vorontsov
2007-04-29 19:46       ` Anton Vorontsov
2007-04-27 23:46 ` Andrew Morton
2007-04-27 23:55   ` Greg KH
2007-04-28 11:51 ` Andrew Morton
2007-04-28 12:31   ` Anton Vorontsov [this message]
2007-04-28 15:57     ` Anton Vorontsov
2007-04-28 19:08     ` Andrew Morton
2007-04-29  1:01       ` Anton Vorontsov

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=20070428123129.GA2056@zarina \
    --to=cbou@mail.ru \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox