From: Hans Wennborg <hans-7z9IcJk4adCsTnJN9+BGXg@public•gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public•gmane.org>
Cc: starvik-VrBV9hrLPhE@public•gmane.org,
linux-cris-kernel-VrBV9hrLPhE@public•gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
kernel-janitors
<kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
devel <devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public•gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public•gmane.org
Subject: Re: [PATCH 1/1] cris: fix %d confusingly prefixed with 0x in format string
Date: Sun, 03 Aug 2014 17:25:13 -0700 [thread overview]
Message-ID: <53DED2E9.5090205@hanshq.net> (raw)
In-Reply-To: <1407046215.1835.24.camel@joe-AO725>
On 08/02/2014 11:10 PM, Joe Perches wrote:
> On Sat, 2014-08-02 at 18:19 -0700, Hans Wennborg wrote:
>> Yes, I have a patch for a bunch of these, but I figured it would be
>> easier to get it merged if I split it up. (Complete kernel newbie here.)
>
> You as a kernel newbie did good, thanks.
>
> A small tip would be to do all of them in a single series
> cc'ing each individual patch to the appropriate maintainers
> and mailing lists.
Thanks for the advice! I have split up and sent out the big patch as a
series, with hopefully the right folks CC'd.
- Hans
next prev parent reply other threads:[~2014-08-04 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1407018043-648-1-git-send-email-hans@hanshq.net>
[not found] ` <1407018043-648-1-git-send-email-hans-7z9IcJk4adCsTnJN9+BGXg@public.gmane.org>
2014-08-03 0:46 ` [PATCH 1/1] cris: fix %d confusingly prefixed with 0x in format string Joe Perches
2014-08-03 1:19 ` Hans Wennborg
2014-08-03 6:10 ` Joe Perches
2014-08-04 0:25 ` Hans Wennborg [this message]
2014-08-04 0:33 ` Joe Perches
2014-08-03 2:26 ` Steve French
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=53DED2E9.5090205@hanshq.net \
--to=hans-7z9icjk4adcstnjn9+bgxg@public$(echo .)gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public$(echo .)gmane.org \
--cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public$(echo .)gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public$(echo .)gmane.org \
--cc=kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-cris-kernel-VrBV9hrLPhE@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=starvik-VrBV9hrLPhE@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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