From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Darren Hart <dvhart@infradead.org>,
Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree
Date: Wed, 3 May 2017 17:43:43 +0300 [thread overview]
Message-ID: <CAHp75Vc1TJ4W8m3TBGYq9FEQ5uM80jR4j2qRA6Oz6MRN3ErTsQ@mail.gmail.com> (raw)
In-Reply-To: <20170503142429.GA26229@spo001.leaseweb.nl>
On Wed, May 3, 2017 at 5:24 PM, Wim Van Sebroeck <wim@iguana.be> wrote:
>> On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote:
>> > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote:
>> > On a side note, it appears that I tagged "watchdog: iTCO_wdt: cleanup
>> > set/unset no_reboot_bit functions" with "Reviewed-by:", not with "Acked-by:".
>>
>> I noticed this as well. If Wim drops these, we'll correct that in our branch.
>
> It makes sence to keep the patches together. I will drop the patches from the watchdog tree.
Thanks, Wim.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2017-05-03 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 4:04 linux-next: manual merge of the drivers-x86 tree with the watchdog tree Stephen Rothwell
2017-05-02 18:09 ` Darren Hart
2017-05-02 19:12 ` Guenter Roeck
2017-05-02 20:21 ` Darren Hart
2017-05-02 20:57 ` Andy Shevchenko
2017-05-02 21:30 ` Darren Hart
2017-05-02 21:58 ` Guenter Roeck
2017-05-02 22:35 ` Darren Hart
2017-05-03 14:24 ` Wim Van Sebroeck
2017-05-03 14:43 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-04 3:37 Stephen Rothwell
2019-03-07 5:27 ` Darren Hart
2019-03-07 5:42 ` Darren Hart
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=CAHp75Vc1TJ4W8m3TBGYq9FEQ5uM80jR4j2qRA6Oz6MRN3ErTsQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=wim@iguana.be \
/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).