Lines Matching refs:you
2 Information you need to know about netdev
27 and the "net-next" tree. As you can probably guess from the names, the
37 A: To understand this, you need to know a bit of background information
57 sent to netdev, but knowing the above, you can predict that in advance.
65 If you aren't subscribed to netdev and/or are simply unsure if net-next
87 A: Firstly, think whether you have a bug fix or new "next-like" content.
88 Then once decided, assuming that you use git, use the prefix flag, i.e.
93 bug-fix net content. If you don't use git, then note the only magic in
94 the above is just the subject text of the outgoing e-mail, and you can
95 manually change it yourself with whatever MUA you are comfortable with.
104 The "State" field will tell you exactly where things are at with
121 There is a patchworks queue that you can see here:
143 the upstream commit ID and why you think it should be a stable candidate.
145 Before you jump to go do the above, do note that the normal stable rules
146 in Documentation/stable_kernel_rules.txt still apply. So you need to
148 impacted. In addition, you need to convince yourself that you _really_
159 A: No. See above answer. In short, if you think it really belongs in
160 stable, then ensure you write a decent commit log that describes who
162 bug was introduced. If you do that properly, then the commit will
166 If you think there is some valid information relating to it being in
169 temporarily embed that information into the patch that you send.
181 it is requested that you make it look like this:
197 use the mailing lists and not reach out directly. If you aren't OK with
204 A: If your changes are against net-next, the expectation is that you
205 have tested by layering your changes on top of net-next. Ideally you
212 A: Attention to detail. Re-read your own work as if you were the
220 If it is your first patch, mail it to yourself so you can test apply
224 sure you are not repeating some common mistake documented there.