netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: fpavlic@de.ibm.com
Cc: netdev Mailinglist <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/9] s390: netiucv driver fixes
Date: Wed, 06 Sep 2006 11:13:56 -0400	[thread overview]
Message-ID: <44FEE5B4.9070003@pobox.com> (raw)
In-Reply-To: <200609061705.14737.fpavlic@de.ibm.com>

fpavlic@de.ibm.com wrote:
> [PATCH 2/9] s390: netiucv driver fixes
> 
> From: Frank Pavlic <fpavlic@de.ibm.com>
>  - missing lock initialization added
>         - avoid duplicate iucv-interfaces to the same peer
>         - rw-lock added for manipulating the list of
>           defined iucv connections
> 
> Signed-off-by: Frank Pavlic <fpavlic@de.ibm.com>
> ---
> 
>  drivers/s390/net/netiucv.c |   80 
> +++++++++++++++++++++++++++++++++++---------
>  1 files changed, 64 insertions(+), 16 deletions(-)
> 
> 05eebe4adf2ad6b442b3dc0bd34ccc5863299efb
> diff --git a/drivers/s390/net/netiucv.c b/drivers/s390/net/netiucv.c
> index 5d6e6cb..d7d1cc0 100644
> --- a/drivers/s390/net/netiucv.c
> +++ b/drivers/s390/net/netiucv.c
> @@ -112,7 +112,12 @@ struct iucv_connection {
>  /**
>   * Linked list of all connection structs.
>   */
> -static struct iucv_connection *iucv_connections;
> +struct iucv_connection_struct {
> + struct iucv_connection *iucv_connections;
> + rwlock_t iucv_rwlock;
> +};

Please submit a patch very soon that runs scripts/Lindent over all the 
s390 net drivers.  These drivers don't comply with 
Documentation/CodingStyle.

	Jeff




  reply	other threads:[~2006-09-06 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 15:05 [PATCH 2/9] s390: netiucv driver fixes fpavlic
2006-09-06 15:13 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-15 14:25 Frank Pavlic

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=44FEE5B4.9070003@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=fpavlic@de.ibm.com \
    --cc=netdev@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).