From: Andi Kleen <andi@firstfloor.org>
To: Naresh Kumar Inna <naresh@chelsio.com>
Cc: David Miller <davem@davemloft.net>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Dimitrios Michailidis <dm@chelsio.com>,
Casey Leedom <leedom@chelsio.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Chethan Seshadri <chethan@chelsio.com>
Subject: Re: [V3 PATCH 9/9] cxgb4vf: Chelsio FCoE offload driver submission (header compatibility fixes).
Date: Wed, 12 Sep 2012 09:52:23 -0700 [thread overview]
Message-ID: <m2har3yyig.fsf@firstfloor.org> (raw)
In-Reply-To: <50502B3A.6080803@chelsio.com> (Naresh Kumar Inna's message of "Wed, 12 Sep 2012 11:57:06 +0530")
Naresh Kumar Inna <naresh@chelsio.com> writes:
>
> OK, I think I should be able to arrange the patch set to fulfill that
> requirement. I was under the impression it was fine for new drivers to
> split patches in this fashion, since they go as a single commit, sorry
> about that.
What they normally do then is to add the Kconfig or Makefile entry
only in the end, so it cannot build before.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Naresh Kumar Inna <naresh@chelsio.com>
Cc: David Miller <davem@davemloft.net>,
"JBottomley\@parallels.com" <JBottomley@parallels.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Dimitrios Michailidis <dm@chelsio.com>,
Casey Leedom <leedom@chelsio.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
Chethan Seshadri <chethan@chelsio.com>
Subject: Re: [V3 PATCH 9/9] cxgb4vf: Chelsio FCoE offload driver submission (header compatibility fixes).
Date: Wed, 12 Sep 2012 09:52:23 -0700 [thread overview]
Message-ID: <m2har3yyig.fsf@firstfloor.org> (raw)
In-Reply-To: <50502B3A.6080803@chelsio.com> (Naresh Kumar Inna's message of "Wed, 12 Sep 2012 11:57:06 +0530")
Naresh Kumar Inna <naresh@chelsio.com> writes:
>
> OK, I think I should be able to arrange the patch set to fulfill that
> requirement. I was under the impression it was fine for new drivers to
> split patches in this fashion, since they go as a single commit, sorry
> about that.
What they normally do then is to add the Kconfig or Makefile entry
only in the end, so it cannot build before.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-09-12 16:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 14:38 [V3 PATCH 0/9] csiostor: Chelsio FCoE offload driver submission Naresh Kumar Inna
2012-09-11 14:38 ` [V3 PATCH 1/9] csiostor: Chelsio FCoE offload driver submission (sources part 1) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 2/9] csiostor: Chelsio FCoE offload driver submission (sources part 2) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 3/9] csiostor: Chelsio FCoE offload driver submission (sources part 3) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 4/9] csiostor: Chelsio FCoE offload driver submission (sources part 4) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 5/9] csiostor: Chelsio FCoE offload driver submission (sources part 5) Naresh Kumar Inna
2012-09-11 17:35 ` David Miller
2012-09-12 5:40 ` Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 6/9] csiostor: Chelsio FCoE offload driver submission (headers part 1) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 7/9] csiostor: Chelsio FCoE offload driver submission (headers part 2) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 8/9] cxgb4: Chelsio FCoE offload driver submission (cxgb4 common header updates) Naresh Kumar Inna
2012-09-11 14:39 ` [V3 PATCH 9/9] cxgb4vf: Chelsio FCoE offload driver submission (header compatibility fixes) Naresh Kumar Inna
2012-09-11 17:33 ` David Miller
2012-09-12 5:35 ` Naresh Kumar Inna
2012-09-12 5:47 ` David Miller
2012-09-12 6:27 ` Naresh Kumar Inna
2012-09-12 16:52 ` Andi Kleen [this message]
2012-09-12 16:52 ` Andi Kleen
2012-09-12 17:20 ` Naresh Kumar Inna
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=m2har3yyig.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=JBottomley@parallels.com \
--cc=chethan@chelsio.com \
--cc=davem@davemloft.net \
--cc=dm@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=naresh@chelsio.com \
--cc=netdev@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.