All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Anders Hammarquist <iko@iko.pp.se>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/2] *** SUBJECT HERE ***
Date: Tue, 25 Jun 2013 16:39:11 -0700	[thread overview]
Message-ID: <20130625233911.GA1087@kroah.com> (raw)
In-Reply-To: <201306221854.r5MIshv5013882@eskarina.iko.pp.se>

On Sat, Jun 22, 2013 at 08:54:43PM +0200, Anders Hammarquist wrote:
> In a message of Fri, 21 Jun 2013 16:56:03 -0700, Greg KH writes:
> >Please resend this in a format that I can apply it in (i.e. one that
> >does not require me to edit it by hand...)
> 
> After more fighting with git, I belive I now made it spit out what I
> wanted. Patch 1/2 ahead.
> 
> >> -static struct usb_device_id ti_id_table_3410[15+TI_EXTRA_VID_PID_COUNT+1] = {
> >> +static struct usb_device_id ti_id_table_3410[16+TI_EXTRA_VID_PID_COUNT+1] = {
> >
> >That's a mess, why have it be a static array at all?  Just include an
> >empty one at the end.
> 
> Indeed. I'd already had some (failed) thoughts about how to handle it
> nicely. Now I've had another think through, and I have something which
> deals with it and at least complains if TI_EXTRA_VID_PID_COUNT is changed
> without changing the initializer. Patch 2/2

Why don't we just drop the extra id thing entirely?  The usb-serial
subsystem handles new device ids being added dynamically from sysfs for
a long time now.  Removing this module option would clean up the code a
lot, and prevent these errors from ever happening again.

thanks,

greg k-h

  reply	other threads:[~2013-06-25 23:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  0:05 [PATCH 0/2] *** SUBJECT HERE *** Anders Hammarquist
2013-06-19 22:53 ` Greg KH
2013-06-21 23:08   ` Anders Hammarquist
2013-06-21 23:56     ` Greg KH
2013-06-22 18:54       ` Anders Hammarquist
2013-06-25 23:39         ` Greg KH [this message]
2013-06-26  8:29           ` Anders Hammarquist
2013-06-26 10:39             ` Johan Hovold
2013-06-27 21:50               ` Anders Hammarquist
2013-06-28 10:23                 ` Johan Hovold
2013-06-28 10:24                   ` [PATCH] USB: ti_usb_3410_5052: fix dynamic-id matching Johan Hovold
2013-07-01 23:22                   ` [PATCH 0/2] *** SUBJECT HERE *** Anders Hammarquist
2013-07-02  9:46                     ` Johan Hovold
2013-06-22 18:55       ` [PATCH 1/2] * Remove unused and overly generic ABBOTT_PRODUCT_ID * Fix sizes of statically sized usb_debvice_id tables Anders Hammarquist
2013-06-22 18:55         ` [PATCH 2/2] Remove static sizing of usb_device_id arrays Anders Hammarquist
2013-07-24 22:52           ` Greg KH
2013-07-25 14:15             ` Anders Hammarquist
2013-07-25 14:37               ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2026-03-24  3:26 [PATCH 0/2] *** SUBJECT HERE *** Meiker Gao
2026-03-24  6:20 ` Meiker Gao (高俊)
2026-03-24  2:47 Meiker Gao
2024-03-30  6:41 lixiaoyong
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov
2021-05-07  4:36 Saurav Girepunje
2021-05-07  6:00 ` Greg KH
2021-05-07  6:18   ` SAURAV GIREPUNJE
2021-04-16  8:07 Tao Zhang
2021-04-16  8:11 ` Greg Kroah-Hartman
2021-04-16  8:11   ` Greg Kroah-Hartman
2019-03-11 15:04 Colin Watson
2019-03-13  9:56 ` Daniel Kiper
2019-03-13 10:12   ` Colin Watson
2019-03-13 10:22     ` Daniel Kiper
2016-03-13 19:50 Andrew Pinski
2016-03-13 19:50 ` Andrew Pinski
2014-06-18 15:34 Claire Murphy
2013-11-20 22:02 Chris Zankel
2013-07-10 13:14 Damien Millescamps
2011-05-03  7:00 sukeshs
2011-05-03 12:14 ` Greg KH
2010-11-29 17:56 Arnaldo Carvalho de Melo
2010-01-06  4:30 [lm-sensors] [RFC/PATCH 0/2] Updates to improve device tree support Bill Gatliff
2010-01-06  4:30 ` [PATCH 0/2] *** SUBJECT HERE *** Bill Gatliff
2010-01-06  4:32   ` Bill Gatliff
2009-06-10 11:51 Izik Eidus
2009-06-08  4:31 Junio C Hamano
2008-08-29  8:16 [PATCH 0/6] 'git svn info' fixes Eric Wong
2008-08-29 13:42 ` [PATCH 0/2] *** SUBJECT HERE *** Thomas Rast

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=20130625233911.GA1087@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=iko@iko.pp.se \
    --cc=linux-kernel@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 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.