From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
linux-iio@vger.kernel.org,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg KH <gregkh@suse.de>
Subject: Re: linux-next: Tree for Oct 11 (iio/resolver)
Date: Tue, 11 Oct 2011 13:45:14 -0700 [thread overview]
Message-ID: <4E94AADA.4080204@xenotime.net> (raw)
In-Reply-To: <20111011201127.455df266dcbffb1d621f8576@canb.auug.org.au>
On 10/11/11 02:11, Stephen Rothwell wrote:
> Hi all,
>
> The linux-next tree is now available from
> git://github.com/sfrothwell/linux-next.git as a temporary measure while
> the kernel.org servers are unavailable.
>
> It may also turn up on git.kernel.org (depending on the mirroring). The
> patch set is still absent, however.
>
> Changes since 20111007:
When no GPIO support is enabled:
drivers/staging/iio/resolver/ad2s1210.c:657:14: error: array type has incomplete element type
drivers/staging/iio/resolver/ad2s1210.c:665:44: warning: type defaults to 'int' in type name
drivers/staging/iio/resolver/ad2s1210.c:665:44: warning: type defaults to 'int' in type name
drivers/staging/iio/resolver/ad2s1210.c:665:44: error: negative width in bit-field '<anonymous>'
drivers/staging/iio/resolver/ad2s1210.c:671:14: error: array type has incomplete element type
drivers/staging/iio/resolver/ad2s1210.c:679:34: warning: type defaults to 'int' in type name
drivers/staging/iio/resolver/ad2s1210.c:679:34: warning: type defaults to 'int' in type name
drivers/staging/iio/resolver/ad2s1210.c:679:34: error: negative width in bit-field '<anonymous>'
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next parent reply other threads:[~2011-10-11 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111011201127.455df266dcbffb1d621f8576@canb.auug.org.au>
2011-10-11 20:45 ` Randy Dunlap [this message]
2011-10-12 8:58 ` linux-next: Tree for Oct 11 (iio/resolver) Jonathan Cameron
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=4E94AADA.4080204@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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).