linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-wireless@vger.kernel.org,
	Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
	Aloisio Almeida Jr <aloisio.almeida@openbossa.org>
Subject: Re: [PATCH -next] nfc: shdlc needs to select CRC_CCITT
Date: Mon, 14 May 2012 22:32:44 +0200	[thread overview]
Message-ID: <20120514203244.GD12740@sortiz-mobl> (raw)
In-Reply-To: <4FB16765.3090602@xenotime.net>

Hi Randy,

On Mon, May 14, 2012 at 01:13:25PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Fix build error: SHDLC uses crc_ccitt so it should select CRC_CCITT.
> 
> ERROR: "crc_ccitt" [net/nfc/hci/hci.ko] undefined!
A similar patch was sent a few days ago by Marcel Holtmann.
It is queued to my nfc-fixes branch and I included it to a pull request I sent
to John last week.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2012-05-14 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 10:03 linux-next: Tree for May 14 Stephen Rothwell
     [not found] ` <20120514200357.e7448e4ca061c8efe3d4757d-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-05-14 20:13   ` [PATCH -next] nfc: shdlc needs to select CRC_CCITT Randy Dunlap
2012-05-14 20:32     ` Samuel Ortiz [this message]
2012-05-14 20:14 ` [PATCH -next] wdt: ie6xx_wdt needs io.h Randy Dunlap
2012-05-17  7:11   ` Wim Van Sebroeck
2012-05-14 20:15 ` [PATCH -next] wdt: fix iTCO printk format warnings Randy Dunlap
2012-05-17  7:14   ` Wim Van Sebroeck

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=20120514203244.GD12740@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=aloisio.almeida@openbossa.org \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).