The pull request you sent on Mon, 11 Mar 2024 18:18:31 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/hardening-v6.9-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/216532e147b2fee6ee830f4a844bbc3cbb9137af
Thank you!
--
Deet-doot-
Hi Linus,
Please pull these kernel hardening updates for v6.9-rc1. As is pretty
normal for this tree, there are changes all over the place, especially
for small fixes, selftest improvements, and improved macro usability.
Some header changes ended up landing via this tree as they depended on
the st
On 08:28 Mon 30 Sep 2019, Randy Dunlap wrote:
On 9/30/19 8:26 AM, Bhaskar Chowdhury wrote:
On 08:13 Mon 30 Sep 2019, Jonathan Corbet wrote:
On Sat, 28 Sep 2019 20:43:03 +0530
Bhaskar Chowdhury wrote:
The following changes since commit 4e4327891fe2a2a4db342985bff4d4c48703c707:
replace dead
The pull request you sent on Mon, 16 Sep 2019 00:19:18 -0600:
> git://git.lwn.net/linux.git tags/docs-5.4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7c672abc120a55f678e5571ae2ee93f06ca4d7f9
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/us
The following changes since commit
d2eba640a4b96bc1bdc0f4a500b8b8d5e16725c8:
docs: phy: Drop duplicate 'be made' (2019-07-26 08:15:26 -0600)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.4
for you to fetch changes up to fe013f8bc160d79c6e33bb66d9bb0cd249492
The pull request you sent on Fri, 26 Jul 2019 08:21:25 -0600:
> git://git.lwn.net/linux.git tags/docs-5.3-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3ea54d9b0d655dab5b5becc7d6456082089fc166
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/
The following changes since commit
5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.3-1
for you to fetch changes up to d2eba640a4b96bc1bdc0f4a500b8b8d5e16725c8:
docs: phy: D
The pull request you sent on Tue, 16 Jul 2019 08:01:22 -0300:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git
> tags/docs/v5.3-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c309b6f2446c18a8b65d3950e6e755440865
Thank you!
--
Deet-doot-
Hi Linus,
As agreed with Jon, I'm sending this big series directly to you, c/c him,
as this series required a special care, in order to avoid conflicts with
other trees.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git
tags/docs/v5.3-1
For a series of pa
The pull request you sent on Tue, 9 Jul 2019 09:06:11 -0600:
> git://git.lwn.net/linux.git tags/docs-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e9a83bd2322035ed9d7dcf35753d3f984d76c6a5
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/use
The following changes since commit
d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.3
for you to fetch changes up to 454f96f2b738374da4b0a703b1e2e7aed82c4486:
docs: automark
The pull request you sent on Wed, 29 May 2019 09:54:08 -0600:
> git://git.lwn.net/linux.git tags/docs-5.2-fixes2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bec7550cca106c3ccc061e3e625516af63054fe4
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel
The following changes since commit
a65fd4f0def56f59822b2c49522d36319bc8da8b:
Documentation: kdump: fix minor typo (2019-05-21 09:31:28 -0600)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.2-fixes2
for you to fetch changes up to 551bd3368a7b3cfef01edaade8970
The pull request you sent on Thu, 23 May 2019 08:48:05 -0600:
> git://git.lwn.net/linux.git tags/docs-5.2-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/61686afe1ff378021da4e5509d081fb5196212d5
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.
The following changes since commit
a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.2-fixes
for you to fetch changes up to a65fd4f0def56f59822b2c49522d36319bc8da8b:
Document
On 2019/4/20 3:01 上午, Jonathan Corbet wrote:
> On Fri, 19 Apr 2019 18:39:51 +0800
> Alex Shi wrote:
>
>> he following changes since commit 5d2a2c59108a00ee550fd9a51f26de72e209a703:
>>
>> docs: speculation.txt: mark example blocks as such (2019-04-11 12:37:03
>> -0600)
>>
>> are available in
On Fri, 19 Apr 2019 18:39:51 +0800
Alex Shi wrote:
> he following changes since commit 5d2a2c59108a00ee550fd9a51f26de72e209a703:
>
> docs: speculation.txt: mark example blocks as such (2019-04-11 12:37:03
> -0600)
>
> are available in the Git repository at:
>
> https://github.com/alexshi/
The pull request you sent on Thu, 7 Mar 2019 15:18:20 -0700:
> git://git.lwn.net/linux.git tags/docs-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1a29e857507046e413ca7a4a7c9cd32fed9ea255
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/use
The following changes since commit
0358affb5cd8bbd685a6ab163a36dd28a818da73:
Documentation: change linux-4.x references to 5.x (2019-02-17 15:41:05 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.1
for you to fetch changes up to 4064174becc09a5a2385a27
The pull request you sent on Wed, 20 Feb 2019 14:08:59 -0700:
> git://git.lwn.net/linux.git tags/docs-5.0-fix
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f6163d67cc31b8f2a946c4df82be3c6dd918412d
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.or
The following changes since commit
bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.0-fix
for you to fetch changes up to 0358affb5cd8bbd685a6ab163a36dd28a818da73:
Documentat
On Fri, Jan 11, 2019 at 11:12:34AM -0700, Jonathan Corbet wrote:
> On Fri, 11 Jan 2019 18:07:49 +
> Liviu Dudau wrote:
>
> > I have a patch adding documentation for the AFBC modifiers supported
> > by the DRM framework with an upcoming patch series. Patch has been
> > out for review for a whi
Hi Matthew,
On Fri, Jan 11, 2019 at 10:13:44AM -0800, Matthew Wilcox wrote:
> On Fri, Jan 11, 2019 at 06:07:49PM +, Liviu Dudau wrote:
> > Hi Jonathan,
> >
> > I have a patch adding documentation for the AFBC modifiers supported
> > by the DRM framework with an upcoming patch series. Patch ha
On Fri, Jan 11, 2019 at 06:07:49PM +, Liviu Dudau wrote:
> Hi Jonathan,
>
> I have a patch adding documentation for the AFBC modifiers supported
> by the DRM framework with an upcoming patch series. Patch has been
> out for review for a while, please pull.
Nowhere in this email do you say wha
On Fri, 11 Jan 2019 18:07:49 +
Liviu Dudau wrote:
> I have a patch adding documentation for the AFBC modifiers supported
> by the DRM framework with an upcoming patch series. Patch has been
> out for review for a while, please pull.
>
> The include/uapi/drm/drm_fourcc.h change is only a comm
Hi Jonathan,
I have a patch adding documentation for the AFBC modifiers supported
by the DRM framework with an upcoming patch series. Patch has been
out for review for a while, please pull.
The include/uapi/drm/drm_fourcc.h change is only a comment pointing
towards the file's location, I hope thi
The pull request you sent on Fri, 4 Jan 2019 15:02:39 -0700:
> git://git.lwn.net/linux.git tags/docs-5.0-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b5aef86e089a2d85a6d627372287785d08938cbe
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.o
The following changes since commit
942104a21ce4951420ddf6c6b3179a0627301f7e:
docs: improve pathname-lookup document structure (2018-12-20 08:47:18 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.0-fixes
for you to fetch changes up to 93fb7f19985a08bbe3
On Sat, 29 Dec 2018 11:24:34 -0800
Linus Torvalds wrote:
> New signing key? And one that you forgot to push out to keyservers?
Sort of...some time ago, I tried to be a good kid and made a separate
signing subkey like Konstantin told me to. Then I couldn't ever get the
nitrokey thing to work and
The pull request you sent on Fri, 28 Dec 2018 09:06:22 -0700:
> git://git.lwn.net/linux.git tags/docs-5.0
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3868772b99e3146d02cf47e739d79022eba1d77c
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/us
On Fri, Dec 28, 2018 at 8:06 AM Jonathan Corbet wrote:
>
> git://git.lwn.net/linux.git tags/docs-5.0
New signing key? And one that you forgot to push out to keyservers?
Linus
The following changes since commit
651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.0
for you to fetch changes up to 942104a21ce4951420ddf6c6b3179a0627301f7e:
docs: improve
The pull request you sent on Wed, 14 Nov 2018 21:16:14 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-4.20-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dbb3c26034fa5336de45e667e2faf80a78531cd0
Thank you!
--
Deet-doot-dot, I am a
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.20-rc3
with top-most commit 97dc6c03c1b0a9af7aa26da7b0b266a762451f5f
Merge branch 'pm-cpuidle'
on top of commit 651022382c7f8da46cb4872a545ee1da6d097d2a
Linux 4.20-rc1
to receive p
On Mon, Nov 5, 2018 at 5:15 AM Martin Schwidefsky
wrote:
>
> This patch would work for me:
Thanks, applied,
Linus
On Mon, 5 Nov 2018 14:15:35 +0100
Martin Schwidefsky wrote:
>
> Follow-up question: the __no_sanitize_address_or_inline define has the
> 'notrace'
> option that is missing for __no_kasan_or_inline. We need that option for
> __load_psw_mask, if we do the replacement all users of __no_kasan_or_in
On Mon, 5 Nov 2018 07:02:56 +0100
Martin Schwidefsky wrote:
> On Fri, 2 Nov 2018 09:09:32 -0700
> Linus Torvalds wrote:
>
> > On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin
> > wrote:
> > >
> > > You're right, version checks shouldn't matter here. But
> > > __no_sanitize_address_or_inline
On Fri, 2 Nov 2018 09:09:32 -0700
Linus Torvalds wrote:
> On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin
> wrote:
> >
> > You're right, version checks shouldn't matter here. But
> > __no_sanitize_address_or_inline
> > shouldn't have been added in the first place, because we already have
> > a
On 11/02/2018 07:11 PM, Linus Torvalds wrote:
> On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin
> wrote:
>>
>> On 11/02/2018 04:46 AM, Linus Torvalds wrote:
>>>
>>> So I _think_ the KASAN config should have a
>>>
>>> depends on CC_IS_GCC && GCC_VERSION >= 40902
>>>
>>> on it, but maybe ther
On Fri, Nov 2, 2018 at 6:16 AM Andrey Ryabinin wrote:
>
> On 11/02/2018 04:46 AM, Linus Torvalds wrote:
> >
> > So I _think_ the KASAN config should have a
> >
> > depends on CC_IS_GCC && GCC_VERSION >= 40902
> >
> > on it, but maybe there is something I'm missing.
>
> I'd rather use cc-option
On Fri, Nov 2, 2018 at 2:43 AM Andrey Ryabinin wrote:
>
> You're right, version checks shouldn't matter here. But
> __no_sanitize_address_or_inline
> shouldn't have been added in the first place, because we already have almost
> the same
>__no_kasan_or_inline:
Ahh, very good.
Vasily, Martin -
On 11/02/2018 04:46 AM, Linus Torvalds wrote:
> On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds
> wrote:
>>
>> The logic for using __no_sanitize_address *used* to be
>>
>> #if GCC_VERSION >= 40902
>
> Ok, looking around, I think this has less to do with the attribute
> being recognized, and
On Fri, Nov 2, 2018 at 2:52 AM Linus Torvalds
wrote:
>
> Anyway, I decided to do the merge by just getting rid of the
> GCC_VERSION check around __no_sanitize_address_or_inline entirely. If
> you enable KASAN, then a function with that marking just won't be
> marked inline.
I was a bit confused w
On 11/01/2018 08:06 PM, Linus Torvalds wrote:
> On Mon, Oct 22, 2018 at 3:59 AM Miguel Ojeda
> wrote:
>>
>> Here it is the Compiler Attributes series/tree, which tries to disentangle
>> the include/linux/compiler*.h headers and bring them up to date.
>
> I've finally emptied the "normal" pull que
On Thu, Nov 1, 2018 at 10:06 AM Linus Torvalds
wrote:
>
> The logic for using __no_sanitize_address *used* to be
>
> #if GCC_VERSION >= 40902
Ok, looking around, I think this has less to do with the attribute
being recognized, and simply just being because KASAN itself wants
gcc-4.9.2.
I'm a
On Thu, Nov 1, 2018 at 6:06 PM Linus Torvalds
wrote:
>
> I'm not sure how much that matters (maybe the original check for 4.9.2
> was just a random pick by Andrey? Added to cc), but together with the
> movement to that looks like it also
> wouldn't want the CONFIG_KASAN tests, I wonder what the r
On Mon, Oct 22, 2018 at 3:59 AM Miguel Ojeda
wrote:
>
> Here it is the Compiler Attributes series/tree, which tries to disentangle
> the include/linux/compiler*.h headers and bring them up to date.
I've finally emptied the "normal" pull queues, and am looking at the
odd ones that I felt I needed
On Tue, Oct 23, 2018 at 9:11 AM Jonathan Corbet wrote:
>
> This is a fairly typical cycle for documentation. There's some welcome
> readability improvements for the formatted output, some LICENSES updates
> including the addition of the ISC license, the removal of the unloved and
> unmaintained 0
The following changes since commit
5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.20
for you to fetch changes up to aea74de4b216cdacda797d54220b8ac19daa1bf7:
docs: Fix ty
Hi Linus,
Here it is the Compiler Attributes series/tree, which tries to disentangle
the include/linux/compiler*.h headers and bring them up to date.
The patches have been in linux-next for a while, *except* the last two
from Nick which came a bit later. Since AFAIU there will be no linux-next
th
On Wed, Oct 17, 2018 at 11:26:34PM -0700, Christoph Hellwig wrote:
> On Tue, Oct 16, 2018 at 10:16:08AM -0700, Matthew Wilcox wrote:
> > > > git://git.infradead.org/users/willy/linux-dax.git ida-fixes-4.19-rc8
> > >
> > > How about you at least test these in linux-next? Putting things on top
>
On Tue, Oct 16, 2018 at 10:16:08AM -0700, Matthew Wilcox wrote:
> > > git://git.infradead.org/users/willy/linux-dax.git ida-fixes-4.19-rc8
> >
> > How about you at least test these in linux-next? Putting things on top
> > of the most recent change is a huge tip-off that this branch got no
> > t
On Tue, Oct 16, 2018 at 06:56:32PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Oct 15, 2018 at 01:40:17PM -0700, Matthew Wilcox wrote:
> >
> > Hi Greg,
> >
> > I have two tiny fixes, one for the IDA test-suite and one for the IDR
> > documentation license.
> >
> > The following changes since comm
On Mon, Oct 15, 2018 at 01:40:17PM -0700, Matthew Wilcox wrote:
>
> Hi Greg,
>
> I have two tiny fixes, one for the IDA test-suite and one for the IDR
> documentation license.
>
> The following changes since commit f0a7d1883d9f78ae7bf15fc258bf9a2b20f35b76:
>
> afs: Fix clearance of reply (201
Hi Greg,
I have two tiny fixes, one for the IDA test-suite and one for the IDR
documentation license.
The following changes since commit f0a7d1883d9f78ae7bf15fc258bf9a2b20f35b76:
afs: Fix clearance of reply (2018-10-15 15:31:47 +0200)
are available in the Git repository at:
git://git.inf
Hi Miguel,
On Fri, 5 Oct 2018 13:32:25 +0200 Miguel Ojeda
wrote:
>
> As discussed, here it is the Compiler Attributes series for
> linux-next. This time the original v6, based on -rc6.
>
> The changes w.r.t. v5:
>
> - Added latest Reviewed-by's and Tested-by's.
>
> The conflicts are trivial
Hi Stephen,
As discussed, here it is the Compiler Attributes series for
linux-next. This time the original v6, based on -rc6.
The changes w.r.t. v5:
- Added latest Reviewed-by's and Tested-by's.
The conflicts are trivial to solve, but if you want a reference, take
a look at (rebased on top of
Hi Ted,
On Thu, Oct 4, 2018 at 7:02 AM Theodore Y. Ts'o wrote:
> In this case, yes. Again, I emphasize that I was using the ext4.h
> cleanup as an *example*. The point I was trying to make was that your
> change did *not* do a full set of deep ext4 regression tests because
> the your change did
On Wed, Oct 03, 2018 at 11:41:08PM +0200, Miguel Ojeda wrote:
>
> I forgot to mention that if the definitions were different, it could
> have caused a problem, because your definition wouldn't apply, so your
> 27+ hours of testing wouldn't have mattered :-P Without the #ifndef,
> we would have at
On Wed, Oct 3, 2018 at 11:23 PM Miguel Ojeda
wrote:
> On Wed, Oct 3, 2018 at 5:33 PM Theodore Y. Ts'o wrote:
> > had done with full consideration, specifically for this reason. Even
> > if the definition was different, my definition *had* been fully tested
> > with over a 27+ VM hours of regress
Hi Ted,
On Wed, Oct 3, 2018 at 5:33 PM Theodore Y. Ts'o wrote:
>
> On Wed, Oct 03, 2018 at 01:54:05PM +0200, Miguel Ojeda wrote:
> >
> > Exactly. And for this case, I simply assumed Stephen wanted a clean
> > series to apply on top of the latest next-* tag (same way we base
> > stuff on top of -r
On Wed, Oct 03, 2018 at 01:54:05PM +0200, Miguel Ojeda wrote:
>
> Exactly. And for this case, I simply assumed Stephen wanted a clean
> series to apply on top of the latest next-* tag (same way we base
> stuff on top of -rc*s). Note that this is *not* really a "tree"
> collecting changes/developme
On Wed, 3 Oct 2018 14:34:28 +0200
Miguel Ojeda wrote:
> When I sent the first email, I assumed that changes in -next were
> supposed to be clean -- my mistake, but please document somewhere how
> -next works! Specially that you are rerere'ing conflicts and
> re-resolving them every day.
Yes, a d
Hi Stephen,
On Wed, Oct 3, 2018 at 1:00 AM Stephen Rothwell wrote:
>
> Hi Miguel,
>
> On Wed, 3 Oct 2018 00:36:52 +0200 Dominique Martinet
> wrote:
> >
> > Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > > As I have read, -next is supposed to be a vision of what the merge
> > > window will look li
On Wed, 3 Oct 2018 14:14:28 +0200
Miguel Ojeda wrote:
> HI Dominique,
>
> On Wed, Oct 3, 2018 at 12:37 AM Dominique Martinet
> wrote:
> >
> > Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > > As I have read, -next is supposed to be a vision of what the merge
> > > window will look like after mer
HI Dominique,
On Wed, Oct 3, 2018 at 12:37 AM Dominique Martinet
wrote:
>
> Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > As I have read, -next is supposed to be a vision of what the merge
> > window will look like after merging everything, i.e. ideally -rc1. For
> > that to work for files out-of-
Hi Ted,
On Wed, Oct 3, 2018 at 1:25 AM Theodore Y. Ts'o wrote:
>
> On Wed, Oct 03, 2018 at 12:12:10AM +0200, Miguel Ojeda wrote:
> > As I have read, -next is supposed to be a vision of what the merge
> > window will look like after merging everything, i.e. ideally -rc1. For
> > that to work for f
On Wed, Oct 03, 2018 at 12:12:10AM +0200, Miguel Ojeda wrote:
> As I have read, -next is supposed to be a vision of what the merge
> window will look like after merging everything, i.e. ideally -rc1. For
> that to work for files out-of-tree (like these ones, which are not
> maintained by a single t
Hi Miguel,
On Wed, 3 Oct 2018 00:36:52 +0200 Dominique Martinet
wrote:
>
> Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > As I have read, -next is supposed to be a vision of what the merge
> > window will look like after merging everything, i.e. ideally -rc1. For
> > that to work for files out-of-
Miguel Ojeda wrote on Wed, Oct 03, 2018:
> As I have read, -next is supposed to be a vision of what the merge
> window will look like after merging everything, i.e. ideally -rc1. For
> that to work for files out-of-tree (like these ones, which are not
> maintained by a single tree), changes should
Hi Nick,
On Tue, Oct 2, 2018 at 11:16 PM Nick Desaulniers
wrote:
>
> On Tue, Oct 2, 2018 at 2:11 PM Stephen Rothwell wrote:
> >
> > Hi Miguel,
> >
> > On Tue, 2 Oct 2018 15:47:12 +0200 Miguel Ojeda
> > wrote:
> > >
> > > The Compiler Attributes series has been stable for 10+ days. To
> > > inc
Hi Stephen,
On Tue, Oct 2, 2018 at 11:11 PM Stephen Rothwell wrote:
>
> Hi Miguel,
>
> On Tue, 2 Oct 2018 15:47:12 +0200 Miguel Ojeda
> wrote:
> >
> > The Compiler Attributes series has been stable for 10+ days. To
> > increase testing before 4.20, I would to request it being picked up
> > for
On Tue, Oct 2, 2018 at 2:11 PM Stephen Rothwell wrote:
>
> Hi Miguel,
>
> On Tue, 2 Oct 2018 15:47:12 +0200 Miguel Ojeda
> wrote:
> >
> > The Compiler Attributes series has been stable for 10+ days. To
> > increase testing before 4.20, I would to request it being picked up
> > for -next.
> >
> >
Hi Miguel,
On Tue, 2 Oct 2018 15:47:12 +0200 Miguel Ojeda
wrote:
>
> The Compiler Attributes series has been stable for 10+ days. To
> increase testing before 4.20, I would to request it being picked up
> for -next.
>
> The changes w.r.t. v5 in the LKML:
>
> - Rebased on top of next-20180928
Hi Stephen,
The Compiler Attributes series has been stable for 10+ days. To
increase testing before 4.20, I would to request it being picked up
for -next.
The changes w.r.t. v5 in the LKML:
- Rebased on top of next-20180928, which required removing
aligned_largest, which was removed by 9503cd9
Hi Arnd,
On Fri, Feb 23, 2018 at 01:26:09PM +0100, Arnd Bergmann wrote:
> On Fri, Feb 23, 2018 at 12:02 PM, James Hogan wrote:
> > I'm happy to put v2 in linux-next now (only patch 4 has changed, I just
> > sent an updated version), and send you a pull request early next week so
> > you can take
On Tue, Nov 14, 2017 at 1:46 PM, Linus Torvalds
wrote:
> And then people can do this:
>
> [url "ssh://g...@gitolite.kernel.org"]
> insteadOf = https://git.kernel.org
> insteadOf = http://git.kernel.org
> insteadOf = git://git.kernel.org
>
> which makes git.kernel.org addresses
Linus Torvalds writes:
> On Tue, Nov 14, 2017 at 1:33 PM, Tobin C. Harding wrote:
>>
>> Linus do you care what protocol? I'm patching Documentation and since
>> the point is creating pull requests for you 'some people' don't matter.
>
> I actually tend to prefer the regular git:// protocol and s
On Tue, Nov 14, 2017 at 1:33 PM, Tobin C. Harding wrote:
>
> Linus do you care what protocol? I'm patching Documentation and since
> the point is creating pull requests for you 'some people' don't matter.
I actually tend to prefer the regular git:// protocol and signed tags.
It's true that https
On Tue, Nov 14, 2017 at 12:05:00PM +0100, Greg Kroah-Hartman wrote:
> Adding lkml and linux-doc mailing lists...
>
> On Tue, Nov 14, 2017 at 10:11:55AM +1100, Tobin C. Harding wrote:
> > Hi Greg,
> >
> > This is totally asking a favour, feel free to ignore. How do yo
free to ignore. How do you format
> > your [GIT PULL] emails to Linus? Do you create a tag and then run a git
> > command to get the email?
> >
> > I tried to do it manually and failed pretty hard (as you no doubt will
> > notice on LKML).
>
> Well, I think yo
On Tue, Nov 14, 2017 at 3:05 AM, Greg Kroah-Hartman
wrote:
>
> Name the tag with something useful that you can understand if you run
> across it in a few weeks, and something that will be "unique".
> Continuing the example of my char-misc tree, for the patches to be sent
> to Linus for the 4.15-rc
On Tue, Nov 14, 2017 at 01:00:14PM +0100, Ulf Hansson wrote:
> [...]
>
> >
> > An example pull request of mine might look like:
> > Char/Misc patches for 4.15-rc1
> >
> > Here is the big char/misc patch set for the 4.15-rc1 merge
> > window. Contained in here is the normal
[...]
>
> An example pull request of mine might look like:
> Char/Misc patches for 4.15-rc1
>
> Here is the big char/misc patch set for the 4.15-rc1 merge
> window. Contained in here is the normal set of new functions
> added to all of these crazy drivers, as well
Adding lkml and linux-doc mailing lists...
On Tue, Nov 14, 2017 at 10:11:55AM +1100, Tobin C. Harding wrote:
> Hi Greg,
>
> This is totally asking a favour, feel free to ignore. How do you format
> your [GIT PULL] emails to Linus? Do you create a tag and then run a git
> command t
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.12-rc3
with top-most commit bb47e964175e5fb4c163066e4373fac055fe5da0
Merge branches 'pm-sleep' and 'powercap'
on top of commit 08332893e37af6ae779367e78e444f8f9571511d
Linux 4.12-rc
Hi Bjorn,
On Wednesday 12 April 2017 01:04 AM, Bjorn Helgaas wrote:
> On Mon, Apr 10, 2017 at 10:43:28AM -0500, Bjorn Helgaas wrote:
>> On Wed, Apr 05, 2017 at 02:22:20PM +0530, Kishon Vijay Abraham I wrote:
>>> Hi Bjorn,
>>>
>>> Please find the pull request for PCI endpoint support below. I've
>>
On Mon, Apr 10, 2017 at 10:43:28AM -0500, Bjorn Helgaas wrote:
> On Wed, Apr 05, 2017 at 02:22:20PM +0530, Kishon Vijay Abraham I wrote:
> > Hi Bjorn,
> >
> > Please find the pull request for PCI endpoint support below. I've
> > also included all the history here.
>
> Thanks, I applied these (wit
On Wed, Apr 05, 2017 at 02:22:20PM +0530, Kishon Vijay Abraham I wrote:
> Hi Bjorn,
>
> Please find the pull request for PCI endpoint support below. I've
> also included all the history here.
Thanks, I applied these (with v7 of the first patch) to pci/host-designware
for v4.12.
> Changes from v5
Hi Bjorn,
On Wednesday 05 April 2017 02:06 AM, Bjorn Helgaas wrote:
> On Mon, Mar 27, 2017 at 03:14:56PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> Please find the pull request for PCI endpoint support below. I've
>> also included all the history here.
>
> I tentatively applied this
Hi Bjorn,
Please find the pull request for PCI endpoint support below. I've
also included all the history here.
Changes from v5:
*) remove #syscon-cells property added in v5 and used
of_parse_phandle_with_fixed_args
*) fix compilation error in make.cross ARCH=blackfin that was because
pci_
On Mon, Mar 27, 2017 at 03:14:56PM +0530, Kishon Vijay Abraham I wrote:
> Hi Bjorn,
>
> Please find the pull request for PCI endpoint support below. I've
> also included all the history here.
I tentatively applied this to pci/host-designware with the mostly trival
textual changes below. If you p
On 03/29/2017 02:36 PM, Kishon Vijay Abraham I wrote:
(snip)
>>>
>>> FWIW:
>>> I've tested Kishon's tag pci-endpoint-for-4.12
>>> and PCIe on artpec6 SoC is still working fine.
>>
>> Thanks for testing it.
>>>
>>> I also included the DRA7xx PCIe driver in my
>>> kernel so that pcie-designware-ep.c
Hi,
On Wednesday 29 March 2017 05:40 PM, Kishon Vijay Abraham I wrote:
> Hi Niklas,
>
> On Wednesday 29 March 2017 05:12 PM, Niklas Cassel wrote:
>> On 03/27/2017 11:44 AM, Kishon Vijay Abraham I wrote:
>>> Hi Bjorn,
>>>
>>> Please find the pull request for PCI endpoint support below. I've
>>> al
Hi Niklas,
On Wednesday 29 March 2017 05:12 PM, Niklas Cassel wrote:
> On 03/27/2017 11:44 AM, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> Please find the pull request for PCI endpoint support below. I've
>> also included all the history here.
>>
>> Changes from v4:
>> *) add #syscon-cells pr
On 03/27/2017 11:44 AM, Kishon Vijay Abraham I wrote:
> Hi Bjorn,
>
> Please find the pull request for PCI endpoint support below. I've
> also included all the history here.
>
> Changes from v4:
> *) add #syscon-cells property and used of_parse_phandle_with_args
>to perform a configuration in
Hi Bjorn,
Please find the pull request for PCI endpoint support below. I've
also included all the history here.
Changes from v4:
*) add #syscon-cells property and used of_parse_phandle_with_args
to perform a configuration in syscon module (as suggested by
Rob Herring)
*) Remove unnecessary
Please find the pull request for PCI endpoint support below. I've
also included all the history here.
Changes from v3:
*) fixed a typo and adapted to https://lkml.org/lkml/2017/3/13/562.
Changes from v2:
*) changed the configfs structure as suggested by Christoph Hellwig. With
this change the
Em Wed, 14 Dec 2016 17:18:57 -0800
Greg Kroah-Hartman escreveu:
> On Wed, Dec 14, 2016 at 04:38:32PM -0800, Linus Torvalds wrote:
> > On Wed, Dec 14, 2016 at 11:18 AM, Jaegeuk Kim wrote:
> > >
> > > BTW, I just downloaded mainline, and tried to build a debian package but
> > > failed due to mi
Hi Mauro,
this is the reST migration of the *media* DocBook-XML set [1]. Its
based on your:
https://git.linuxtv.org/mchehab/experimental.git mchehab/docs-next
Since the flat-table patch is not yet in Jon's docs-next and your
mchehab/docs-next is one behind Jon', I had to merge these patches.
1 - 100 of 114 matches
Mail list logo
