All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [staging:staging-next 70/73] drivers/staging/comedi/drivers/amplc_dio200.c:1444:2: error: implic
Date: Wed, 15 Aug 2012 14:07:36 +0000	[thread overview]
Message-ID: <20120815140736.GA32426@localhost> (raw)
In-Reply-To: <502B71C7.4010005@mev.co.uk>

> > Well it looks like my patches got applied in the wrong order (1, 3,
> > 2) on Greg's staging-next branch, but as long as all 3 patches are
> > applied it ought to compile okay.
> 
> Argh, I did?  Sorry about that.  Nothing I can do about it now :(

No problem. That reminds me to mark the staging-next branch as
non-rebaseable (which means the test system will silently ignore
intermediate errors in that branch).

Perhaps usb-next is non-rebaseable as well. Are there any more that
should be marked as non-rebaseable?

Thanks,
Fengguang

  parent reply	other threads:[~2012-08-15 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  9:54 [staging:staging-next 70/73] drivers/staging/comedi/drivers/amplc_dio200.c:1444:2: error: implic Ian Abbott
2012-08-15 13:54 ` Greg Kroah-Hartman
2012-08-15 14:07 ` Fengguang Wu [this message]
2012-08-15 14:10 ` Greg Kroah-Hartman
2012-08-15 14:35 ` Fengguang Wu
2012-08-15 14:47 ` Greg Kroah-Hartman
2012-08-15 14:50 ` Fengguang Wu

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=20120815140736.GA32426@localhost \
    --to=fengguang.wu@intel.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 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.