From: "Bhanu Prakash Gollapudi" <bprakash@broadcom.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "David Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vladislav Zolotarov" <vladz@broadcom.com>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
mchan@broadcom.com
Subject: Re: linux-next: manual merge of the net tree with the scsi tree
Date: Wed, 29 Jun 2011 21:20:40 -0700 [thread overview]
Message-ID: <4E0BF998.7030800@broadcom.com> (raw)
In-Reply-To: <20110630123325.43268067.sfr@canb.auug.org.au>
On 6/29/2011 7:33 PM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net tree got conflicts in
> drivers/scsi/bnx2fc/bnx2fc.h and drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> between commit 2382d2364a60 ("[SCSI] bnx2fc: Bumped version to 1.0.2")
> from the scsi tree and commit 619c5cb6885b ("New 7.0 FW: bnx2x, cnic,
> bnx2i, bnx2fc") from the net tree.
>
> I used the versions from the net tree as those version numbers were newer.
>
Stephen, can you please send the conflicts? Most probably you should
have seen the conflicts w.r.t version number in bnx2fc.h and date in
bnx2fc_fcoe.c. If that is the case, the versions from net tree are good.
Thanks,
Bhanu
next prev parent reply other threads:[~2011-06-30 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 2:33 linux-next: manual merge of the net tree with the scsi tree Stephen Rothwell
2011-06-30 4:20 ` Bhanu Prakash Gollapudi [this message]
2011-06-30 4:41 ` Stephen Rothwell
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=4E0BF998.7030800@broadcom.com \
--to=bprakash@broadcom.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vladz@broadcom.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