From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: net: Fixup the armada100 FEC driver
Date: Mon, 30 Jul 2012 17:35:00 +0200 [thread overview]
Message-ID: <201207301735.01010.marex@denx.de> (raw)
In-Reply-To: <CANr=Z=a8TQvt8XKdrafSN6sK1m_sVFswrqWGc67Wvm-h2sbsTw@mail.gmail.com>
Dear Joe Hershberger,
> Hi Marek,
>
> On Mon, Jul 30, 2012 at 1:35 AM, Marek Vasut <marex@denx.de> wrote:
> > Dear Prafulla Wadaskar,
> >
> >> > -----Original Message-----
> >> > From: u-boot-bounces at lists.denx.de [mailto:u-boot-
> >> > bounces at lists.denx.de] On Behalf Of Marek Vasut
> >> > Sent: 28 July 2012 01:20
> >> > To: u-boot at lists.denx.de
> >> > Cc: Marek Vasut; Joe Hershberger; u-boot-dm at lists.denx.de
> >> > Subject: [U-Boot] [PATCH] dm: net: Fixup the armada100 FEC driver
> >> >
> >> > Apply the following questionable adjustment to silence GCC.
> >> >
> >> > armada100_fec.c: In function 'armdfec_send':
> >> > armada100_fec.c:589:2: warning: dereferencing type-punned pointer will
> >> > break strict-aliasing rules [-Wstrict-aliasing]
> >> >
> >> > Signed-off-by: Marek Vasut <marex@denx.de>
> >> > Cc: Joe Hershberger <joe.hershberger@ni.com>
> >
> > [...]
> >
> > Joe, can you please pick this for -next (or -master already?) ?
>
> OK... I figured this was just an RFC, since it was sent to the u-boot-dm
> list.
That was a bad choice to cross post it to both MLs ... and I was already told
so, quite a lot.
> I'll pull it into master after release.
>
> Thanks,
> -Joe
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-30 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 19:50 [U-Boot] [PATCH] dm: net: Fixup the armada100 FEC driver Marek Vasut
2012-07-30 6:32 ` Prafulla Wadaskar
2012-07-30 6:35 ` Marek Vasut
2012-07-30 15:24 ` Joe Hershberger
2012-07-30 15:35 ` Marek Vasut [this message]
2012-09-03 9:09 ` Prafulla Wadaskar
2012-09-06 1:50 ` Joe Hershberger
2012-09-28 15:53 ` [U-Boot] [U-Boot-DM] " Joe Hershberger
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=201207301735.01010.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox