grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: rijndael.c warning (was Re: grub-2.02~beta1 happened)
Date: Tue, 24 Dec 2013 16:58:24 +0100	[thread overview]
Message-ID: <52B9AF20.8050805@gmail.com> (raw)
In-Reply-To: <CAJ0EP40T0GzM-GCzZ6ZHDOAuAi10vtty+2cP-Yhypd6C62Zbkg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

On 23.12.2013 23:25, Mike Gilbert wrote:
> On Thu, Dec 19, 2013 at 7:39 AM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> On 19.12.2013 06:43, Bruce Dubbs wrote:
>>> Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>>> Hello, all. I've just uploaded 2.02~beta1. This also means that we're
>>>> now in freeze. I'm willing to consider exceptions on case-by-case basis
>>>> but it would be exceptions. The major points to do before release:
>>>> - ARM64 loader.
>>>> - Yeeloong 3A support needs some love.
>>>> - XEN would probably need config adjustments.
>>>> - XNU loader needs fixes.
>>>> - NEWS needs contents.
>>>> - Documentation.
>>>> - Loads and loads of testing and some bugfixes.
>>>
>>> There are a few warnings for rijndael.c with gcc 4.8.2.  A couple of
>>> them are pretty trivial.  Others probably should be turned off with
>>> -Wno-strict-aliasing.  Do you want a patch?
>>>
>> This file is managed by libgcrypt. Could you take issue with them? I'm
>> fine with backporting patches from libgcrypt but it's better not to have
>> own patches for libgcrypt (Debian fiasco, remember?)
> 
> This has already been fixed upstream, and the change applies to grub's
> copy of libgcrypt without any issues.
> 
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=dfb4673da8ee52d95e0a62c9f49ca8599943f22e
> 
Done, thanks.
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-12-24 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  1:51 grub-2.02~beta1 happened Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19  5:43 ` Bruce Dubbs
2013-12-19 12:39   ` rijndael.c warning (was Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-23 22:25     ` Mike Gilbert
2013-12-24 15:58       ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-19  6:38 ` grub-2.02~beta1 happened Andrey Borzenkov
2013-12-19  9:53   ` ext4 inline data (Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 16:05     ` Andrey Borzenkov
2013-12-19 18:23       ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 19:59 ` Important EHCI bugfix " Aleš Nesrsta
2013-12-20 12:16   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-20 17:57     ` Aleš Nesrsta

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=52B9AF20.8050805@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /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).