netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cornelia.huck@de.ibm.com
Cc: shemminger@vyatta.com, greg@kroah.com, fubar@us.ibm.com,
	netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] sysfs: remove error messages for -EEXIST case
Date: Thu, 15 May 2008 01:01:39 -0700 (PDT)	[thread overview]
Message-ID: <20080515.010139.219194657.davem@davemloft.net> (raw)
In-Reply-To: <20080515095246.3b6a0d1d@gondolin.boeblingen.de.ibm.com>

From: Cornelia Huck <cornelia.huck@de.ibm.com>
Date: Thu, 15 May 2008 09:52:46 +0200

> >  int sysfs_add_one(struct sysfs_addrm_cxt *acxt, struct sysfs_dirent *sd)
> >  {
> > -	if (sysfs_find_dirent(acxt->parent_sd, sd->s_name)) {
> > -		printk(KERN_WARNING "sysfs: duplicate filename '%s' "
> > -		       "can not be created\n", sd->s_name);
> > -		WARN_ON(1);
> > +	if (sysfs_find_dirent(acxt->parent_sd, sd->s_name))
> >  		return -EEXIST;
> > -	}
> > 
> >  	sd->s_parent = sysfs_get(acxt->parent_sd);
> 
> ...but this will cause many useful warnings to disappear.
> 
> What to do here?

Make a __sysfs_add_one() that doesn't warn.   Make
sysfs_add_one() be a wrapper around __sysfs_add_one()
that warns.

Change networking to call __sysfs_add_one().

Repeat and rinse up the call chain, as needed.

  reply	other threads:[~2008-05-15  8:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  0:03 [PATCH] net: Avoid problems with bonding and device rename Stephen Hemminger
2008-05-15  0:07 ` David Miller
2008-05-15  1:15 ` [PATCH 1/3] net: handle errors from device_rename Stephen Hemminger
2008-05-15  5:33   ` David Miller
2008-05-15  8:41   ` Wang Chen
2008-05-15 20:09     ` Stephen Hemminger
     [not found] ` <20080514181257.74fbb5aa@extreme>
2008-05-15  1:15   ` [PATCH 3/3] bonding: handle case of device named bonding_master Stephen Hemminger
2008-05-15  5:35     ` David Miller
2008-05-15  1:16   ` [PATCH 2/3] sysfs: remove error messages for -EEXIST case Stephen Hemminger
2008-05-15  1:26     ` David Miller
2008-05-15  3:14       ` Greg KH
2008-05-15  5:26         ` David Miller
2008-05-15  5:34     ` David Miller
2008-05-15  7:52     ` Cornelia Huck
2008-05-15  8:01       ` David Miller [this message]
2008-05-15  9:31         ` Cornelia Huck
2008-05-15 10:00           ` David Miller
2008-05-15 10:06             ` Cornelia Huck
2008-05-20 10:59               ` [PATCH] driver core: Suppress sysfs warnings for device_rename() Cornelia Huck
2008-05-20 21:45                 ` Stephen Hemminger
2008-05-20 22:52                   ` Greg KH
2008-05-20 22:52                 ` Greg KH
2008-05-21  8:05                   ` Cornelia Huck
2008-06-10  9:09                     ` Cornelia Huck
2008-06-10 15:30                       ` Stephen Hemminger

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=20080515.010139.219194657.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=cornelia.huck@de.ibm.com \
    --cc=fubar@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).