From: Gerd Hoffmann <kraxel@redhat.com>
To: Pantelis Koukousoulas <pktoss@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb: Remove magic constants from device bmAttributes
Date: Mon, 16 Dec 2013 12:43:20 +0100 [thread overview]
Message-ID: <1387194200.28883.5.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1387186600-20389-1-git-send-email-pktoss@gmail.com>
On Mo, 2013-12-16 at 11:36 +0200, Pantelis Koukousoulas wrote:
> Replace magic constants in device bmAttributes with symbolic ones
> from Linux kernel ch9.h
> - .bmAttributes = 0xc0,
> + .bmAttributes = USB_CONFIG_ATT_ONE | USB_CONFIG_ATT_SELFPOWER,
Looks good, but fails checkpatch with lots of "WARNING: line over 80
characters" messages.
cheers,
Gerd
next prev parent reply other threads:[~2013-12-16 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 9:36 [Qemu-devel] [PATCH] usb: Remove magic constants from device bmAttributes Pantelis Koukousoulas
2013-12-16 11:43 ` Gerd Hoffmann [this message]
2013-12-16 12:34 ` Pantelis Koukousoulas
2013-12-16 14:27 ` Gerd Hoffmann
2013-12-16 15:10 ` Pantelis Koukousoulas
2014-01-28 14:26 ` Gerd Hoffmann
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=1387194200.28883.5.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=pktoss@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).