[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1339674758-ner-4999@calvin>
Date: Thu, 14 Jun 2012 11:52:38 +0000
From: Tomas Carnecky <tomas.carnecky@...il.com>
To: Fengguang Wu <wfg@...ux.intel.com>, Jens Axboe <axboe@...nel.dk>
Cc: linux-scsi@...r.kernel.org, linux-raid@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
"git@...r.kernel.org" <git@...r.kernel.org>
Subject: Re: drivers/block/cpqarray.c:938:2: error: too many arguments to
function lk_rq_map_sg
On Thu, 14 Jun 2012 19:31:42 +0800, Fengguang Wu <wfg@...ux.intel.com> wrote:
> On Thu, Jun 14, 2012 at 12:45:38PM +0200, Jens Axboe wrote:
> > On 06/14/2012 12:02 PM, Fengguang Wu wrote:
> > > OK, I'll add a grep for "Dont-Auto-Build". If it's found in *any*
> > > commit of the branch, the build script will skip the whole branch.
> > > Does this make sense to you?
> >
> > Yeah that'll work for me. A description or tag might be more elegant,
> > but this is easier...
>
> Great, let's settle with the in-commit tag "Dont-Auto-Build" for now :)
>
> "git branch --edit-description" could potentially be the most elegant
> solution, unfortunately for now there seems no way for me to retrieve
> the branch description edited by you..
>
> Another alternative, git tag, has the problem that it goes out of sync
> every time you do rebase, which will sure happen a lot for early RFC
> patches.
Commit notes or a special namespace for branches (refs/heads/wip/...) would
also be an option.
tom
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists