From: Larry Finger <Larry.Finger@lwfinger.net>
To: nick <xerofoify@gmail.com>, "Rafał Miłecki" <zajec5@gmail.com>,
"Michael Büsch" <m@bues.ch>
Cc: Network Development <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stefano Brivio <stefano.brivio@polimi.it>,
b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c
Date: Sat, 29 Nov 2014 12:54:17 -0600 [thread overview]
Message-ID: <547A1659.9070605@lwfinger.net> (raw)
In-Reply-To: <547A0BC5.2080005@gmail.com>
On 11/29/2014 12:09 PM, nick wrote:
> Sorry about that, next time I will be more careful.
One other thing would be to change the initial part of the subject. Yes, the
device is in drivers/net/wireless/, but it is much more common to not include
those in patches that are sent to Linville. I would have used "b43: Add ...".
That catches the eye more quickly. As they say in the newspaper business, "Don't
bury the lead."
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: nick <xerofoify@gmail.com>, "Rafał Miłecki" <zajec5@gmail.com>,
"Michael Büsch" <m@bues.ch>
Cc: Network Development <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stefano Brivio <stefano.brivio@polimi.it>,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c
Date: Sat, 29 Nov 2014 12:54:17 -0600 [thread overview]
Message-ID: <547A1659.9070605@lwfinger.net> (raw)
In-Reply-To: <547A0BC5.2080005@gmail.com>
On 11/29/2014 12:09 PM, nick wrote:
> Sorry about that, next time I will be more careful.
One other thing would be to change the initial part of the subject. Yes, the
device is in drivers/net/wireless/, but it is much more common to not include
those in patches that are sent to Linville. I would have used "b43: Add ...".
That catches the eye more quickly. As they say in the newspaper business, "Don't
bury the lead."
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: nick <xerofoify-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Michael Büsch" <m@bues.ch>
Cc: Network Development
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Stefano Brivio
<stefano.brivio-hl5o88x/ua9eoWH0uzbU5w@public.gmane.org>,
b43-dev
<b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c
Date: Sat, 29 Nov 2014 12:54:17 -0600 [thread overview]
Message-ID: <547A1659.9070605@lwfinger.net> (raw)
In-Reply-To: <547A0BC5.2080005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 11/29/2014 12:09 PM, nick wrote:
> Sorry about that, next time I will be more careful.
One other thing would be to change the initial part of the subject. Yes, the
device is in drivers/net/wireless/, but it is much more common to not include
those in patches that are sent to Linville. I would have used "b43: Add ...".
That catches the eye more quickly. As they say in the newspaper business, "Don't
bury the lead."
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-29 18:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 22:16 [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c Nicholas Krause
2014-11-28 22:16 ` Nicholas Krause
2014-11-28 22:40 ` Rafał Miłecki
2014-11-28 22:40 ` Rafał Miłecki
2014-11-28 23:21 ` Michael Büsch
2014-11-28 23:21 ` Michael Büsch
2014-11-29 3:32 ` nick
2014-11-29 3:32 ` nick
2014-11-29 8:54 ` Rafał Miłecki
2014-11-29 8:54 ` Rafał Miłecki
2014-11-29 8:56 ` Michael Büsch
2014-11-29 8:56 ` Michael Büsch
2014-11-29 9:04 ` Rafał Miłecki
2014-11-29 9:04 ` Rafał Miłecki
2014-11-29 18:09 ` nick
2014-11-29 18:09 ` nick
2014-11-29 18:54 ` Larry Finger [this message]
2014-11-29 18:54 ` Larry Finger
2014-11-29 18:54 ` 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=547A1659.9070605@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
--cc=xerofoify@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.