From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-next@vger.kernel.org, Oliver Neukum <oliver@neukum.org>
Subject: Re: linux-next: hid tree build warning
Date: Sat, 21 Feb 2009 10:11:00 +1100 [thread overview]
Message-ID: <20090221101100.b35d5a45.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LNX.1.10.0902201254100.18874@jikos.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
Hi Jiri,
On Fri, 20 Feb 2009 12:55:07 +0100 (CET) Jiri Kosina <jkosina@suse.cz> wrote:
>
> Thanks a lot for catching this, I have fixed it (moved hid_reset_resume()
> into the ifdef CONFIG_PM part of the source) and pushed the fix to the
> branch you pull into -next.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-02-20 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 8:08 linux-next: hid tree build warning Stephen Rothwell
2009-02-20 11:55 ` Jiri Kosina
2009-02-20 23:11 ` Stephen Rothwell [this message]
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=20090221101100.b35d5a45.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jkosina@suse.cz \
--cc=linux-next@vger.kernel.org \
--cc=oliver@neukum.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