From: Valdis.Kletnieks@vt.edu
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-04-22-16-38 uploaded
Date: Thu, 22 Apr 2010 21:40:47 -0400 [thread overview]
Message-ID: <10748.1271986847@localhost> (raw)
In-Reply-To: Your message of "Fri, 23 Apr 2010 09:46:25 +0900." <20100423094625.70beb17a.kamezawa.hiroyu@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Fri, 23 Apr 2010 09:46:25 +0900, KAMEZAWA Hiroyuki said:
> On Thu, 22 Apr 2010 16:38:55 -0700
> akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2010-04-22-16-38 has been uploaded to
> > drivers-usb-net-kawethc-add-device-allied-telesyn-at-usb10-usb-ethernet-ada
pter.patch
>
> This patch can't be applied...
> maybe drivers/usb/net directory doesn't exist ??
>
> Now I just skip this one.
Looks more like a path error in the patch.
diff -puN drivers/usb/net/kaweth.c~drivers-usb-net-kawethc-add-device-allied-telesyn-at-usb10-usb-ethernet-adapter drivers/usb/net/kaweth.c
|--- a/drivers/usb/net/kaweth.c~drivers-usb-net-kawethc-add-device-allied-telesyn-at-usb10-usb-ethernet-adapter
|+++ a/drivers/usb/net/kaweth.c
However, there *is* a drivers/net/usb/kaweth.c and the patch applies once
you fix the paths.
kaweth-new-usb-id-07c9-b010-allied-telesyn-at-usb10.patch appears to be a
near-duplicate (correct path in diff, different comment.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-04-23 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 23:38 mmotm 2010-04-22-16-38 uploaded akpm
2010-04-23 0:46 ` KAMEZAWA Hiroyuki
2010-04-23 1:40 ` Valdis.Kletnieks [this message]
2010-04-23 1:57 ` Valdis.Kletnieks
2010-04-26 21:41 ` Lee Schermerhorn
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=10748.1271986847@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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