From: Darren Hart <dvhart@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Bastien Nocera <hadess@hadess.net>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Rafael Wysocki <rjw@rjwysocki.net>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch 1/2] thinkpad_acpi: signedness bugs getting current_mode
Date: Thu, 19 Mar 2015 03:42:03 +0000 [thread overview]
Message-ID: <20150319034203.GA22993@fury.dvhart.com> (raw)
In-Reply-To: <20150315134813.1b0a5685@canb.auug.org.au>
On Sun, Mar 15, 2015 at 01:48:13PM +1100, Stephen Rothwell wrote:
> Hi Darren,
>
> On Sun, 15 Mar 2015 13:46:12 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > The people you will inconvenience more by rebasing are the developers
> > who write patches that are based on your tree. If you rebase under
> > them, they may have to rebase and fix up the patches they have already
> > tested and had reviewed before they can then submit them to you
> > (hopefully before you rebase again).
>
> This, of course, only applied to published trees (which includes
> anything in linux-next) - what you do in your own (logically private)
> development tree is your own business.
Thanks for the guidance Stephen. Unless a more compelling argument comes up,
I'll stick to this going forward.
--
Darren Hart
Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Bastien Nocera <hadess@hadess.net>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Rafael Wysocki <rjw@rjwysocki.net>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch 1/2] thinkpad_acpi: signedness bugs getting current_mode
Date: Wed, 18 Mar 2015 20:42:03 -0700 [thread overview]
Message-ID: <20150319034203.GA22993@fury.dvhart.com> (raw)
In-Reply-To: <20150315134813.1b0a5685@canb.auug.org.au>
On Sun, Mar 15, 2015 at 01:48:13PM +1100, Stephen Rothwell wrote:
> Hi Darren,
>
> On Sun, 15 Mar 2015 13:46:12 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > The people you will inconvenience more by rebasing are the developers
> > who write patches that are based on your tree. If you rebase under
> > them, they may have to rebase and fix up the patches they have already
> > tested and had reviewed before they can then submit them to you
> > (hopefully before you rebase again).
>
> This, of course, only applied to published trees (which includes
> anything in linux-next) - what you do in your own (logically private)
> development tree is your own business.
Thanks for the guidance Stephen. Unless a more compelling argument comes up,
I'll stick to this going forward.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-19 3:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 9:34 [patch 1/2] thinkpad_acpi: signedness bugs getting current_mode Dan Carpenter
2015-03-11 9:34 ` Dan Carpenter
2015-03-11 10:07 ` Bastien Nocera
2015-03-11 10:07 ` Bastien Nocera
2015-03-11 10:28 ` Henrique de Moraes Holschuh
2015-03-11 10:28 ` Henrique de Moraes Holschuh
2015-03-14 19:03 ` Darren Hart
2015-03-14 19:03 ` Darren Hart
2015-03-14 21:06 ` Darren Hart
2015-03-14 21:06 ` Darren Hart
2015-03-15 2:46 ` Stephen Rothwell
2015-03-15 2:46 ` Stephen Rothwell
2015-03-15 2:48 ` Stephen Rothwell
2015-03-15 2:48 ` Stephen Rothwell
2015-03-19 3:42 ` Darren Hart [this message]
2015-03-19 3:42 ` Darren Hart
2015-03-22 18:58 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2015-03-22 18:58 ` Henrique de Moraes Holschuh
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=20150319034203.GA22993@fury.dvhart.com \
--to=dvhart@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=hadess@hadess.net \
--cc=hpa@zytor.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=kernel-janitors@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.