From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/5] tty: Add a function to insert a string of characters with the same flag
Date: Sat, 27 Feb 2010 15:37:07 -0800 [thread overview]
Message-ID: <20100227233707.GA10941@kroah.com> (raw)
In-Reply-To: <20100227190212.5958a7d5@lxorguk.ukuu.org.uk>
On Sat, Feb 27, 2010 at 07:02:12PM +0000, Alan Cox wrote:
> On Fri, 26 Feb 2010 14:11:00 -0800
> Greg KH <greg@kroah.com> wrote:
>
> > On Wed, Feb 17, 2010 at 01:06:30PM +0000, Alan Cox wrote:
> > > The USB drivers often want to insert a series of bytes all with the same
> > > flag set - provide a helper for this case.
>
> Thats the original set of patches I sent you - there was a second set
> which cleaned up the stuff which leaked from one patch to the next or did
> those vanish into the department of email oblivion somewhere ?
No, I saw them after writing this, and I applied that series instead.
It should all be good now, sorry for the noise.
greg k-h
next prev parent reply other threads:[~2010-02-27 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 13:06 Alan Cox
2010-02-17 13:06 ` [PATCH 2/5] tty: Prune uses of tty_request_room in the USB layer Alan Cox
2010-02-17 13:06 ` [PATCH 3/5] tty: sort out the request_room handling for whiteheat Alan Cox
2010-02-17 13:07 ` [PATCH 4/5] tty: kill request_room for USB ACM class Alan Cox
2010-02-17 13:07 ` [PATCH 5/5] tty: Fix up char drivers request_room usage Alan Cox
2010-02-26 22:11 ` [PATCH 1/5] tty: Add a function to insert a string of characters with the same flag Greg KH
2010-02-27 14:45 ` Christopher Curtis
2010-02-27 19:02 ` Alan Cox
2010-02-27 23:37 ` Greg KH [this message]
2010-02-27 19:32 ` Alan Cox
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=20100227233707.GA10941@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@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
Powered by JetHome