public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [battery:master 23/24] drivers/mfd/88pm860x-core.c:803:39: warning: assignment from incompatible
Date: Fri, 21 Sep 2012 00:02:49 +0000	[thread overview]
Message-ID: <20120921000249.GA14399@lizard> (raw)
In-Reply-To: <20120920225658.GA12235@localhost>

On Fri, Sep 21, 2012 at 07:29:42AM +0800, Fengguang Wu wrote:
[...]
> Yes. Because I'm building every commit,

Oh, I see.

> > I think you're building with HEAD = a830d28b48bf9294, but why?
> > (And 23/24 makes me think that you're indeed missing the latest
> > commit.)
> 
> This report is for [23/24] a830d28b. The head ([24/24] f1ade35253f50)
> fixes the warning. Oh well, some warnings may not hurt bisectability
> while others do lead to runtime errors, so I can hardly avoid false
> reports on such fixed-in-HEAD warnings..
> 
> But if your tree never rebases, I can definitely avoid sending reports
> for such intermediate errors/warnings.

It's fine -- these reports are useful even if I don't rebase, now I
just know that interim warnings are also reported.

And sometimes I do rebase, if there's some major bisectabilty problem
(which I surely don't want to appear in upstream).

Thanks,
Anton.

      parent reply	other threads:[~2012-09-21  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 22:56 [battery:master 23/24] drivers/mfd/88pm860x-core.c:803:39: warning: assignment from incompatible poi Fengguang Wu
2012-09-20 23:13 ` [battery:master 23/24] drivers/mfd/88pm860x-core.c:803:39: warning: assignment from incompatible Anton Vorontsov
2012-09-20 23:29 ` Fengguang Wu
2012-09-21  0:02 ` Anton Vorontsov [this message]

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=20120921000249.GA14399@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=kernel-janitors@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