All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephan Mueller <smueller@chronox.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 26 (drbg)
Date: Wed, 27 Aug 2014 09:36:40 -0700	[thread overview]
Message-ID: <53FE0918.3000004@infradead.org> (raw)
In-Reply-To: <53FCF700.7020107@infradead.org>

On 08/26/14 14:07, Randy Dunlap wrote:
> On 08/26/14 13:19, Stephan Mueller wrote:
>> Am Dienstag, 26. August 2014, 12:03:31 schrieb Randy Dunlap:
>>
>> Hi Randy,
>>
>>> On 08/26/14 00:34, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20140825:
>>>>
>>>> The net tree gained a build failure for which I reverted a commit.
>>>>
>>>> The mfd tree still had its build failure so I used the version from
>>>> next-20140822.
>>>
>>> on i386:
>>>
>>> ../include/crypto/drbg.h:157:2: warning: left shift count >= width of type
>>> [enabled by default] ../include/crypto/drbg.h:163:2: warning: left shift
>>> count >= width of type [enabled by default]
>>>
>>> I guess that someone has already seen this but I haven't noticed any reports
>>> of it.
>>
>> Thank you for reporting the issue. The patch and fix is provided with [1]. Did 
>> you test with this patch?
>>
>> [1] 
>> https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=b9347aff91ce4789619168539f08202d8d6a1177
>>
> 
> I tested whatever is in linux-next of 20140826.
> 
> I'll check that commit later, got to run errands now.

Yes, that works.  Thanks.

-- 
~Randy

      reply	other threads:[~2014-08-27 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  7:34 linux-next: Tree for Aug 26 Stephen Rothwell
2014-08-26 19:03 ` linux-next: Tree for Aug 26 (drbg) Randy Dunlap
2014-08-26 20:19   ` Stephan Mueller
2014-08-26 21:07     ` Randy Dunlap
2014-08-27 16:36       ` 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=53FE0918.3000004@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=smueller@chronox.de \
    /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.