From: Andrew Morton <akpm@linux-foundation.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
linux-usb-devel@lists.sourceforge.net, hjlipp@web.de,
kkeil@suse.de, i4ldeveloper@listserv.isdn4linux.de,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 1/2] usb_gigaset: suspend support [v2]
Date: Thu, 1 Nov 2007 11:45:37 -0700 [thread overview]
Message-ID: <20071101114537.0091c8d1.akpm@linux-foundation.org> (raw)
In-Reply-To: <472A18D7.7020703@imap.cc>
On Thu, 01 Nov 2007 19:20:07 +0100
Tilman Schmidt <tilman@imap.cc> wrote:
> >> +static int gigaset_suspend(struct usb_interface *intf, pm_message_t message)
> >> +{
> >> + struct cardstate *cs;
> >> + struct usb_cardstate *ucs;
> >> +
> >> + if ((cs = usb_get_intfdata(intf)) == NULL ||
> >> + (ucs = cs->hw.usb) == NULL) {
> >> + err("%s: no cardstate", __func__);
> >> + return -EFAULT;
> >> + }
> >
> > Is the above reeeeeely needed? I bet it never happens.
>
> I'm a great believer in defensive programming. :-)
>
> Anyway, to be sure these checks aren't needed, I would need the
> assurance that the suspend and resume methods are serialized with
> the probe and disconnect methods. Are they?
dunno it beats me. Not to my knowledge. Perhaps Greg and Rafael would know?
next prev parent reply other threads:[~2007-11-01 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071029185311.4C955FC04C@xenon.ts.pxnet.com>
2007-10-29 19:10 ` [linux-usb-devel] [PATCH 1/2] usb_gigaset: suspend support Alan Stern
2007-10-29 21:20 ` Tilman Schmidt
2007-10-30 8:52 ` Oliver Neukum
2007-11-01 20:17 ` Tilman Schmidt
[not found] ` <20071029214131.70EABFC043@xenon.ts.pxnet.com>
2007-10-30 21:01 ` [PATCH 1/2] usb_gigaset: suspend support [v2] Andrew Morton
2007-11-01 18:20 ` Tilman Schmidt
2007-11-01 18:45 ` Andrew Morton [this message]
2007-11-01 19:47 ` [linux-usb-devel] " Alan Stern
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=20071101114537.0091c8d1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rjw@sisk.pl \
--cc=tilman@imap.cc \
/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