From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: "LKML" <linux-kernel@vger.kernel.org>,
"Russell King" <rmk+lkml@arm.linux.org.uk>,
"Al Viro" <viro@ftp.linux.org.uk>,
torvalds@osdl.org
Subject: Re: [PATCH/RFT] tlclk: convert to the new platform device interface
Date: Fri, 23 Dec 2005 14:42:55 -0500 [thread overview]
Message-ID: <200512231442.56682.dtor_core@ameritech.net> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470C36C8F9@orsmsx401.amr.corp.intel.com>
On Friday 23 December 2005 14:14, Gross, Mark wrote:
> The patch "looks" ok, but I have two issues:
>
> 2.6.15-rc6, hangs on the udev startup on my RHEL4 system so I can't
> smoke test this and more importantly an errata update patch I sent out
> earlier didn't make it in. (I was having email client issues with kmail
> changing tabs to spaces on me that day so it may be my fault that patch
> got dropped.)
>
> How would you like to proceed?
> 1) Should I send out an update patch that includes yours and the errata
> patch, knowing that we can only say that it compiles.
> 2) Should I send a unit tested errata patch to a 2.6.14.latest version?
> 3) Both 1 and 2?
> 4) Just ack your patch (I did review it and it compiles and looks fine)
> and re-submit my errata changes on top of your update?
>
My patch can safely wait till 2.6.16 opens so there is no hurry. I'd suggest
trying to resolve udev issue first and getting the errata patch into 2.6.15
and only then taking care of mine.
I do not know how critical that errata patch is to get it in 2.6.14.y.
--
Dmitry
next prev parent reply other threads:[~2005-12-23 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 19:14 [PATCH/RFT] tlclk: convert to the new platform device interface Gross, Mark
2005-12-23 19:42 ` Dmitry Torokhov [this message]
2005-12-23 22:43 ` [PATCH] " mgross
2005-12-24 3:30 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2005-12-16 6:55 Dmitry Torokhov
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=200512231442.56682.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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