From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>,
netdev@vger.kernel.org, Andrew Bird <ajb@spheresystems.co.uk>,
Javier Marcet <javier@krausbeck.org>,
Filip Aben <f.aben@option.com>,
Paulius Zaleckas <paulius.zaleckas@teltonika.lt>,
Oliver Neukum <oliver@neukum.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HSO: add option hso driver
Date: Tue, 13 May 2008 19:26:48 -0400 [thread overview]
Message-ID: <482A23B8.7050705@pobox.com> (raw)
In-Reply-To: <20080513232727.21c74bb2@core>
Alan Cox wrote:
>> Jeff, please queue this up for 2.6.27 if there are no problems that you
>> can see. It has been in the linux-next tree for a while, and many users
>> are reporting that it is working for them.
>>
>> Or if you feel it's ok for 2.6.26, I will not object to that either :)
>
> Can we get it into 2.6.26 - its a driver for new hardware and the driver
> is going to get a clean up for 2.6.27 anyway.
>
> Comments below are minor and I don't think blockers
>
> So for the serial side
>
> Acked-by: Alan Cox <alan@redhat.com>
AFAIK new drivers are OK post-rc1, since no possibility of regression
and it enables new users.
However, an exception to that might be a super-huge driver slipped in at
the last minute with no review (clearly not the case here)
Jeff
next prev parent reply other threads:[~2008-05-13 23:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 21:51 [PATCH] HSO: add option hso driver Greg KH
2008-05-13 21:51 ` Greg KH
2008-05-13 22:27 ` Alan Cox
2008-05-13 22:27 ` Alan Cox
2008-05-13 23:26 ` Jeff Garzik [this message]
2008-05-14 1:58 ` Greg KH
2008-05-14 4:57 ` Greg Kroah-Hartman
2008-05-14 4:57 ` Greg Kroah-Hartman
2008-05-14 13:59 ` Paulius Zaleckas
2008-05-14 13:59 ` Paulius Zaleckas
2008-05-14 15:12 ` Filip Aben
2008-05-14 17:36 ` Marcel Holtmann
2008-05-14 17:36 ` Marcel Holtmann
2008-06-12 2:51 ` Jeff Garzik
2008-05-14 4:52 ` [PATCH] " Greg KH
2008-05-14 4:52 ` Greg KH
2008-05-14 15:58 ` Jan Engelhardt
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=482A23B8.7050705@pobox.com \
--to=jgarzik@pobox.com \
--cc=ajb@spheresystems.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=f.aben@option.com \
--cc=greg@kroah.com \
--cc=javier@krausbeck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=paulius.zaleckas@teltonika.lt \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.