From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev@lists.infradead.org
Subject: Re: [PATCH 2/2] ssb: pci: update PCIe workarounds
Date: Wed, 27 Apr 2011 12:59:29 -0500 [thread overview]
Message-ID: <4DB85981.2090606@lwfinger.net> (raw)
In-Reply-To: <1303918788-4903-2-git-send-email-zajec5@gmail.com>
On 04/27/2011 10:39 AM, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki<zajec5@gmail.com>
> ---
> drivers/ssb/driver_pcicore.c | 35 +++++++++++++++++++++++++++--------
> 1 files changed, 27 insertions(+), 8 deletions(-)
ACK.
Larry
next prev parent reply other threads:[~2011-04-27 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:39 [PATCH 1/2] ssb: pci: separate workarounds Rafał Miłecki
2011-04-27 15:39 ` [PATCH 2/2] ssb: pci: update PCIe workarounds Rafał Miłecki
2011-04-27 17:59 ` Larry Finger [this message]
2011-04-27 18:00 ` [PATCH 1/2] ssb: pci: separate workarounds Larry Finger
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=4DB85981.2090606@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=zajec5@gmail.com \
/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).