From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: rebase of the jdelvare-hwmon quilt series
Date: Thu, 5 Sep 2013 10:19:03 +1000 [thread overview]
Message-ID: <20130905101903.0198dbbfdf9e9172fb9b55b2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
Hi Jean,
Why did you bother rebasing the jdelvare-hwmon quilt series? None of the
patches changed (not that that even matters).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-09-05 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:19 Stephen Rothwell [this message]
2013-09-05 7:25 ` linux-next: rebase of the jdelvare-hwmon quilt series Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2013-07-11 0:27 Stephen Rothwell
2013-07-11 5:57 ` Jean Delvare
2013-07-11 6:53 ` Stephen Rothwell
2013-07-11 7:39 ` Jean Delvare
2013-07-11 23:17 ` Paul Gortmaker
2013-07-12 0:27 ` Stephen Rothwell
2013-07-12 0:36 ` Stephen Rothwell
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=20130905101903.0198dbbfdf9e9172fb9b55b2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).