From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: Fengguang Wu <wfg@linux.intel.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-scsi@vger.kernel.org, linux-raid@vger.kernel.org,
virtualization@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: drivers/block/cpqarray.c:938:2: error: too many arguments to function lk_rq_map_sg
Date: Thu, 14 Jun 2012 11:52:38 +0000 [thread overview]
Message-ID: <1339674758-ner-4999@calvin> (raw)
In-Reply-To: <20120614113142.GA13954@localhost>
On Thu, 14 Jun 2012 19:31:42 +0800, Fengguang Wu <wfg@linux.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
next prev parent reply other threads:[~2012-06-14 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 23:03 drivers/block/cpqarray.c:938:2: error: too many arguments to function ‘blk_rq_map_sg’ wfg
2012-06-13 23:03 ` wfg
2012-06-14 6:30 ` Jens Axboe
2012-06-14 6:30 ` Jens Axboe
2012-06-14 9:01 ` drivers/block/cpqarray.c:938:2: error: too many arguments to function 慴lk_rq_map_sg� Fengguang Wu
2012-06-14 9:05 ` Jens Axboe
2012-06-14 9:05 ` Jens Axboe
2012-06-14 9:25 ` Fengguang Wu
2012-06-14 17:26 ` Junio C Hamano
2012-06-14 17:26 ` Junio C Hamano
2012-06-14 17:26 ` Junio C Hamano
2012-06-14 9:25 ` Fengguang Wu
2012-06-14 10:02 ` drivers/block/cpqarray.c:938:2: error: too many arguments to function lk_rq_map_sg Fengguang Wu
2012-06-14 10:02 ` Fengguang Wu
2012-06-14 10:45 ` Jens Axboe
2012-06-14 10:45 ` Jens Axboe
2012-06-14 11:31 ` Fengguang Wu
2012-06-14 11:31 ` Fengguang Wu
2012-06-14 11:52 ` Tomas Carnecky [this message]
2012-06-14 11:52 ` Tomas Carnecky
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=1339674758-ner-4999@calvin \
--to=tomas.carnecky@gmail.com \
--cc=axboe@kernel.dk \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wfg@linux.intel.com \
/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.