public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Cc: linux-kernel@vger•kernel.org, Rasesh Mody <rmody@brocade•com>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: linux-next: Tree for Dec 20 (brocade/bna)
Date: Fri, 20 Dec 2013 12:52:30 -0800	[thread overview]
Message-ID: <52B4AE0E.8070701@infradead.org> (raw)
In-Reply-To: <20131220172503.b2b7cb92f437d974f032e1a4@canb.auug.org.au>

On 12/19/13 22:25, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20131219:
> 


on i386:

drivers/net/ethernet/brocade/bna/bnad.c: In function 'bnad_start_xmit':
drivers/net/ethernet/brocade/bna/bnad.c:3074:26: error: 'struct bnad_tx_vector' has no member named 'dma_len'


CONFIG_NEED_DMA_MAP_STATE is not enabled.


-- 
~Randy

      parent reply	other threads:[~2013-12-20 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  6:25 linux-next: Tree for Dec 20 Stephen Rothwell
2013-12-20 18:58 ` [PATCH -next] gpu: fix qxl missing crc32_le Randy Dunlap
2013-12-20 20:52 ` Randy Dunlap [this message]

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=52B4AE0E.8070701@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rmody@brocade$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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