From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Robert Love <robert.w.love@intel.com>
Cc: Hillf Danton <dhillf@gmail.com>,
Mike Christie <michaelc@cs.wisc.edu>,
devel@open-fcoe.org, linux-scsi@vger.kernel.org
Subject: Re: [Open-FCoE] [PATCH] add cpu on/offline support in Fibre Channel exchange and sequence handling
Date: Mon, 11 Oct 2010 15:49:46 -0700 [thread overview]
Message-ID: <1286837386.20358.106.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1286834888.13422.1572.camel@fritz>
On Mon, 2010-10-11 at 15:08 -0700, Robert Love wrote:
> On Fri, 2010-10-08 at 22:57 +0800, Hillf Danton wrote:
>
> Hi Hillf,
>
> Can you please prefix the libfc patches with "libfc: <title>"? Also, for
> your other patches that have a "SCSI" prefix, I think James' system adds
> the "[SCSI]" prefix when he applies patches so you don't need to add it.
>
> > Fibre Channel exchange pool is setup in a per cpu way that
> > entire exchange id range is divided equally across all cpus.
> >
> > When cpu goes offline, the corresponding range of exchg id
> > becomes unavailable until it is online again.
> >
> > This work tries to fix the unavailability based on notifier_block.
> >
> > Signed-off-by: Hillf Danton <dhillf@gmail.com>
> > ---
> >
> > --- o/linux-2.6.36-rc4/drivers/scsi/libfc/fc_exch.c 2010-09-13
> > 07:07:38.000000000 +0800
> > +++ m/linux-2.6.36-rc4/drivers/scsi/libfc/fc_exch.c 2010-10-08
> > 22:24:48.000000000 +0800
>
> Most patches I've seen on the various mailing lists are created by
> diffing the files within the kernel directory, so that you don't have
> the "/linux-2.6.36-rc/" in each hunk. It's the difference between using
> 'patch -p1' or 'patch -p2' when applying the patch.
>
> I think this is preventing git-am from applying the patches. To import
> them I ended up having git-am fail and then manually using the 'patch
> -p2' command, so that I could get both the commit message from git-am
> and then the patch itself from 'patch'. I don't know about anyone else,
> but if you post patches without the kernel directory in the diff line it
> would help me out. Thanks.
>
Hmmm, I am not sure about how to do this with git-am, but when I do this
between lio-core-2.6.git/lio-4.0 -> lio-core-backports.git patches, I
use:
'git-apply --index --verbose --directory=$DIR_PREFIX'
which is described in the git-apply manual here:
--directory=<root>
Prepend <root> to all filenames. If a "-p" argument was also
passed, it is applied before prepending the new root.
For example, a patch that talks about updating a/git-gui.sh to
b/git-gui.sh can be applied to the file in the working tree
modules/git-gui/git-gui.sh by running git apply
--directory=modules/git-gui.
Best,
--nab
next prev parent reply other threads:[~2010-10-11 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 14:57 [PATCH] add cpu on/offline support in Fibre Channel exchange and sequence handling Hillf Danton
2010-10-11 22:03 ` Zou, Yi
2010-10-11 22:08 ` [Open-FCoE] " Robert Love
2010-10-11 22:49 ` Nicholas A. Bellinger [this message]
2010-10-11 23:23 ` Robert Love
2010-10-14 14:55 ` Hillf Danton
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=1286837386.20358.106.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=devel@open-fcoe.org \
--cc=dhillf@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=robert.w.love@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox