From: Tilman Schmidt <tilman@imap.cc>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Jiri Kosina <jikos@jikos.cz>, Jeff Garzik <jeff@garzik.org>,
Greg KH <greg@kroah.com>,
hjlipp@web.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Usb-Devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: gigaset build broken on current linux-2.6.git
Date: Sun, 11 Feb 2007 19:40:15 +0100 [thread overview]
Message-ID: <45CF630F.1040706@imap.cc> (raw)
In-Reply-To: <45CC3109.1010502@imap.cc>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On Thu, 08 Feb 2007 14:02:31 +0100 I wrote:
> Subject: Re: [linux-usb-devel] [PATCH 41/70] usbcore: remove unused bandwith-related code
>
> This breaks compilation of drivers/isdn/gigaset/bas-gigaset.c.
> If you pass on this patch, please pass on Andrew's
>
> fix-gregkh-usb-usbcore-remove-unused-bandwith-related-code.patch
>
> along with it.
On Fri, 09 Feb 2007 09:30:01 +0100, I wrote:
> Jiri Kosina schrieb:
>> ISDN: gigaset - remove forgotten urb->bandwidth reference
>>
>> Recent changes in usbcore removed the bandwidth field from struct urb.
>> Remove the forgotten occurence in bas-gigaset.c
>>
>> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> Signed-off-by: Tilman Schmidt <tilman@imap.cc>
I notice that 2.6.20-git6 still doesn't include either of these fixes.
Is there anything I need to do in order to push it?
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
- In theory, there is no difference between theory and practice.
In practice, there is.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-02-11 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 22:28 gigaset build broken on current linux-2.6.git Jeff Garzik
2007-02-08 22:45 ` Jiri Kosina
2007-02-09 8:30 ` Tilman Schmidt
2007-02-11 18:40 ` Tilman Schmidt [this message]
2007-02-11 18:47 ` Greg KH
2007-02-12 6:16 ` Jeff Garzik
2007-02-12 18:37 ` Greg KH
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=45CF630F.1040706@imap.cc \
--to=tilman@imap.cc \
--cc=greg@kroah.com \
--cc=hjlipp@web.de \
--cc=jeff@garzik.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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).