From: Stanislaw Gruszka <sgruszka@redhat.com>
To: nick <yocto6@gmail.com>
Cc: IvDoorn@gmail.com, helmut.schaa@googlemail.com,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
users@rt2x00.serialmonkey.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: FIXMEs in rt2800lib.c
Date: Fri, 26 Sep 2014 14:22:08 +0200 [thread overview]
Message-ID: <20140926122207.GA27809@redhat.com> (raw)
In-Reply-To: <5424566B.6000206@gmail.com>
On Thu, Sep 25, 2014 at 01:52:43PM -0400, nick wrote:
> I seem to be hitting to fix mes in the file I listed in the subject. Would someone tell me if it's Ok to remove
> the lines that over write certain registers.
No, as long you prove that they are not needed.
Stanislaw
next prev parent reply other threads:[~2014-09-26 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 17:52 FIXMEs in rt2800lib.c nick
2014-09-26 12:22 ` Stanislaw Gruszka [this message]
[not found] ` <20140926122207.GA27809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-26 13:32 ` Nicholas Krause
2014-09-26 17:02 ` nick
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=20140926122207.GA27809@redhat.com \
--to=sgruszka@redhat.com \
--cc=IvDoorn@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
--cc=yocto6@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).