From: "hch@infradead.org" <hch@infradead.org>
To: Anish Bhatt <anish@chelsio.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"jbottomley@parallels.com" <jbottomley@parallels.com>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
Karen Xie <kxie@chelsio.com>,
Manoj Malviya <manojmalviya@chelsio.com>
Subject: Re: [PATCH scsi] libcxgbi : support ipv6 address host_param
Date: Sat, 18 Oct 2014 08:12:03 -0700 [thread overview]
Message-ID: <20141018151203.GA30355@infradead.org> (raw)
In-Reply-To: <525DB349B3FB5444AE057A887CB2A8D8920F15@nice.asicdesigners.com>
On Fri, Oct 17, 2014 at 07:43:34PM +0000, Anish Bhatt wrote:
> I actually wanted to get some clarification on how the branches on scsi-queue
> work. The core/drivers separation is easy enough, but the current branches
> are confusing. If say I am submitting a bug fix for the next 3.17 release, what
> branch should I be basing my changes on ? Is there a preferred procedure for
> submitting bug fixes vs new features ?
Anything that is an urgent and/or very small fix should just be against
Linus' current tree and will go into the drivers branch for that tree.
Anything bigger and/or less urgent should be sent against the drivers
branch for the next release.
next prev parent reply other threads:[~2014-10-18 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 22:59 [PATCH scsi] libcxgbi : support ipv6 address host_param Anish Bhatt
2014-10-17 19:43 ` Anish Bhatt
2014-10-18 15:12 ` hch [this message]
2014-10-18 15:18 ` hch
2014-10-19 4:07 ` Anish Bhatt
2014-10-19 14:17 ` hch
2014-10-19 17:51 ` Anish Bhatt
2014-10-21 19:09 ` Mike Christie
2014-10-25 0:06 ` Anish Bhatt
2014-10-27 9:56 ` hch
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=20141018151203.GA30355@infradead.org \
--to=hch@infradead.org \
--cc=anish@chelsio.com \
--cc=jbottomley@parallels.com \
--cc=kxie@chelsio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=manojmalviya@chelsio.com \
--cc=michaelc@cs.wisc.edu \
/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