From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: import of usb series failed
Date: Tue, 23 Feb 2010 18:16:24 -0800 [thread overview]
Message-ID: <20100224021624.GB14159@kroah.com> (raw)
In-Reply-To: <20100220120207.1d765147.sfr@canb.auug.org.au>
On Sat, Feb 20, 2010 at 12:02:07PM +1100, Stephen Rothwell wrote:
> So, since the ".current" series are all empty, I am importing the
> driver-core, tty and then usb series on top of v2.6.33-rc8. I have just
> done this again manually and the failure still happens (I have not
> refetched your quilt series since yesterday.
>
> At this point, the file drivers/usb/serial/ftdi_sio_ids.h from line 185
> looks like this:
>
> #define FTDI_ELV_PCD200_PID 0xF06C /* PC-Datenlogger (PCD 200) */
> #define FTDI_ELV_ULA200_PID 0xF06D /* USB-LCD-Ansteuerung (ULA 200) */
> #define FTDI_ELV_ALC8500_PID 0xF06E /* ALC 8500 Expert */
> #define FTDI_ELV_FHZ1000PC_PID 0xF06F /* FHZ 1000 PC */
> #define FTDI_ELV_UR100_PID 0xFB58 /* USB-RS232-Umsetzer (UR 100) */
> #define FTDI_ELV_UM100_PID 0xFB5A /* USB-Modul UM 100 */
>
> The patch hunk looks like this:
>
> @@ -185,7 +185,7 @@
> #define FTDI_ELV_TFD128_PID 0xE0EC /* ELV Temperatur-Feuchte-Datenlogger TFD 128 */
> #define FTDI_ELV_FM3RX_PID 0xE0ED /* ELV Messwertuebertragung FM3 RX */
> #define FTDI_ELV_WS777_PID 0xE0EE /* Conrad WS 777 */
> -#define FTDI_ELV_EM1010PC_PID 0xE0EF /* Engery monitor EM 1010 PC */
> +#define FTDI_ELV_EM1010PC_PID 0xE0EF /* Energy monitor EM 1010 PC */
> #define FTDI_ELV_CSI8_PID 0xE0F0 /* Computer-Schalt-Interface (CSI 8) */
> #define FTDI_ELV_EM1000DL_PID 0xE0F1 /* PC-Datenlogger fuer Energiemonitor (EM 1000 DL) */
> #define FTDI_ELV_PCK100_PID 0xE0F2 /* PC-Kabeltester (PCK 100) */
>
> Between v2.6.33-rc8 and the head if Linus' tree thee are two patches that
> change this file. So I guess the BASE in the driver-core.current series
> files needs updating.
Yes, that seems to be the problem here.
I have been doing the BASE tag as a -rc level tag (or rc-gitX tag), can
I use a SHA1 of Linus's tree to base this against instead? Would that
work ok with your scripts?
thanks for figureing this out, sorry for the trouble, this was my fault.
greg k-h
next prev parent reply other threads:[~2010-02-24 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 23:55 linux-next: import of usb series failed Stephen Rothwell
2010-02-18 0:21 ` Greg KH
2010-02-18 2:22 ` Stephen Rothwell
2010-02-19 6:52 ` Stephen Rothwell
2010-02-19 15:53 ` Greg KH
2010-02-20 1:02 ` Stephen Rothwell
2010-02-24 2:16 ` Greg KH [this message]
2010-02-24 4:01 ` Stephen Rothwell
2010-02-25 17:54 ` Greg KH
2010-02-26 0:27 ` Stephen Rothwell
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=20100224021624.GB14159@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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