From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <axboe@kernel.dk>
Cc: Lee Trager <Lee@PicturesInMotion.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, bzolnier@gmail.com
Subject: Re: [PATCH] HPA resume fix
Date: Tue, 29 Aug 2006 13:50:27 +0100 [thread overview]
Message-ID: <1156855828.6271.106.camel@localhost.localdomain> (raw)
In-Reply-To: <20060829114210.GI12257@kernel.dk>
Ar Maw, 2006-08-29 am 13:42 +0200, ysgrifennodd Jens Axboe:
> On Tue, Aug 29 2006, Alan Cox wrote:
> > For -mm only to get more testing
> >
> > Acked-by: Alan Cox <alan@redhat.com>
>
> It should go into the state machine as described imho. Bart?
If it works then yes it can become an explicit state. Firstly we need to
find out if it works.
next prev parent reply other threads:[~2006-08-29 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 9:55 [PATCH] HPA resume fix Lee Trager
2006-08-29 11:11 ` Alan Cox
2006-08-29 11:42 ` Jens Axboe
2006-08-29 12:50 ` Alan Cox [this message]
2006-08-29 12:32 ` Jens Axboe
2006-08-30 8:55 ` Lee Trager
2006-08-30 8:59 ` Jens Axboe
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=1156855828.6271.106.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Lee@PicturesInMotion.net \
--cc=akpm@osdl.org \
--cc=axboe@kernel.dk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).