linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 6 (hid)
Date: Thu, 7 Mar 2013 09:13:32 +0100	[thread overview]
Message-ID: <CAN+gG=H4_1nUhhsUe031Q1QrnVna+F7hmAepe6kbNm=8z_gOjw@mail.gmail.com> (raw)
In-Reply-To: <51379849.6040903@infradead.org>

Hi Randy,

On Wed, Mar 6, 2013 at 8:26 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 03/05/13 16:50, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130305:
>>
>
> on i386 and x86_64:
>

Sorry, it looks like my patches went not very smoothly.

> ERROR: "usb_control_msg" [drivers/hid/hid-multitouch.ko] undefined!

I've submitted a new patch removing this direct call. Maybe we should
change the Kconfig while these patches are not applied. Jiri?

> ERROR: "usb_ifnum_to_if" [drivers/hid/hid-holtek-kbd.ko] undefined!

oops, I'll have to double check this one.

>
> when CONFIG_USB_SUPPORT is not enabled.
>
> Should these drivers depend on USB_HID?

The goal of the patch series that breaks this was to make the hid
drivers independent of their transport layers, thus most of them
should not depend on usbhid anymore.

Cheers,
Benjamin

>
>
> --
> ~Randy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-03-07  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  0:50 linux-next: Tree for Mar 6 Stephen Rothwell
2013-03-06 19:26 ` linux-next: Tree for Mar 6 (hid) Randy Dunlap
2013-03-07  8:13   ` Benjamin Tissoires [this message]
2013-03-07 10:09     ` Jiri Kosina
2013-03-07 10:28       ` Benjamin Tissoires
2013-03-07 10:33         ` Jiri Kosina
2013-03-07 11:20           ` Benjamin Tissoires

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='CAN+gG=H4_1nUhhsUe031Q1QrnVna+F7hmAepe6kbNm=8z_gOjw@mail.gmail.com' \
    --to=benjamin.tissoires@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).