From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
James Smart <james.smart@emulex.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: Tree for May 6 (lpfc)
Date: Mon, 06 May 2013 09:14:41 -0700 [thread overview]
Message-ID: <5187D6F1.9070103@infradead.org> (raw)
In-Reply-To: <20130506144207.c812a0227d7763d26e5fec80@canb.auug.org.au>
On 05/05/13 21:42, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees. Please clean this up
> and resist the temptataion to rebase your trees on the way to your
> upstream ...
>
> Changes since 20130506:
>
on i386:
# CONFIG_CRC_T10DIF is not set
drivers/built-in.o: In function `lpfc_bg_crc':
(.text+0x3cb3c9): undefined reference to `crc_t10dif'
--
~Randy
next prev parent reply other threads:[~2013-05-06 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 4:42 linux-next: Tree for May 6 Stephen Rothwell
2013-05-06 4:42 ` Stephen Rothwell
2013-05-06 16:14 ` Randy Dunlap [this message]
2013-05-06 16:49 ` linux-next: Tree for May 6 (lpfc) James Bottomley
2013-05-06 17:36 ` Martin K. Petersen
2013-05-06 17:48 ` Randy Dunlap
2013-05-06 17:42 ` linux-next: Tree for May 6 (b43/bcma) Randy Dunlap
2013-05-06 17:42 ` Randy Dunlap
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 3:06 ` Larry Finger
2013-05-07 9:15 ` Johannes Berg
2013-05-07 9:15 ` Johannes Berg
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=5187D6F1.9070103@infradead.org \
--to=rdunlap@infradead.org \
--cc=james.smart@emulex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.