From: David Miller <davem@davemloft.net>
To: nicolas.ferre@atmel.com
Cc: neidhard.kim@lge.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] net/cadence/macb: fix bug/typo in extracting gem_irq_read_clear bit
Date: Tue, 09 Jul 2013 12:50:40 -0700 (PDT) [thread overview]
Message-ID: <20130709.125040.1834646995344159799.davem@davemloft.net> (raw)
In-Reply-To: <51DC340F.2060402@atmel.com>
From: Nicolas Ferre <nicolas.ferre@atmel.com>
Date: Tue, 9 Jul 2013 18:02:23 +0200
> On 09/07/2013 10:36, Jongsung Kim :
>> Signed-off-by: Jongsung Kim <neidhard.kim@lge.com>
>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> Cc: stable <stable@vger.kernel.org> # 3.10+
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2013-07-09 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:36 [PATCH] net/cadence/macb: fix bug/typo in extracting gem_irq_read_clear bit Jongsung Kim
2013-07-09 16:02 ` Nicolas Ferre
2013-07-09 19:50 ` David Miller [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=20130709.125040.1834646995344159799.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neidhard.kim@lge.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=stable@vger.kernel.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).